The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
While I think this is true for the most part, it also largely depends on your line of work. My software runs machines that produce a LOT of product every day. I hear about nearly every hiccup it has because it costs the company money and that is very consequential to a lot of people and their wallets. Me included.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
Yeah that makes sense. It was more of a general point, I think there is still some areas where software needs to be perfect, such as financial and medical etc. just because the liability of error is too great.
Any company, or person, who has "we/I are/am passionate about <insert relevant item here>", is not. If they really were, then it would show in the quality of their products and they would not need to crow about it. It is almost as stupid as the recorded message you hear while waiting to connect to customer services, which repeatedly says, "your call is important to us".
It's mostly about quick and painless release cycles.
Have a bug? Fix and roll out, you'll be back in business in a couple of minutes (in theory, practice learns that bugs are piling up, business wants new features, and the work around is somewhat acceptable ).
What's more, you either write code that works and won't be touched for the next ten years or you're constantly writing on the same code base.
There doesn't really seem to be an in between.
In fact, businesses are changing so rapidly that I've read articles telling me to write code that can be thrown away and replaced because it'll probably be obsolete in a few months or even weeks anyway.
Add to that, that new languages, tools and (versions of) frameworks are released almost monthly.
If you started programming in 2015 you wouldn't even have a chance to really learn any language well because you've probably switched everything three times already.
To give but an example, in 2015 I was working with Knockout.js, which was replaced with Angular, after which came AngularJS (and don't forget TypeScript either!) which was to bloated so people started doing React and Vue.js instead (there have been some others as well, like Ember and Aurelia).
Heck, I just googled "front end frameworks" and out of the top five on some websites I only knew Bootstrap, back in 2017 (yes, only two years ago) I knew them all!
You may have switched from .NET to .NET Core, which isn't too big of a change, but in school you probably did Java. Oh, and now your boss wants Node.js too!
Perhaps you hopped on the mobile hype train so you're doing... PhoneGapXamarinIonicKendo UI, heck what are kids using these days, Swift?
In database land everyone wants MySQLSQL ServerPostgreSQLRedisMongoDB some multi-model DB that has them all, like Cosmos DB.
For DevOps, which is pretty hot, the choice is easy JenkinsBambooTeamCityGitLab... Myself, I stick to one tool only TFSVSOVSTS Azure DevOps!
Well, at least my package manager stayed the same... NuGetBowernpmWebpackYarn NuGet again.
And don't forget everything has to be cloud nowadays, AWS or Azure, although businesses are starting to use Google Cloud as well (at least that choice is limited).
No kidding, I've seen, not used, and considered all of this (and MUCH more) at some point since 2015, a four year period!
Now here's the good news, companies can't hire specialists for each language, tool or framework, so you have to be "full stack" and know them all!
Just when I get familiar enough to deliver quality the full stack changes
And don't try to find a job that uses just the tools you know either, it's impossible!