Why we deploy 31 times a week
Small releases are boring releases. Here is the pipeline that lets our clients ship on a Friday afternoon without holding their breath.
(02) — The note
Written by the people who did the work. Numbers come from client analytics, shared with permission.
Big releases fail in big ways. We would rather ship something small every few hours.
Flags, canaries, rollback
Every change goes out behind a feature flag to 5% of traffic first. Dashboards watch error rates and latency, and a bad change rolls back automatically.
What it costs
A day of setup per project and some discipline about keeping pull requests small. What you get back is calm launches.
(03) — Keep reading
More from the journal
Process
7 min
How we quote a build in two weeks
A fixed quote needs a fixed scope. Here is the discovery sprint we run before we name a price, and what you get at the end of it.
Case notes
6 min
The checkout that paid for itself in a month
Fernloop's new checkout lifted conversion from 3.1% to 4.6%. The design was the easy part. Here is what made the numbers move.
AI
9 min
Evals before features: shipping AI that doesn't guess
We write the test conversations before we write the prompt. It's slower for a week and much faster for a year.