You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Feature flags: how unfinished code goes live without anyone seeing it

How CI/CD works: why releasing code every day is safer than once a month

Rollback: how to undo a bad deploy in minutes

A new version of an app goes live, and nobody can use it. Hunting for the bug can take hours, while every user waits. The fastest teams do something else first, and it only works because they keep every build.

  1. 1 Thursday, 15:10: build 81 is on production, and every booking fails. In the laundry room, a neighbour with a full basket stares at the phone.15:10build 81 on productiona neighbourBookingfailed

    Thursday, 15:10: build 81 is on production, and every booking fails. In the laundry room, a neighbour with a full basket stares at the phone.

  2. 2 Finding the bug, fixing it and sending the fix through every stage could take an hour or more. That is an hour with no laundry for anyone.find the bugfix itbuildevery stagean hour or more

    Finding the bug, fixing it and sending the fix through every stage could take an hour or more. That is an hour with no laundry for anyone.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode DORA metrics: why teams that deploy more often break less

Share this comic

More comics