Skip to content

blog: add "Stop reading the diff. Review the assumptions." - #415

Open
adamaltman wants to merge 1 commit into
mainfrom
aa/review-the-assumptions
Open

blog: add "Stop reading the diff. Review the assumptions."#415
adamaltman wants to merge 1 commit into
mainfrom
aa/review-the-assumptions

Conversation

@adamaltman

Copy link
Copy Markdown
Member

What/Why/How?

Adds the blog post "Stop reading the diff. Review the assumptions." at blog/review-the-assumptions.md.

The post makes these points:

  • Line-by-line review was the only checker when humans wrote every line. Agents write the lines now and agents can read them. A human who reads the same lines after the agent is a slower duplicate checker with a queue in front of it.
  • Machines cannot review assumptions. A wrong assumption costs more than any bug. A wrong data model or interface lives for years.
  • Humans must review the assumptions before the code exists. In writing, one claim per line, each marked verified or unverified. If the first review of the premise happens in the code PR, it is too late.
  • In the PR, humans review the interface, the intent, and the safety envelope. Not the lines.
  • Exception: tenant boundary, auth, billing, and deletion still get a human code read.
  • Review closes after ship, when the biggest assumption gets marked true or false.

Frontmatter follows blog/rise-of-parallelism.md. The header image is a new generated PNG at blog/images/review-the-assumptions.png. publishedDate is set to 2026-09-17, one day after the parallelism post.

Open questions for review:

  • Categories. No category in blog/metadata/blog-metadata.yaml covers how we work with agents. The post uses the same pair as the parallelism post. Suggest a better pair if one exists.
  • The H1 ends with a period, so the file carries a markdownlint-disable-next-line MD026 comment. Remove it if the title changes.

Reference

  • Companion post: blog/rise-of-parallelism.md (PR blog: Multitasking is dead. Parallelism is rising. #413). That post says review the pitch, not the flight. This one says what the review of the pitch looks like.
  • Internal code review SOP: docs/intranet/engineering/sops/code-reviews.md in the monorepo. The post argues against its strict rule.

Testing

  • markdownlint-cli2 --config .markdownlint.yaml blog/review-the-assumptions.md passes with 0 errors.
  • The image is 1200x630 PNG, 34 KB.
  • Preview build: check the rendered post, the header image, and the blog index after the preview deploys.

Screenshots (optional)

Header image: blog/images/review-the-assumptions.png

Check yourself

  • Code is linted
  • Tested
  • All new/updated code is covered with tests

Security

  • Security impact of change has been considered
  • Code follows company security practices and guidelines

🤖 Generated with Claude Code

Add a blog post on where human code review belongs now.
Agents write the lines and agents can check them.
Humans review the assumptions, and they do it before the code exists.
The PR review moves to interface, intent, and safety.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

@redocly redocly Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

marketing-site AI Review: 🟢 Completed

Redocly Agent has reviewed your changes and found 1 potential issue(s).

Note

Low Risk

Adds static content (a new markdown blog post and header image asset) with no impact on application runtime logic, APIs, or core infrastructure.

Overview

Adds a new blog post at blog/review-the-assumptions.md titled "Stop reading the diff. Review the assumptions.", which explores evolving code review practices in AI-assisted workflows by shifting human review focus from line-by-line diffs to pre-code assumption validation, interface design, safety envelopes, and post-ship outcome verification.

Also introduces the associated blog post header image asset at blog/images/review-the-assumptions.png.

It waits.
A reviewer opens it, reads three hundred lines, leaves four comments about naming, and approves.
Two days passed.
Nothing about the change got safer.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Severity: Low

The verbs abruptly shift from present to past tense in the pull request scenario ("Two days passed. Nothing about the change got safer."). Use present tense ("pass", "gets") to maintain consistency with the preceding sentences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant