~/$ mbaurin's blog

the firefighter rotation that changed how i see production

8:23am. slack notification: "Urgent, seller paid yesterday but cannot access anything."

i am the firefighter for the day, first responder for production issues during business hours. one seller, one access issue. should be simple.

it was not...

the cascade

within 20 minutes, one issue becomes five:

this is overstimulation in production. not one bug, five people asking five different questions while you are still figuring out what broke.

the breakthrough

i cut the noise. got 20 uninterrupted minutes.

the pattern emerged: yesterday's deployment changed user provisioning. payment worked, but the webhook triggering access was failing silently due to new validation rules.

fix was straightforward. finding it required focus.

crisis resolved. but those 20 minutes taught me more about production ownership than months of feature development.

what changed

before firefighter rotation, seller issues felt distant. after ? every seller became personal.

i started building error messages and admin tools into features from day one, not because someone told me to, but because i knew i would be explaining failures at 8 am.

webhook failures got retry logic. payment success without feature access became impossible, not an edge case. "technically correct" became "seller friendly."

the real lesson

ff rotation creates shared accountability. when you know you will debug your teammate's code at 8 am, code reviews get thorough. when they will explain your feature's failure to angry customers, you write better error messages.

customer empathy becomes real when your code decisions affect real businesses spending real money.

two months later, my phone still buzzes at 8:23am. but now i'm ready, with better error handling, clearer feedback, and a seller first mindset.

from feature developer to seller advocate. from "technically works" to "actually works."