---
title: How does software get shipped without breaking things?
url: https://varstatt.com/jurij/p/how-does-software-get-shipped-without-breaking-things
author: Jurij Tokarski
date: 2026-03-16
description: Continuous deployment, feature flags, monitoring from day one, and safe-to-fail design replace big-bang releases and lengthy QA cycles.
section: Blog (https://varstatt.com/jurij/archive)
tags: principles-faq (https://varstatt.com/jurij/c/principles-faq)
---

The traditional approach stacks up weeks of changes, runs a QA cycle, then deploys everything at once. When something breaks, it's buried in a pile of unrelated changes. The book describes a different model: deploy small, deploy often, detect problems fast, and recover in minutes.

[Continuous Flow](/principles/delivery/continuous-flow) replaces sprint ceremonies with a priority queue. No velocity tracking, planning poker, or batch releases. The developer works top-down from a ranked list, deploys each piece as it's ready, and moves on. Priorities shift? Reorder the list — no sprint replanning required.

[Feature Flags](/principles/delivery/feature-flags) decouple deployment from release. Incomplete work deploys to production behind a disabled flag. The main branch stays production-ready at all times. No long-lived feature branches, no merge conflicts piling up, no big-bang deployment day. When the feature is ready, the flag turns on. If something breaks, the flag turns off — surgical rollback, not full revert.

[Quality Gates](/principles/delivery/quality-gates) focus on safe-to-fail, not fail-safe. Preventing every possible bug requires massive overhead and still misses edge cases. The alternative: test proportionally to risk (payment flow gets more scrutiny than a settings page), deploy small changes that are easy to inspect, and invest in the ability to detect and recover quickly.

[Monitor Day One](/principles/diligence/monitor-day-one) means observability starts with the first deploy, not after launch. Error tracking, uptime monitoring, analytics, and performance metrics — all running before real users arrive. Launch week has the highest traffic and the most new bugs. That's exactly when visibility matters most.

[Production Is Done](/principles/delivery/production-is-done) closes the loop. Work isn't done when the code is reviewed or merged. It's done when it's live in production with monitoring confirming it works. This definition forces simple deployments — if deploying is painful, it gets avoided, and work piles up.