Getting More Out of Code Reviews

A review goes better when the author explains what to look at. A short note about the behaviour and any uncertain decisions gives me a starting point.

As a reviewer, I try to distinguish a bug from a preference. If something must change, explain the consequence. If it's optional, say so. And if the diff is too large to understand properly, ask for a walkthrough rather than leaving a few cosmetic comments and approving it anyway.