Employer making me choose between career advancement and LOB success and then tying my job security to the latter.
I usually have comparable or better options available at any given time due to the sheer number of recruiters who are constantly floating things my way.
An up-to-date, relevant skillset is worth a potential 5 figure pay bump in the near future, which tends to be much more lucrative than slightly increased job security at my current pay rate.
They usually get one screw-up before I skip out for a better paying gig.
Fool me once, shame on you. Fool me twice, shame on me.
Have more than tripled my salary in the last 6 years hopping around like this.
But honestly, I'm also just not a fan of management styles which attempt to extract additional value via appeals to fear.
Usually if I see workplace management react to crunch time by letting shit roll downhill while making negative implications about how resistance might impact job security, that instantly puts me in job hunting mode.
I might stick around for a bit to help out people on my team that I actually like, but at that point I'm already mentally checked out and looking for my next gig.
If you're not a scrub, go through non-scrub recruiters, and manage to get through a handful of high-vis projects relatively unscathed, word travels extremely quickly and from then on out you can pretty much coast mostly on reputation.
What I'm hearing you say is that the rapid increase in flexibility of choice within the JS ecosystem has a tradeoff of enabling dilettantes to further muddle the mixture.
I would argue that we should not be intentionally relying on technical design decisions to bust through difficulties which are more related to human factors and office politics than software architecture or implementation.
Having an extra negative 400 to 500 calorie offset on a daily basis can be incredibly helpful considering a lot of creeping weight gain is caused by a caloric surplus of only a couple hundred per day.
A sound card w/ decent surround sound features (Creative <3), noise cancelling headphones, and good map awareness & position play gave me a far higher KDA in CS 1.6 and Source than practicing with the AWP til my eyes and fingertips bled.
The Shift key became infinitely more useful once my ears acclimated to the setup change.
In many ways it's not so different than billiards/snooker/pool. Being a good shot-maker helps but just about all the consistently performing pros focus first and foremost on position-play and thinking several shots ahead.
Why would you use parseInt over Math.round if you only expect a single arg?
Seems like you'd only want to use parseInt if you expect to need radix changes at some point, e.g. converting between hex strings, decimal values, and binary strings
Maybe their target audience doesn't primarily consist of entry-level devs relegated to maintaining legacy eCommerce web properties and back-office portal/intranet systems?
Keeping that "Just buy a shitload of cheap-o eBay 2U/4U hand-me-downs" workflow viable for years to come :D