Rollback

Shipping the broken version is not the disaster. Not being able to undo it fast, that's the disaster. A rollback is the undo button for your live app.

When we covered deploy, it was the doors opening and the audience walking in. Sometimes opening night is a mess. The new version is broken and real people are hitting it right now. The panic move is to try to fix it live while everyone watches you sweat. The professional move is to put last night's working version back up instantly, then go fix the broken one in private.

Reprinting last night's menu. A restaurant prints a fresh menu every evening. Tonight's has a typo: wrong prices, a dish that doesn't exist, confusion at every table. You don't freeze the dining room and rewrite the menu from scratch while guests wait. You grab last night's menu, the one you kept, and hand it back out in thirty seconds. Service keeps moving. You fix tonight's version after close, calmly.

That's a rollback: instantly switching the live app back to the previous version that worked. The reason it's fast instead of a rebuild is the thing you learned with Git and commits. Every version is already saved. You're not recreating last night's menu. You kept it. You're just handing it back out.

This is the line worth holding onto, because it sounds like a Git rewind and isn't. A Git rewind happens in your workshop. You walk your code back to an old snapshot while you build. A rollback happens at the storefront. You flip what the public is currently hitting back to the last good version. Same instinct (every version is saved, so return to a good one), two different stages of the journey. One's where you make the thing, one's where customers use it. That five-minute fix on our Android app I told you about when we covered Git? That was this exact instinct in action.

And it's the whole reason you can ship without holding your breath. Deploying stops being terrifying the moment undo is one button. You're no longer promising the new version is flawless. You're promising that if it's not, the audience sees the mess for sixty seconds and then the good show is right back up. Modern hosts make it literally a click. Vercel and most platforms keep your recent deploys ready to restore, and some flip back on their own the instant a new version starts throwing errors.

Shipping isn't brave because you're certain. It's brave because rollback turns a bad version into a sixty-second problem instead of a lost night.