GlyphI've seen a lot of people talking about the practice of code review in a way that I consider unrealistic lately. So here are my thoughts on what code review is—and isn't—for: https://blog.glyph.im/2026/03/what-is-code-review-for.html
Sorry for the jump scare in the back half, but, this is my attempt to (A) write about The Problem without comprehensively making everything *about* The Problem all the time, and, (B) hack off a bit of useful philosophizing and writing from my Enormous Never-Going-To-Be-Finished Omnibus Post
Jeff Miller (orange hatband)@glyph I like point 2.
> Second — and this is actually its more important purpose — code review is a tool for acculturation.
And your points about automatic checks being the primary filters on code properties are well taken and worth repeating.
Bradalot “
”Code review is a social process, and you should treat it as such.
This is why we also like to include a "distant voice" in code review, someone within the big org who is less intimately familiar with the code/code base, just to notice things the local folk have perhaps become blind to, and to socialize more broadly coding practices and organizational affordances. (Also catches integration bugs and interface confusion early, which is a plus.)