Skip to content
AtomicReps
The Retrieval · Issue 08

The catch block that kept the build green and lost 5% of the data.

Green build for three weeks. Then 5% of the rows were just gone.

The track
Writes code
The rep
About thirty seconds
Published
September 2, 2026

The Exhibit

Two things are both true, and the gap between them is where that lost 5% lives. A randomized trial of 1,974 developers measured about 26% more throughput with AI on scoped tasks. The trial. And the 2025 DORA report found AI amplifies what is already there: strong teams improve, weak spots get exposed faster. The report.

Put together: AI multiplies, it does not originate. It scales your existing judgment, in both directions. Faster execution on top of a shaky mental model is a shaky mental model shipped sooner.

The study

Comprehension Debt

Comprehension debt: the gap between what gets shipped and what the team can still reason about.

The thing being multiplied is the only thing worth protecting: your ability to reason about what you are shipping. Lose that and the speedup stops being yours, it is just the tool's output passing through you on the way to production. Keep it, and the same multiplier compounds in your favor.

The idea

The Rep

Thirty seconds:

A flaky call kept throwing, so you wrap it in try/catch and log the error so the pipeline stays green. Weeks later a report is quietly missing 5% of its rows. What went wrong?

The answer

Catching and logging is not handling. The exception was a signal that a unit of work failed; swallowing it converted a loud failure into a silent one, and the in-flight work (the rows that call was supposed to fetch or write) just vanished with no retry, no dead-letter, no alert. Green build, missing data. The fix is to decide per failure: retry with backoff if it is transient, route to a dead-letter queue if it needs later handling, fail the batch loudly if partial results are not acceptable, and alert on the log line instead of trusting someone to read it. An empty or log-only catch is a decision to lose data quietly. Make the decision on purpose.

About thirty seconds

Start the sequence

You read this one out of order. Start at issue one.

Subscribe and the sequence begins at the beginning, whichever issue brought you here.

Which track

One confirmation email first. Nothing else until you click it.