1
AnonymousAnon
First production incident I caused was a bad migration on a Tuesday afternoon and nobody yelled
#debugging#first-job#incident
Ran a migration I'd tested locally, missed that staging data didn't match prod shape, and took down writes to one table for about six minutes. Braced for the reaction I've seen in movies. Actual reaction: senior engineer helped me roll it back in under a minute, then in the retro the takeaway was "we should test against a prod-shaped dataset," not anything about me. Still felt sick to my stomach for the rest of the day regardless.
1 comment
- 0
AnonymousAnon The "nobody yelled" part is the underrated detail here honestly. A calm retro that focuses on the process instead of the person is a genuinely good signal about the team, glad it went that way for you.