I also think they tend to be the older ones among us who have seen what happens when it all goes wrong, and the stack comes tumbling down, and so want to make sure you don't end up in that position again. Covers all areas of IT from Cyber, DR, not just software.
When I have moved between places, I always try to ensure we have a clear set of guidelines in my initial 90-day plan, but it all comes back to the team.
It's been 50/50: some teams are desperate for any change, and others will do everything possible to destroy what you're trying to do. Or you have a leader above who has no idea and goes with the quickest/cheapest option.
The trick is to work this out VERY quickly!
However, when it does go really wrong, I assume most have followed the UK Post Office saga in the UK around the software bug(s) that sent people to prison, suicides, etc. https://en.wikipedia.org/wiki/British_Post_Office_scandal
I am pretty sure there would have been a small group (or at least one) of tech people in there who knew all of this and tried to get it fixed, but were blocked at every level. No idea - but suspect.
Millions of boocampers and juniors trying to make a quick buck; any tech work that is not “make it, and make it quick” is punished; tech debt swept under the rug; any initiative is being shut down because status quo is more important; “we’ll optimize when it becomes a problem” on 15 seconds page reload; dozen of layers of parasites and grifters making your life hell, because their paycheck depends on it; salary bumps that don’t even cover inflation – the only way to actually move in life is to join, raise as much hell as possible in 2 years and jump ship leaving the fallout for the next SOB in the line.
And that’s just what I bothered enough to type on bad iOS keyboard.