At times, Aaron and I approach pull-requests in very different ways. I like reviewing them commit-by-commit in some cases, but Aaron prefers scanning the whole thing at once.
In the latest episode of the No Compromises podcast, we dig into when each approach shines, how “atomic” commits can help (or hurt) reviewers, and why understanding how your teammate’s brain works is a super-power.
Along the way we share practical tips for leaving yourself notes, spotting hidden changes, and keeping large refactors under control.
- 00:00 The “gift” of a pull request and the pain of huge PRs
- 02:30 Joel’s commit-by-commit strategy and where it helps
- 04:50 Aaron’s Tetris-style holistic review (and leaving self-notes)
- 07:45 When atomic commits backfire and trust becomes a factor
- 08:45 Silly bit
And after listening, don't forget to subscribe to the podcast, so you don't miss future episodes.
Here to help,
Joel
P.S. Want help getting started with a better code review process for your project?