@@ 00 · blog @@
Notes from the pyor.
On the review bottleneck: why PRs got hard to read, how to review the big and the generated ones, and what a review surface owes you. We'd rather publish something worth your time than fill a feed.
@@ 01 · published @@
July 18, 2026Agentic code review: how review changes when agents write the codeAgentic code review means reviewing code whose author is a model: absent intent, tiered rigor by blast radius, and a human who still owns the merge.the agent era · 7 minJuly 18, 2026Greptile alternatives in 2026: an honest comparisonGreptile alternatives compared honestly: CodeRabbit and GitHub Copilot code review, plus Pyor, a review surface that triages the diff instead of commenting.the field · 8 minJuly 16, 2026Stop reviewing code on GitHubGitHub hosts your PRs; it was never built to review them. Why the default web diff is the wrong surface for review, and where to read code instead.a strong opinion · 7 minJuly 16, 2026GitHub Copilot code review alternatives in 2026GitHub Copilot code review alternatives compared honestly: CodeRabbit and Greptile go deeper, and Pyor takes a non-bot approach that triages the diff for you.the field · 8 minJuly 14, 2026What AI should (and shouldn’t) do in code reviewWhere AI in code review actually helps: upstream as a quiet pre-filter, humans downstream on a fast surface. Why Pyor ships no AI summaries, by design.our position · 6 minJuly 14, 2026Graphite alternatives in 2026: an honest comparisonGraphite alternatives compared honestly: GitHub native stacked PRs in private preview, CodeRabbit and Greptile for AI review, and Pyor as a review surface.the field · 8 minJuly 12, 2026AI PRs are burning out open source maintainersAI-generated PRs arrive in minutes; review still happens at volunteer speed. The data behind open source maintainer burnout, and what projects can do.the commons · 6 minJuly 12, 2026CodeRabbit alternatives in 2026: an honest comparisonCodeRabbit alternatives compared honestly: Greptile, GitHub Copilot code review, Graphite, and Pyor, a surface that triages the diff instead of commenting.the field · 8 minJuly 10, 2026Alert fatigue comes for code reviewAI review false positives don't just waste time; they teach your team to ignore the bot, real catches included. How to tune a reviewer for trust.the agent era · 5 minJuly 8, 2026AI code review tools: what they actually catchHow accurate is AI code review? Independent testing shows most suggestions duplicate linters, some are wrong, a few are gold. How to evaluate a tool honestly.the evidence · 6 minJuly 6, 2026Atomic commits make reviewable PRsStructure a pull request as a sequence of atomic commits and reviewers can read it like chapters. The craft of commit-by-commit review, and the squash debate.review craft · 6 minJuly 4, 2026Do code reviews actually find bugs?Do code reviews find bugs? Yes, but fewer than you'd hope, and that's not their main value. What the research says reviews deliver, and when they pay off.the evidence · 6 minJuly 2, 2026Re-reviewing a PR after changes: the interdiff problemHow to review changes since your last review: the interdiff problem, force-push pain, git range-diff, and commit-scoped diffs that keep threads intact.review craft · 6 minJune 30, 2026Nitpicks are killing your code reviewCode review nitpicking crowds out logic review, demoralizes authors, and slows merges. Automate the nits, label the rest, save attention for what matters.review culture · 6 minJune 28, 2026Author self-review: the cheapest code review you’re not doingSelf-review your pull request before requesting eyes: catch the cheap defects at the cheapest point and halve reviewer round-trips. A five-minute pass.review craft · 6 minJune 26, 2026LGTM culture: when code review becomes theatreLGTM code review can mean real approval or rubber-stamping. How LGTM culture drifts into theatre, and how to make approval mean something.review culture · 6 minJune 24, 2026Reviewing PRs locally vs. in the browser: when to pull the branchSome reviewers pull the branch to review pull requests locally; others live in the web diff. The real trade-offs, when each wins, and the third option.review craft · 6 minJune 22, 2026Stop losing review requests: fixing the PR review inboxReview requests die in GitHub notification noise. Build a PR query inbox with search filters, review SLAs, scheduled review blocks, and a real queue.team flow · 6 minJune 20, 2026AI writes code faster than you can review itAuthoring got 50% faster; reviewing didn't. Why the AI code review bottleneck is structural, what it does to teams, and the three places to attack it.the agent era · 6 minJune 18, 2026GitHub PR review alternatives in 2026: an honest comparisonGitHub PR review alternatives compared honestly: Graphite's stacks, Stage's AI chapters, Pyor's native surface, or just pulling locally. Which fits your team?the field · 8 minJune 16, 2026Reviewing AI-generated code: a practical checklistHow to review AI-generated code: a practical checklist covering intent match, hallucinated APIs, untested edges, security surface, and testing the tests.the agent era · 7 minJune 14, 2026How big should a pull request be?The research-backed answer on pull request size: under ~400 changed lines, smaller is better. Where the number comes from, when to break it, how to split.review craft · 5 minJune 12, 2026How to review large pull requests without losing your mindA practical, step-by-step method for reviewing large pull requests: triage the files that matter, review in passes, and keep your place in a 40-file diff.review craft · 7 minJune 10, 2026Why are pull requests so hard to review?Pull request review is slow because reading code is harder than writing it, and the tools make it worse. The four real causes, and what actually helps.the bottleneck · 6 min