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 Continuous deployment: what changes when nobody presses the button

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

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

Big apps often hold features that already sit on their servers and stay invisible to every user. Why would a team put unfinished code into production on purpose, and how does it stay hidden?

  1. 1 Miva's waiting list is half done, and every merge now goes straight to production. She can stop merging for two weeks, as in the long branches of release day, or let half a waiting list reach the neighbours.Mivastop mergingfor two weekshalf a waitinglist goes live

    Miva's waiting list is half done, and every merge now goes straight to production. She can stop merging for two weeks, as in the long branches of release day, or let half a waiting list reach the neighbours.

  2. 2 She takes a third way. Her code goes to production every day, and still no neighbour sees a single button of it.productionwaiting-list codea neighbourthe usualapp

    She takes a third way. Her code goes to production every day, and still no neighbour sees a single button of it.

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 Rollback: how to undo a bad deploy in minutes

Share this comic

More comics