Just because people use "for the children" in inappropriate scenarios to further an agenda has nothing to do with this discussion and you know it.
If you make a tool to essentially hide people's activity online, you KNOW what it's going to ultimately be used for.
...and you clearly think it's worth the trade off. So no need to continue
Yeah, it's a lot to pay for a keyboard that might not work out for you. That's why I suggest the Logitech.
I'd prefer one without the numpad, personally like the old Microsoft Sculpt, but for some reason MS refuses to update that keyboard to a more modern, lower latency wireless tech.
I'm currently flirting with some of the mechanical options like the Moonlander, but haven't yet pulled the trigger on that one.
As for the mouse, seriously the vertical mouse made a HUGE difference for me. More than the keyboard honestly.
BUILD SOMETHING.
Learning concepts without the ability to apply them are essentially useless.
Get your hands dirty and build something that would be valuable to you and solve a problem for yourself.
Don't get hung up on doing it "right". Focus on making it work. Don't worry about how it'll work for a million users. Right now your focus is on making it work for one user.
As you go you'll hit walls. Research how to get past them and keep going. Again, you're going to make mistakes. DO NOT GET HUNG UP ON THIS.
Making mistakes is part of the journey. Even the best software engineers in the world rarely get things right their first try. It's part of the process.
I feel like we're splitting hairs here. MIT is an extremely permissible license. The fact someone could take this and make a closed source fork doesn't affect the existence or openness of the MIT licensed releases
https://github.com/bluesky-social
Even their web and mobile clients are FOSS
The FUD and misinformation on here about Bluesky an AT is wild
Of course. The well has been poisoned, and there's no way to know what any company's actually doing behind the scenes. I'm just lamenting that it had to come to this.
This is honestly a nightmare for developers who rely on telemetry and metrics to identify issues and bugs that are otherwise "silent".
Just because your app doesn't throw errors doesn't mean the code isn't flawed and trapping users within a part of the experience that they cannot fix or leave.
I cant speak for every team in every company, but there's very little to no interest in "harvesting" your "data" for profit.
We just want to figure out what broke and how we correct it ASAP.
I think Reddit does have a legitimate argument that the scales have tipped and Reddit eating the costs of "whales" abusing their APIs for for-profit use cases without Reddit being compensated at all is fair.
3P apps using the API at no cost while simultaneously monetizing Reddit's content by showing their own ads does seem to be taking advantage.
That said, the way Reddit approached this was so scorched earth and bone headed.
For example. Reddit gets 10s of millions of dollars in free content moderation services from volunteers. The moderators of all their biggest subreddits rely on 3P moderation tools since Reddit's are so poor.
So with the new API policy, they're asking their unpaid moderators to PAY them for the privilege. It's such a slap in the face.
Finally to address the original question, Reddit should absolutely block API consumers who are just training their glorified chat bots to regurgitate plagerized content.
Tip 1: Assuming you are starting work at a company that has a healthy culture, do not be afraid to ask for help! There's a lot to learn and it's going to take time to get up to speed. Don't freak out because you aren't slinging PRs like the rest of the team after a week.
However when asking for help, you should open with what you've done already to help yourself. It's important to respect your peer's time, so trying to optimize for efficiency and help them help you as much as possible.
Part of this is also not spinning your wheels and struggling for so long that they need to spend a ton of time helping digging you out of the hole you dug for yourself.
Tip 2: Next is it's important to pay it forward. Docs are super outdated and you got more current knowledge from a braindump from a more experienced engineer? UPDATE THE DOCS!
Tip 3: Once you find your footing, and ship some projects and get a feel for things, it's important to find your voice. If your most Senior engineer on the team proposes something, don't just follow it blindly. If you see a blind spot in the approach, please raise it! Ask questions!
Truly great senior engineers hate it when the team just rolls over and blindly accepts their proposals/architecture. They want feedback! No one is perfect or sees everything. They want the team's help to stress test the approach.
Tip 4: Make sure you keep an open dialog about expectations with your manager. Never assume your manager knows how you spend your time every moment of every day. Ensure you give your manager visibility into your "invisible work".
Examples of invisible work would be taking time to help a new hire. Having conversations with people on another team you depend on or who depends on you to come to consensus on an approach that is beneficial to both teams. Or something like updating documentation or spending time in meetings to review engineering designs, collaborating with product and designers, etc etc etc
Tip 5: Don't be a dick. Avoid being super defensive and assuming others are out to get you, embarrass you, or generally are operating in bad faith until they prove otherwise.
Tip 6: Respect what came before. You'll surely come across some seriously jank code, or a ton of tech debt, or poor approaches. Due to business needs of the time, crunch time, lack of resources, etc are often reasons people did what they did. They very likely know certain things are bad. Calling out bad code or architecture isn't impressing anyone. They know.
When identifying these things, start by asking for context. Come with solutions that are attainable. Calling out things without fresh ideas on how to solve these known problems is not helpful and a waste of everyone's time. Focus on approaches for how to fit fixing the problems into your team's resourcing.
Tip 7: Learn to communicate in a way that resonates with your audience. Try to understand their motivations and what matters to them. Saying that something sucks and we should rebuild in your preferred tech is not an argument. What's the value? How long would it take? What are the trade offs? How does doing this work achieve the businesses' goals?
Not defending LMG's mistakes, but GN's opinion that you should not ask for comment doesn't hold water.
GN definitely has an agenda here. He made several comments that made it quite clear he's resentful of LTT's success.
While I don't think anything he reported is false, it's all wrapped in a narrative that relies on implications. He certainly makes a whole lot of hay about a few small mistakes and heavily implies LTT is in the pockets of their sponsors and a conspiracy theory that LTT is only successful because of some connections and preferred treatment by YouTube.
He's very much trying to establish a narrative that LMG is wildly corrupt and undeserving of their success. However, a lot of it comes across as sour grapes.