Search a title or topic

Over 20 million podcasts, powered by 

Player FM logo
Artwork

Content provided by Joel Clermont and Aaron Saray. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Joel Clermont and Aaron Saray or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Finding a code-review style that fits your brain

16:20
 
Share
 

Manage episode 495267585 series 2974897
Content provided by Joel Clermont and Aaron Saray. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Joel Clermont and Aaron Saray or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

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.

  • (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

Sign up for the newsletter
  continue reading

131 episodes

Artwork
iconShare
 
Manage episode 495267585 series 2974897
Content provided by Joel Clermont and Aaron Saray. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Joel Clermont and Aaron Saray or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

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.

  • (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

Sign up for the newsletter
  continue reading

131 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Copyright 2025 | Privacy Policy | Terms of Service | | Copyright
Listen to this show while you explore
Play