Home / Lessons / Judge the result / 15 of 27

What happens after the code works

Working code starts the delivery. It does not finish it.

ApplicationDatabaseCode works locallyFeature branchPull requestAutomated checks (CI)Preview environmentIndependent reviewMy mergeAutomatic deployment (CD)Live verificationReal usersAdditive migrationChecked on atest databaseMy approvalfor productionProductiondatabase readyDeployment is not proof.The live check is aseparate step.

normal movementretry or blockedmy decisionwritten, shared statestopped

The application travels one path: a feature branch, a pull request, automated checks, a preview environment, independent review, my merge, automatic deployment, live verification, and then real users.

Database changes travel a second path: an additive migration, verification against a test database, my approval for production, and confirmation that production is ready. The two paths join before the merge.

Deployment is not proof. Checking the live system is a separate step.

How I do it

CI is the automated checks on the proposed change. CD is the automatic deployment after I approve a merge.

The rule

Treat "it works here", "it is deployed" and "it works for users" as three different claims.

The skills I use for this: /gstack-land-and-deploy, /gstack-canary. Made by Garry Tan.

Read next

The ideas behind it

This lesson as plain text, for your agent. Or all 27 on one page.

Try “secrets”, “merge”, “handover” or “database”.