Quality and going live safely
The client remembers the day it broke, not the day it was built.
Going live means real users, real money and real data. Companies use a simple discipline so that a release is boring, which is exactly what you want.
| Before release | Why |
|---|---|
| Test on a staging copy, not the live site | Mistakes stay away from real users |
| Take a backup of database and files | You can undo a bad release |
| Use a checklist: forms, payments, login, mobile view | Nobody remembers everything under pressure |
| Release at a quiet time, not late Friday night | People are available to fix problems |
| Know how to roll back | Five minutes of downtime instead of five hours |
| Watch logs and errors for an hour after | Catch problems before the client calls |
After every incident, teams write a short note: what happened, why, how it was fixed and what will prevent it. No blame, only learning.
๐ญ What would you do?
It is 7 pm. Your fix works on your laptop. The client wants it live tonight.