Back to blog

What breaks when you treat code review as bug catching?

Thắng Đoàn
Thắng Đoàn

Your review process finds typos and edge cases, yet the codebase still gets harder to change every quarter. The problem may be what your reviewers think their job is.

Reviews exist to catch what tests cannot

Automated tests check whether code does what the author intended. They cannot tell you whether the intent itself was right. SmartBear explains that developers often lean on manual or automated testing while neglecting the human ability to see and correct mistakes in someone else's work. Per SmartBear, peer reviews catch the types of bugs that slip past testing and reduce later QA work. If your reviews only mirror your test suite, you are paying a human to do a machine's job.

  • Tests check intent; reviews check whether the intent was right
  • Reviews front-load defect finding and cut later QA load

Google's checklist is mostly not about bugs

Google's engineering practices guide lists what reviewers should examine: design, functionality, complexity, tests, naming, and comments. Most of those categories are about the next reader, not the current bug. Design asks whether the code fits your system. Complexity asks whether another developer could understand and use this code later. Naming asks whether names are clear. When a review only discusses functional defects, most of Google's checklist goes unchecked.

  • Design: does it fit the system
  • Complexity: can the next developer follow it
  • Naming and comments: is intent legible

How you comment decides whether the review lands

Google's reviewer guide includes dedicated sections on how to write review comments and how to handle pushback. That is telling. The technical content of a comment matters less than whether the author can act on it without a fight. Google frames its recommendations as coming from long experience, covering review speed, comment style, and disagreement. A process without those norms produces defensiveness, and defensiveness produces shallow reviews.

What this does not solve

These sources describe review process and priorities, not outcomes data. Neither Google's overview nor SmartBear's primer quantifies how much review quality affects delivery speed or defect rates for a specific team. They also assume reviewers have the time and context to judge design, which small teams often lack. If your reviewers are racing through large changes, a better checklist will not save you.

Which of Google's six review categories does your team actually discuss in pull requests?
Where does your review process assume reviewer time and context you do not really have?

Pull your last five merged pull requests and tag each review comment against Google's categories: design, functionality, complexity, tests,

Sources

Google Engineering Practices: Code Review Overview

Google: How to Do a Code Review

SmartBear: What is Code Review?

Share:

Recommended for you

Enjoyed this article?

Subscribe for new articles. No spam. Unsubscribe anytime.

By subscribing you agree to receive the newsletter. No spam, and you can unsubscribe anytime.