Summary
Was this newsletter forwarded to you?Sign upto get it in your inbox.The bug report was deceptively simple: A user noticed that their email signature formatting was off inCora, our AI-powered email assistant. I asked Claude Code to investigate and fix it. By morning, the fix had touched 27 files, and more than 1,000 lines of code had changed. I didn’t write any of them.A year ago, I would have spent my afternoon reading that code. Line by line, file by file, squinting at the migration that movedemail_signaturefrom one database table to another, Ctrl+F-ing for every instance of our feature flags.This time, I spent 15 minutes making decisions, and the code shipped without a single bug.Before AI, code review meant reading every line a teammate wrote. You checked for typos, logic errors, and style inconsistencies, the way an editor reviews a manuscript. Now my code reviews no longer involve reading code. And I’ve gotten better at catching problems because of it.This is code review done thecompound engineeringway: Agents review in parallel, findings become decisions, and every correction teaches the system what to catch next time. The signature fix that touched 27 files? Thirteen specialized AI reviewers examined it simultaneously while I made dinner.I’ll show you how I set it up, how it caught a critical bug I would have missed, and how you can start—even without custom tooling.The death of manual code reviewReading code, even briefly, gave me a sense of the shape of things. I could feel when the codebase was getting too complicated. By letting go of manual review, I worried that I’d lose that clarity, and the architecture would wander off without me.But I realized, too, that manual code reviews were no longer sustainable. When a developer writes 200 lines, their manager might spend 20 to 40 minutes reading it. The ratio of time spent writing code to reviewing it holds at 5:1 or 10:1—I can sit down with a cup of coffee, and the coffee will still be warm by the time I finish. AI has broken that ratio. The time it takes to generate code has collapsed, but the time it takes for a human to review code hasn’t. Something had to give...Become apaid subscriber to Everyto unlock this piece and learn about:Why Kieran Klaassen stopped reading his own code, and started catching more bugs because of itThe 13-agent review system that spotted a critical error hiding in line 31 of a 1,000-line changeThree questions that surface problems in two minutes that a 30-minute manual review would missSubscribeClick hereto read the full postWant the full text of all articles in RSS?Become a subscriber, orlearn more.Book information
Genre
Business and Economics
