Earlier quoted context omitted.
I found that the best coded reviews are always from small change sets. They tend to have more comments on what the code is doing rather than what the code looks like. Sometimes this can’t be done though. I’d also say that if your team is commenting only on style in code reviews then they don’t understand that part of the code base very well. It isn’t a bad thing but presents a signal that they could spend some of the…
With some reflection, I think you're correct on the understanding problem. The problem has always been inconsistent - some code reviews are worth thousands of times more than others - and a determining factor may be how invested the particular reviewer is in that piece of code, how well they understand the surrounding ecosystem and things of that nature. As a concrete example, it has always been rare that a backend A…
In your defence, it’s hard to find out a way to fix a bad code review process with a team. I’m unsure how to really tackle that.