Getting It to Users — and Taking It Back
Two Copies from Here On
Until now there has been one copy of the booking page, and you have edited it the way you would edit a document: change it, look at it, change it again. The day the first real booking lands, that era ends. From here on there are two copies. One is the copy customers use — the one a dog owner may be halfway through booking on right now. The other is the copy you change, somewhere customers aren't. The rule is simple and worth saying plainly: you never change the thing people are standing on. If you edit the live page on a Tuesday afternoon and get it wrong, a customer meets your mistake before you do. Keeping a separate working copy costs almost nothing, and it removes an entire category of bad afternoon before any of them can happen.
- From the first real booking onwards, there are two copies: theirs and yours
- Make changes where customers aren't — never on the page people are using
- Editing the live thing means customers meet your mistakes before you do
- A separate working copy removes a whole category of bad afternoon
Shipping Is a Decision, Not an Accident
Once there are two copies, "shipping" stops being a mysterious engineering word. It just means moving a change from your copy to theirs — deliberately, at a moment you chose. That last part carries most of the value. You choose the moment: a quiet Tuesday evening, not a Saturday morning while the diary is filling. You choose what goes: one small change you can describe in a sentence, not a month of accumulated edits travelling together. And you look afterwards: make a booking yourself, watch the confirmation email arrive, glance at the page on your phone. None of this is technical. It is the same care a groomer takes before handing a dog back — a deliberate check at a chosen moment, rather than a hope. The habit costs minutes each time, and it is the difference between shipping and gambling.
- Shipping means moving a change from your copy to the customers' copy
- Choose the moment: a quiet Tuesday evening, not a filling Saturday diary
- Ship one change you can describe in a sentence, not a month of edits
- Look afterwards: book a slot yourself and watch the confirmation arrive
Rollback: Taking a Change Back
Some changes will be wrong. Not might — will. You will ship something that looked fine on your copy and misbehaves on theirs, because the live copy has real data, real phones and real people doing things you never pictured. Rollback is the answer, and it is a product feature rather than an admission of failure: the ability to put back the last version that worked, quickly, while you think. The difference between a bad five minutes and a bad weekend is usually just whether you can do this — and whether you knew the steps before you needed them. If Vibecoding taught you to save a working copy after every good step, this is the same habit one level up: the saved copy now lives on the platform, and putting it back is a button you have already pressed once, calmly, in advance.
- Some shipped changes will be wrong; plan for that rather than hoping
- Rollback means putting back the last version that worked, quickly
- Knowing the steps in advance separates a bad five minutes from a bad weekend
- It is Vibecoding's saved-copy habit, one level up and living on the platform
Prefer slides, quizzes, and saved progress? Read this lesson in the library — free, no sign-up.