Cracking the Code Review

on YouTube ↗44m

" summary

Argues that better PR hygiene plus automation cuts review friction, cites a $60B annual bug-fix cost (2013) as motivation, and shows concrete fixes: use PR templates and checklists, add screenshots and examples, review your own branch in an editor, and target reviewers with deadlines. Recommends specific tools and workflows that actually reduce noise—error-prone (with picnic rules) and OpenRewrite for automated fixes, Google Java Format + Spotless for enforced formatting, and ArchUnit for architecture rules—reporting that starting small (three repos) and tuning rules wins adoption.

AI-written summary · about

" chapters (6)

1. 0:00Introduction to code reviews
2. 3:00Pull request best practices
3. 3:54Creating and managing reviews
4. 16:34Being an effective reviewer
5. 28:20Automating quality with tools
6. 43:51Conclusion

" related talks

• 45mCracking the Code ReviewPaco van Beckhoven · Voxxed Days CERN 2025
• 41mCracking the Code Review from Guesswork to Automated GuidancePaco van Beckhoven · Code Quality Conference 2024
• 46mLooks GREAT To Me: Getting Past Bare Minimum Code ReviewsAdrienne Braganza Tacke · Voxxed Days Thessaloniki 2023
• 23mDrama-Free Code Review!Maha Alsayasneh · Voxxed Days Luxembourg 2022
• 01h 05mGetting Good (or Better) at Code ReviewsRhia Dixon · NDC Melbourne 2025
• 18mHow To Review Someone's Code While Not Being A Jerk!Maha Alsayasneh · DevFest Toulouse 2023
• 01h 01mBetter Code Reviews FTW!Tess Ferrandez-Norlander · NDC London 2024
• 32mLooks GREAT To Me: Getting Past Bare Minimum Code ReviewsAdrienne Braganza Tacke · Infobip Shift 2023