Agreed. It's easy to handwave it off. Americans churn out propaganda and inject it into every form of media it can. Similar to preservatives, some media is more nitrate than meat. China cuts it out because it says it's unhealthy to consume. China can do that overtly in it's culture war because it has never guaranteed not to.
The cheapest way to scale mental problems is to use the state to replace the father's role in a family. I know plenty of large families with perfectly well adjusted kids. I can't say I've met any well adjusted kids raised by a single mom.
Guilded over discord in my opinion. More features like forums in a channel. Long term, I only see discord and their company culture turning it into twitch or other zealot infested dumps.
Salesforce doesn't care. There about to roll out slack-first infrastructure that turns slack into the only chat-based CRM. Their core users aren't on the free model. They're paying a small fortune for Salesforce and see Slack's cost as a drop in the bucket.
The author is being overly semantic about a widely observed phenomenon in order to sling his devops. He's saying the phrase isn't good because a 10x developer given grunt work couldn't actually churn it at 10x speeds, but they're capable of doing complex work 95x+ faster than an average dev. It adds nothing to the discussion and is feel good drivel for insecure developers.
Cities in the US with strong public transit have only ended up building moving toilets for the homeless. There are a number of bigger issues that come first before billions more in public funding goes into larger wheeled toilets.
Every year learn a programming language that is a whole new paradigm. Stack-based FORTH, a Lisp dialect like Clojure, x86, etc. Do this while getting as strong as you can in your main language(s). Write your own simple scripting language that solves a problem you actually run into. Maybe something like a tool that scaffolds code for you.
If you enjoyed that, take it even further. Get familiar with some more advanced data structures and patterns. FSA, abstract syntax trees, bloom filters, compressed bit vectors. Build an API, a framework and an engine to get deep into the world of being a code steward. Learn how to write and document code that goes into central infrastructure.
While you're doing this, get something like FB reader and pay $7 for premium. Have it read the SWEBOK out loud to you. Get deep into understanding software design, construction methods, testing, maintenance and all of the moving parts in the E2E process.
Note that above isn't necessarily good advice, just like all of the advice in this thread. "having fun it" or "doing hallucinogens" or "listen to some online courses" won't accomplish your goal. If some of the things above resonate with you, go for it. Mostly, just fuel your curiosity without burning yourself out.
Look at what more successful people are doing, deconstruct how you could do that yourself, and keep doing it until "more successful people" are few and far in-between.
One of the teams I oversee works exclusively with FS. Here's the gist from my POV.
It's hard to get fired from the bank. This leads to a downward spiral. Good developers are pushed out because they don't want to do the work of people who hide for a living. The hiders create a game with management that makes their job easier.
"We're all going to pretend this work is really complex and takes forever to do."
The longer you play this game, the less exposure you get to real challenges and skill growth. The cycle causes change in banking systems to be the slowest of any industry. This causes banks to be more than a decade behind everything else. This causes FS devs to be unable to catch up to modern best practices.
Probably not, but generation focus is pretty good at connecting companies with specific subsets of users. I know they already maintain a list of current heroku devs.
I can only speak about render.com which I've seen recommended several times. I was thoroughly unimpressed. Heroku is my go to when I want to spend no more than 5 minutes getting a microservice deployed. Otherwise I would use DO. Render seemed to be the longer and clunkier experience of DO without the benefits of DO.
Your skill at a job doesn't equate to your value as a person. A job is just a way I and most others contribute back to the world. It's in everyone's best interest if there aren't unnecessary barriers to that contribution. For instance, universities' poor curriculums and the way they predatorily pretend to be the gatekeepers of "prestigious" jobs.
It's more interesting for many to believe that AI could be so powerful that we run into fantastical problems like what you described. That's the only reason I've been able to come up with to explain why people think deeply fake looking deep fakes are approaching Azimovian levels.
The best option is not to go. I had also done full time programming for clients from age 15 on. 5 years after that I got opportunities to lead small projects. 10 more years after that and I was made VP of an engineering department. I've worked a lot with fresh graduates from "good" schools with good GPAs. I've always been thoroughly unimpressed by what they know and what they think is important for the job.