Skip to content
Free since 2015. Built for the engineers who keep things running.

cat /articles/if-we-stop-reading-the-code-what-do-we-read.md

Platform Engineering

If we stop reading the code, what do we read?

Engineers who no longer read every line of AI-generated code still need a way to review it. The piece argues reviewers should focus on intent, acceptance criteria, and recorded decisions instead.

The New Stack21 Nov 2026 · 7 min read · summary

article --summary

The summary

The article starts from Robert Martin's admission that he rarely looks at the code his agents write, and notes that most teams have already stopped reading every line. He describes a diagram-based tool he uses to check structure, dependency direction, and risky complexity, which he calls a dynamic version of UML built after the code exists. The author argues that people who claim not to read code are usually still reading it in some indirect way, such as through tests, selective checks, or end-of-process review. He proposes that reviewers read three things: the intent of a change, acceptance criteria verified by a separate agent, and the human decisions made along the way. These also help the team keep a shared mental model of how the system works. The piece closes by saying that attention can shift away from code as confidence grows, but responsibility stays with the humans who merge the change.

Editorial note: This is a summary of an article first published by The New Stack. The full piece is on their site.

Reading now

Topic
Platform Engineering
Source
The New Stack
Published
21 Nov 2026
Format
Curated summary

Have a take on this?

Write it up and submit it. It goes on the list once an editor approves it.

Submit an article

articles --latest

Latest articles

New from the blogs we follow and the community.

All articles

newsletter --weekly

DevOps Weekly, minus the noise.

The best reads, new jobs and upcoming events, in one email a week.