Post

Rachel's Ramblings: Maybe We Shouldn't Be Reviewing All This Code: Or, perhaps the problem isn't that AI has broken code review, maybe it’s that we've been using code review to solve the wrong problems martinfowler.com/rachels-ramb...

martinfowler.comMaybe We Shouldn't Be Reviewing All This CodeOr, perhaps the problem isn't that AI has broken code review, maybe it’s that we've been using code review to solve the wrong problems

2/9/26, 1:49 pm8 reposts23 likes

Copper Sun Brass Coders

@coppersun.dev

4 Sept

Splitting review into two layers helps: deterministic stuff like secrets, type mismatches, dead code, unsafe deps should get caught by tools before a human ever sees the diff. That frees reviewers to focus on intent and design, which is what they're actually good at judging.

Chraz

@edu.runlinea.com

2 Sept

Rachel's framing is sharp. Review got overloaded as the place we check correctness, teach juniors, and gate design. Agents just made the queue overflow so that overload finally showed.

maasha.bsky.social

@maasha.bsky.social

2 Sept

IMHO, Code review: retrospective invitation for people to sit together and go over the thought process to solve a problem. Not AI applicable.