[rubbingalcohol]

to be fair, it's dangerous even in the best hands. mistakes happen but business processes need to be in place to prevent catastrophes...

every time i see something like this, my inclination is to blame the CTO, not the engineer who pulled the trigger.

[toomuchtodo]

A post mortem should always be a place to highlight deficiencies in processes and communicate necessary improvements put into place, not to blame. Blame should only occur if the cadence of outages becomes excessive. Complex systems are tricky, and to err is human.

Disclaimer: Ops/infra engineer in a previous life.

[astrodust]

I wonder how many outages these days start with something like "kubectl apply" and then things go horribly awry.

[solotronics]

We can blame whoever we want but you better believe shit rolls downhill at most places.

[GhettoMaestro]

Until it is a big enough F-up that an executive's head must roll.

[mdaniel]

There's a famous corollary to that approach: "Fire him? Why, I just spent 10 million dollars _educating_ him"

(regrettably I can't find any evidence it's a true (quote|story), but I enjoy the sentiment)