Ha, yea. I can get behind this. There are times that one dumb thing causes the entirety of my tests to crumble and I'm always admittedly laughing saying "that's why we have tests!"
I also favour responding to mistakes quickly over preventing them completely.
I've seen a lot of teams where there was the one keeper of the systems who knew how to do all the deployments and migrations. In every situation they became a bottleneck for the team, and prevented any real improvements being made.
Even at my last role people would get angry at me when I'd ask for "command confirmation" and/or "an extra sets of eyes".
In my world, I favor getting it right vs. responding to mistakes. It's the difference between "scalable" and "firefighting".
Having a SPF asset who holds the keys to the entire kingdom is a completely different problem, and a different conversation.
Some people work more carefully than others. This is absolutely a thing in software development/operations (my fields). When I was young, I had more screw-ups because I was still learning "how to work carefully" with certain things... It's hard for me to admit this but it is 100% the truth. When things went wrong, I felt the need to take it on my shoulders vs. to put it on the rest of the team who likely had nothing to do with the error.
As with all things this isn't black and white, which is why I'm making this comment.