I like this post. With my recent new job, I didn't realize how much of code review is social, about learning idioms and passing along advice. It can also help find where idioms need to be created, that is, repeated code that should be pulled into a common library instead of repeating it over again.
I have been on both sides of this recently.
And automating the hard parts needs to be done. This is running tests regularly, using static analysis, running code coverage and more. All of these should be in place before llm are used, that way they can take a lot of the load off human reviewers.
> https://mastodon.social/users/glyph/statuses/116169576453804352