4 ms·

I had the privilege to work at a company that _actually_ had "blameless postmortems." That phrase is easy to say, but when you're on-call and get woken up at 3

I had the privilege to work at a company that _actually_ had "blameless postmortems." That phrase is easy to say, but when you're on-call and get woken up at 3 in the morning to deal with someone else's mess, let's just say "blameless" isn't _my_ first reaction. However--getting to the root of the issue, allowing everyone involved come up with solutions, and continuously improving the runbook is clearly the best way forward. Sure, it's reactionary, but proactive guidance is never going to be as imaginative in breaking things as production traffic.

tetha 3y ago
In a team of individuals, the term isn't necessarily "blameless". I'd never hold a weird or accidental outage against you personally. The major question would be: Why did that happen? However, you're forever going to be the fucking guy causing a database outage on Christmas. You might have had no choice, but fuck you. All of us have these scars. But then the question is: Why do we all have these scars? Maybe the system we're dealing with is not as great as it should be? Maybe the localized amount of anger is just a thing leading towards a more systematic problem. Oops, back into the ideas of blameless post-mortems.