I'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
What Is Code Review For?

Code review is not for catching bugs.

@glyph IMO, one of the best uses of a language model is to review your own writing or code, since it has a good idea of what the "norm" is, can keep its attention indefinitely, and can explain reasonably well what the norm is. It also fits well within the paradigm of "are you working for the machine, or is the machine working for you?”. But it also doesn't mean that people shouldn't be a part of the review, just that people should be doing the fun stuff, not the dry, hard to focus on stuff.
@glyph it's also much easier for a lot of us to take a critique from a machine than from a person!