March 16, 2026
Waiting is the real bug
Every layer of review makes you 10x slower
Engineers call it a bureaucracy boss fight; skeptics say it’s coordination, not code
TLDR: A tech leader claims each extra approval layer multiplies wait time by 10 and says AI won’t fix the queue—only fewer reviews will. Comments split: skeptics blame coordination, BigCo vets say the delays are real, AI fans tout throughput gains, and others push planning and sandboxing to cut risk and reviews.
A hot take lit up dev-land: add one more approval and your work gets 10x slower. The post paints a painfully familiar picture—30 minutes to write a fix, then five hours waiting for a code review, a week for a design sign‑off, and a quarter just to get on another team’s calendar. AI? The author says it won’t save you from the queue; it’ll just write code faster so it can wait longer.
Cue the flamewar. Power commenter tptacek rolls in with a reality check: five hours to review a pull request (a “PR,” basically a code change) is bogus—this feels like coordination chaos, not reviewers napping. Over in BigCo land, abtinf backs the “10x per layer” lore with grim vibes: manager approval takes a day, second level takes ten, third level is “at least a quarter.” That’s not a workflow, it’s an approval volcano.
Meanwhile, markbao is waving the AI flag: even if reviews still crawl, saving build time means you can stack more PRs and boost throughput—“good lord, get used to doing more.” Others pivot the blame to planning: sublinear says better requirements upfront beats frantic “show progress” theater. And simonw proposes a plot twist—sandbox risky code so the worst outcome is bad output, not a meltdown, and shrink the review blast radius. The comments turned a slow queue into a meme: “calendar Tetris,” “boss fights,” and the “Mythical Mammoth” of coordination hell.
Key Points
- •The article asserts a rule-of-thumb: each additional approval layer increases wall-clock time by roughly 10×.
- •Examples given: 30 minutes to code a simple fix, ~5 hours with peer review, ~1 week with design doc approval, and ~12 weeks when coordinating with another team.
- •At executive levels, changing product direction can take multiple quarters, reflecting compounded approval delays.
- •AI-accelerated coding (e.g., via assistants like Claude) does not address review and coordination wait times, which dominate total duration.
- •The author concludes that the only sustainable way to speed up delivery is to reduce the number of reviews/approval layers.