Everyone's a Critic - The Why And How of Code Review

Small is Beautiful

10 lines of code = 10 issues.
500 lines of code = "looks fine".
Code reviews.
— Michal Konturek (@MichalKonturek) June 22, 2015

Not so much about the review itself, but about the pull request.
In the same way that long functions are a code smell, so are big pull requests
Branching is easy with Git - if it's a big feature, create a feature branch, and review the code as it's being merged into that branch
If you wait until the feature is ready to merge into your main branch, reviewing it will be a nightmare
Watch out for attention fatigue - it's difficult to review large changes
If you give people too much information, they'll struggle.
Cognitive load of reviewing large change means reviewers are less likely to spot problems.
Code review requires concentration, and it's difficult to concentrate for a long time.
And that seems like an appropriate place to finish.

Thanks Alex

Small is Beautiful

Image credits