It Happens to Everyone
You pushed. The pipeline went green. You opened the site to admire your work — and it's a white screen. Or a 500. Or the checkout button silently does nothing. Your heart rate doubles, because this isn't localhost anymore. Real users are looking at your broken deploy right now.
Here's what nobody tells beginners: every developer you admire has broken production. What separates seniors from juniors isn't avoiding it — it's having a calm, rehearsed answer to "what now?". This post is that answer: how to get back to the last working version fast, the one database trap that turns a bad evening into a disaster, and the five-point contingency plan that makes the next incident boring.
Rule Zero: Restore First, Diagnose Later
Your instinct will scream "find the bug and push a fix!" Resist it. Debugging under pressure produces bad code, and a rushed "hotfix" is how one outage becomes two. The professional move is boring:
