Browse the book & resources

Chapter 06 / 20

6. Engineering Quality & Reliability: Who Verifies and Recovers?

Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.

Imagine a reviewer receiving a cleanly written change that modifies access checks in three services. The tests pass. The risk lies in a permission boundary the author has not mentioned. The critical question is not whether a human clicked "approve"; it is whether someone could identify the unsafe case and had time to test it.

AI can draft tests, point out gaps, and summarize incident evidence. It can also produce code that looks familiar enough to invite shallow review. A team needs risk-proportionate checks: small changes with observable effects; tests that exercise the failure mode, not merely the happy path; a reviewer who understands the boundary; and a recovery path when a change escapes. The non-AI alternative might be clarifying ownership, removing flaky tests, or practicing rollback. Automation should make those controls stronger, not make them appear optional.

Be careful with attractive statistics about "AI correction." One open-source study of Claude Code–identified pull requests found that 214 of 475 merged agentic PRs had a later commit. That is a revision rate among merged PRs, not the proportion of all AI changes needing substantial correction. Revisions may be minor; rejected submissions and edits before opening a PR are not in that denominator. The study did not find a statistically significant difference in measured revision effort from its matched human PRs. A local audit needs a pre-agreed definition: behavior, security, or architecture altered to make a change acceptable, separated from formatting and added scope. Record who found the issue, who specified the fix, and who performed it.

Reliable operation continues after merge. Track customer-impacting incidents and SLOs, change failure, recovery time, and on-call burden, segmented by change risk. A stable incident count over a short pilot is not proof of improved safety; rare harms need a longer window and explicit tests of dangerous cases. Google's SRE on-call guidance makes rollback and escalation practiced skills, not merely text in a runbook. Some migrations or external effects cannot be undone by redeploying an old binary.

The reliability check: Sample recent changes, including rejected ones. Estimate review and correction labor without guessing at unseen work, examine one escaped defect, and ask whether your next proposed AI use makes detection, decision, and recovery easier for the person on call.

Sources cited in this chapter

  1. https://arxiv.org/html/2509.14745v3
  2. https://sre.google/workbook/on-call/

Browse all references →