
Sign up to save your podcasts
Or


Joel and Aaron compare two very different ways to tackle pull-requests—reviewing them commit-by-commit or scanning the whole thing at once. They 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 they share practical tips for leaving yourself notes, spotting hidden changes, and keeping large refactors under control.
By Joel Clermont and Aaron Saray4.9
88 ratings
Joel and Aaron compare two very different ways to tackle pull-requests—reviewing them commit-by-commit or scanning the whole thing at once. They 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 they share practical tips for leaving yourself notes, spotting hidden changes, and keeping large refactors under control.

57 Listeners

697 Listeners

568 Listeners

56 Listeners

76 Listeners

24 Listeners

987 Listeners

50 Listeners

17 Listeners

14,371 Listeners

27 Listeners

2 Listeners

7 Listeners

0 Listeners

4 Listeners