DEV Community

Jonathan Hall
Jonathan Hall

Posted on • Originally published at jhall.io on

Optimize for recovery time, not defect count

Regular readers of mine know that I’m a strong advocate for continuous deployment. But many teams are afraid of implementing CD for fear that more bugs might slip through than with a more manual process.

The problem with this concern is that it’s focused on the wrong thing.

The focus is on trying to reduce the number of defects that get released (formally known as Mean Time Between Failure (MTBF)).

A much more useful goal is to try to reduce the time it takes to fix defects when they do occur (formally known as Mean Time to Repair).

Why?

Even if we can reduce our defect count to, say, one per year, if reparing that one defect takes days or weeks, the impact will be severe.

On the other hand, if we can improve our ability to detect and repair defects to, say minutes, then the impact of even hundreds or thousands of defects may be minimal.


If you enjoyed this message, subscribe to The Daily Commit to get future messages to your inbox.

Qodo Takeover

Introducing Qodo Gen 1.0: Transform Your Workflow with Agentic AI

While many AI coding tools operate as simple command-response systems, Qodo Gen 1.0 represents the next generation: autonomous, multi-step problem-solving agents that work alongside you.

Read full post

Top comments (0)

Billboard image

The Next Generation Developer Platform

Coherence is the first Platform-as-a-Service you can control. Unlike "black-box" platforms that are opinionated about the infra you can deploy, Coherence is powered by CNC, the open-source IaC framework, which offers limitless customization.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay