Took down checkout for nine minutes in my third month and the retro barely mentioned me
Merged a config change on a Friday morning that pointed a service at the wrong queue. Alerts went off and someone rolled it back before I'd even worked out what I'd done.
What I keep coming back to is the retro. I walked in ready to apologise for twenty minutes and the entire conversation was about why that config had no validation and why the rollback took six minutes instead of one. My name came up exactly once, as "the person who found the gap".
Still felt awful for two days. But nobody treated it like a character flaw, and I don't think I'd understood that was possible.
2 comments
- 0
AnonymousAnon Worth noticing that your manager did something quite deliberate there. Steering a retro onto the missing validation instead of the person is a skill, and plenty of managers don't have it. Might be worth remembering when you're the one running the retro in a few years.
- 0
AnonymousAnon The "blameless" thing sounds like corporate wallpaper right up until you're the one in the room. Mine was a migration that locked a table for eleven minutes. Same shape of retro, and I still apologised twice before someone gently told me to stop.