While it's true you do hear a lot about "moving fast and breaking things" in software, I think that sentiment comes more from a business perspective than an actual software development one. I cant think of a programmer (at least any that I know personally) who would prefer to write the kind of shitty code one has to write to meet a deadline over code that is well designed and maintainable. I think in general the "move fast and break things" mindset is imposed by the need to deliver a good-enough product quickly enough to make money, and so that mindset becomes a disproportionately vocal one because the companies that adopt it end up with a product they can sell sooner.
Meanwhile the people who actually maintain the stuff are constantly tearing their hair out because they're always fighting the extra friction imposed by the technical debt that they traded for a lowered time to market. And the only way to continue to build on a foundation of brittle software is to break it some more. The cycle continues.
I point this effect out because while it's true that programmer culture is to blame to some extent because lots of programmers buy into the mindset, you can't just make it entirely a case of "lol fuckn techbros". You can and should blame techbros for a lot of things, I'm definitely not saying you shouldn't. But even if nobody in tech enthusiastically bought into the mindset of "move fast and break things" you'd still see people adhering to its premise because on a long enough time scale remaining competitive is impossible without doing so.