So yes, there is very little tolerance from us toward those who are in it for money/status/prestige, and not for the love of it.
Somewhat, sure.
It's also managers who tell you you're being laid off, but good news, not for three months. And, oh, by the way, if you leave early no severance.
And why are you being laid off?
Your duties are being offshored.
_You_ aren't being offshored because they need three people to replace you, but your duties are.
Ostensibly this saves money.
I’m a maintainer on one library in small part because of an argument I had with a maintainer of a similar library years ago. And nearly a maintainer on another one. I voted with my feet and made improvements to DX an/or performance because I can’t pull down a wrongheaded project but I can pull up a better one.
(Incidentally I looked at his issue log the other day and it’s 95% an enumeration of the feature list of the one I’m helping out on. Ha!)
Do I go soul searching now or start a blog?
Working with people that love what they're doing can be very chill. Working with people angling for a promotion, taking shortcuts, one-upping the co-workers and still not pulling their weight is exhausting.
This is not a new phenomenon, in the past this kind of dev also existed. Lots of people studied CompSci but didn't want to be a "lowly developer" for long and were just making time to "become a manager". Of course they never put the work for that as well. Today it's half of the people I interview: they never got good enough to become a manager, and never become good enough to pass most interviews in the market of today.
On the other hand, I got a couple manager friends who love coding and are trying to become individual contributors, but keep getting pulled into leading projects because of their expertise.
Don't get me wrong, though, everyone wants to make money and have a good career, I just prefer working with a different kind of person.
Despite what you see on r/cscareeerquestions, if you tell anyone outside of tech that you work at a FAANG, they just shrug.
I was a hobbyist for 10 years before I got my first job. I was a short (still short), fat (I got better) kid with a computer, what else was I going to do?
But by the time I graduated in 1996 and moved to Atlanta, there were a million things I enjoyed doing that didn’t involve computers when I got off of work.
I’ll be in my 30th year next year. My titles might have changed but part of my job has always been creating production code.
I have never written a line of code since 1996 that I haven’t gotten paid for. It’s always been a means to exchange labor for money and before that, to exchange labor for a degree so I could make money
I figured out rather quickly to do the least amount of work, stay off the radar, do the cool stuff on my own time and saw my role as a corporate code jockey as nothing more than a way to pay my bills and keep a roof over my head.
All of my romantic ideas of being a developer, writing beautiful code and getting the pat on the back for such a great job? It all evaporated within the first two years.
Its just not worth it any more and you completely nailed it why.
I've seen a lot of this in younger engineers, too, but taken to such extremes that it's counterproductive for everyone.
"Resume driven development" is the popular phrase to describe it: People who don't care if their choices are actively hostile to their teammates, the end users, or anyone else as long as they think it will look good on their resume.
This manifests as the developer who pushes microservices and kubernetes on to the small company's simple backend and then leaves for another company, leaving an overcomplicated mess behind.
It's not limited to developers. One of the worst project managers I encountered prided himself on "planning accuracy", his personal metric for on-time delivery of tickets. He's push everyone to ship buggy software to close tickets on time. Even weirder, he'd start blocking people from taking next sprint's tickets from the queue if they finished their work because that would reduce his personal "planning accuracy" stat that he tracked.
We even had a customer support person start gaming their metrics: They wanted to have the highest e-mail rate and fastest response time, so they'd skim e-mails and send off short responses. It made customers angry because it took 10 e-mails to communicate everything, but he thought it looked good on his numbers. (The company tracked customer satisfaction, where he did poorly, but that didn't matter because he wanted those other achievements for his resume)
If the individual's focus is on short term income or career growth, then they align with the company's goals.
Solid engineering practices and product quality don't matter anymore (except in FOSS), and will likely be viewed as antagonistic to the KPIs, OKRs, or whatever metrics measure what is considered success.
Stated as someone who has been in various forms of IT since 1985, and has experienced most of software engineering turned into an MBA value extraction mindset. If you can't beat 'em, join 'em.
... which doesn't really matter anymore either as long as it's profitable, see Facebook, Twitter, Boeing...