This is trivially incorrect outside of SV.

There are plenty of slow moving projects that focus on the stability of the codebase if you work for a business that isn't a "tech company" and work on services instead of products.

indeed sweeping industry-wide conclusions are often drawn upon technology. however these generally apply to web/apps only. for example, in this thread we have someone extolling the virtues of not reviewing code. this is probably correct in the context of web/apps, but doesn't hold true otherwise. similarly the linked article talks about the frustration of being forced to merge known bad code - acceptable behaviour when the product is pictures on a screen, otherwise i have not observed this behaviour to be systemic

I wish it was easier to find this sort of business and work my way into one

I'm so tired of startups.