Well... unless it's something really new, not a small change.
Some changes are not amenable to small diffs.
In that case, you don't just "review the diff", diffs are VERY limited. Lots of context is lost (you still use it as a guide, but it's not enough).
So, what to do?
Do a code walkthrough, involve reviewers early, if you're on the reviewing end, check-out the thing and navigate the code with whatever tool will help you understand it best (IDEs, whatever).
Reviewing a large change should be closer to pair-programming than a classical code review.
1 comment
[ 4.9 ms ] story [ 15.5 ms ] threadIn that case, you don't just "review the diff", diffs are VERY limited. Lots of context is lost (you still use it as a guide, but it's not enough).
So, what to do?
Do a code walkthrough, involve reviewers early, if you're on the reviewing end, check-out the thing and navigate the code with whatever tool will help you understand it best (IDEs, whatever).
Reviewing a large change should be closer to pair-programming than a classical code review.