It's true. For almost all of my career I've worked in the software equivalent of a lab building a diamond making robot. I did a stint at a consulting firm -- that was more like coal mining than manufacturing gemstones. By this I mean never ending surface area, and very little incentive to ever go back and refactor anything.

For most orgs, code isn't the end product. Code is the way to build the product to sell to the user.

Therefore, in most orgs, code architecture/style is a distant secondary to 'does it achieve what the user will pay money for' and 'why isn't it finished yesterday?'.

"I'm sorry Dave...I can't do that"