@@ ✦ · series @@
AI and Code Review
Code generation got cheap; understanding stayed expensive. This series follows that inversion end to end: what AI reviewers actually catch, how to review code an agent wrote, what bot noise does to reviewer attention, and the division of labor that keeps a human owning the merge.
June 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.June 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.July 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.July 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.July 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.July 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.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.July 20, 2026Human on the loop code review vs human in the loop: pick one honestlyHuman in the loop gates every change before merge. Human on the loop code review samples and audits with authority to intervene. When each posture fits.July 24, 2026AI code change intent documentation: capture the why before the session diesAI code change intent documentation keeps the reasoning after the agent session ends: what was asked, what was chosen, what was rejected, what is untested.July 26, 2026When AI changes tests to pass, green CI stops meaning correctWhen AI changes tests to pass, green CI stops meaning correct. Why reviewers should read test diffs first and how to protect assertions from quiet rewrites.July 28, 2026Prompt injection is now a code review problemPrompt injection code review: how hidden instructions in READMEs, comments, and issues steer AI agents and reviewers, and a checklist for catching them.August 1, 2026Multiple AI code reviewers: when parallel bots help and when they just multiply noiseMultiple AI code reviewers barely overlap in what they find. When parallel review bots are worth the noise, and when one well-tuned reviewer wins.August 3, 2026Junior developers, AI code review, and the learning loop we are quietly breakingHow junior developers and AI code review collide: unclear ownership when agents write full PRs, and the norms that protect the learning loop.