@@ ✦ · 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.
Coming July 8, 2026AI code review tools: what they actually catch
Coming July 10, 2026Alert fatigue comes for code review
Coming July 12, 2026AI PRs are burning out open source maintainers
Coming July 14, 2026What AI should (and shouldn’t) do in code review
Coming July 18, 2026Agentic code review: how review changes when agents write the code
Coming July 20, 2026Human on the loop code review vs human in the loop: pick one honestly
Coming July 24, 2026AI code change intent documentation: capture the why before the session dies
Coming July 26, 2026When AI changes tests to pass, green CI stops meaning correct
Coming July 28, 2026Prompt injection is now a code review problem
Coming August 1, 2026Multiple AI code reviewers: when parallel bots help and when they just multiply noise
Coming August 3, 2026Junior developers, AI code review, and the learning loop we are quietly breaking
Coming November 15, 2026You should read the code, not the AI summary