That's true but that is to offset the really negative aspects. How many places never let dev's actually design systems that stand up to scrutiny because the execs don't care if BS is pumped out because as long as the business floats then it doesn't matter.

Then the code base becomes a mass of spaghetti that at this point the revolving door of devs have to both figure out and keep alive in ever increasingly stressful situations until they either burn out or move on for greener pastures perpetuating that cycle.

So far in my career the split is 60:30:10 places who don't care about actual engineering and run their business on crap, those who recognized things are biting them but the amount of inertia you need to counteract things and rebuild is huge and then the very fine percentage of places that actually have a good culture around engineering.

The first is horrible because you're a fungible asset and the job is miserable the second is better but still bad because at this point they do see you as valuable but you're going to be spending your time digging them out of a grave and then the third is just a magical experience where you're valued and the codebase isn't constantly a light breeze away from collapsing.

The majority of the industry is in position 1 and I guess we'll see if it ever makes it to 2 or 3.

Worth noting that I made high salaries and could work from home in every case but it would be correct to say I continue to enjoy programming in spite of the industry.

I also don't think it's a coincidence that companies who are in group 3 are typically leagues ahead of 1 and 2.