@mattpocockuk: The "should you read code" debate is dumb because the real decision isn't binary, it's a scale: 1. Reading every line o…

X AI KOLs Following News
code-review developer-workflow ai-assistance

Summary

Matt Pocock argues that the decision to read code during code review is not binary but a spectrum, listing seven levels of engagement from reading every line to letting models handle everything.

The "should you read code" debate is dumb because the real decision isn't binary, it's a scale: 1. Reading every line of every diff 2. Scanning every diff, reviewing important lines 3. Ignoring diffs but understanding the 'why' of every PR 4. Spot checking PR's instead of reading every one 5. Ignoring PR's, but doing regular spot checks on the codebase 6. Ignoring the code, but spot checking agent traces to help improve the system 7. Ignoring both the code and the system, let models handle everything Where are you on the scale?
Original Article
View Cached Full Text

Cached at: 07/05/26, 10:30 AM

The “should you read code” debate is dumb because the real decision isn’t binary, it’s a scale:

  1. Reading every line of every diff
  2. Scanning every diff, reviewing important lines
  3. Ignoring diffs but understanding the ‘why’ of every PR
  4. Spot checking PR’s instead of reading every one
  5. Ignoring PR’s, but doing regular spot checks on the codebase
  6. Ignoring the code, but spot checking agent traces to help improve the system
  7. Ignoring both the code and the system, let models handle everything

Where are you on the scale?

Similar Articles

Reviewing code requires reading

Lobsters Hottest

A developer blog post argues against the idea of shipping AI-generated code to production without reading it, emphasizing that code review serves critical purposes: diffusing responsibility, reducing bus factor, and maintaining team knowledge of the codebase.