#reliability
Every post tagged "reliability".
124 posts · showing 51–60
-
When a Worker Returns Garbage: Validating at the Handoff
Thirty-nine extracts were fine. The fortieth had every field present, correctly typed, and null — and the supervisor aggregated it, because well-formed looked like correct.
-
The Timeout That Looked Like an Empty Result
The health check timed out, the handler returned an empty list, and the agent reported all clear while two services were down. An empty result and a failed check must not share a shape.
-
Positions Worth Revising About Agents
Eight beliefs that are reasonable on their face and don't survive production. Every correction points the same direction — which makes it a useful prior for the next problem.
-
The Second-System Effect in Agent Deployments
The first agent works because it was scoped well. The second aims at exactly the cases the first one escalated — which is the residual that resisted automation for structural reasons.
-
When to Stop Improving an Agent
There's always another failing case, so without a stopping rule the work either never ends or ends arbitrarily. The signal isn't the error rate — it's effort per point of improvement.
-
The Documentation Problem Agents Create
Documentation has two audiences with different needs, and generated docs that restate the code become negative value the moment they drift — a confident wrong answer with an authoritative source attached.
-
Why Your Codebase Will Grow Faster Than Your Understanding
Writing code built understanding as a byproduct, which is why "the team knows the system" used to be true without anyone planning it. That coupling broke and only one of the two rates changed.
-
Data Work Gets More Valuable, Not Less
The buffer between bad data and consequences was a person who noticed the number looked wrong. Agents act on it — which turns data quality from an analytical property into an operational one.
-
What Happens to QA When Agents Write the Tests
Cheap test generation makes suite quality matter more, not less — because the default outcome is a large, green suite that verifies nothing. Someone has to own whether it catches things.
-
Evaluation Engineer: The Job Description Writing Itself
The furthest-formed of the emerging roles: well-defined, consistently needed, consistently unstaffed. It's everyone's dependency and nobody's job, which is exactly why.