1 min lesson
Why review is the real bottleneck
Respond to "Why is review, not generation, the new bottleneck - and how does that reframe the whole anti-pattern taxonomy?" Name the reason and the detail behind it.
Step 1 of 2
Tie the whole taxonomy together with one mental model: with agents producing code at 10x-100x prior rates, the constraint is no longer generating code, it's reviewing it. There are far more PRs than humans can read line by line, so quality and review become where engineering effort and tooling investment belong.
The goal isn't to read faster. It's to read less, better: the human stops reading every line and instead reads a tight, agent-written summary, 'the agent generated 3M lines; here are the 7 things you, the expert, should decide on.' Every guardrail in this module exists to protect that scarce human review attention, which is exactly why volume-as-success is so corrosive: it celebrates the thing that is now cheap while ignoring the thing that is now scarce.
When a customer describes a mess, resist solutioning immediately. Name the anti-pattern first ('that's classic vibe-merging' / 'you've made coverage a target'), say who's losing trust, then prescribe the single guardrail. That sequence, name → trust impact → control, separates a field engineer from a feature-lister.
Strongest closing line: 'AI didn't break your pipeline. Skipping a discipline did. We put the discipline back - the PR stays the unit of trust.'