Teams are using different model families for code review to catch blind spots
desilvakai · reddit · 2026-07-24
A pair of founders describe a code-review setup where one AI agent writes changes, a different model family reviews them, and a third model runs an adversarial pass before a human merges the code.
Their key point: review is most useful when the reviewer is meaningfully different from the writer, because a reviewer that uses the same base model often inherits the same blind spots and simply agrees with the original mistakes. The downside is cost: the reviewer has to rebuild context from scratch by pulling the branch, rerunning tests, and re-deriving the reasoning. They ask how others make this pattern cheaper at scale.
More from coding & agent
- Uncle Bob says he trusts agents only after tests and constraints, not by reading their code — tokenbender · 2026-07-24
- Codex bypassed a hidden anti-bot honeypot while a human got blocked — corbtt · 2026-07-24
- MinHash Pitfalls: Developers Discuss Using LLMs to Review Tricky Code Bugs — giffmana · 2026-07-24
- PenguinHarness lets TypeScript agents create and improve other agents — RepulsiveBad8681 · 2026-07-24
- ConFuse adds a shared context layer for coding agents across repos and docs — Loud-Two-408 · 2026-07-24
- DSPy and GEPA users often write custom proposers to reduce overfitting — dbreunig · 2026-07-24