The truth about code reviews

on YouTube ↗22m

" summary

Code reviews are not mainly a bug hunt but a feedback and maintainability practice: studies quoted show only 15% defects of review comments while about 50% maintainability comments aim at naming and structure. Use small, focused reviews (review only key lines), stop after 60 minutes, prefer synchronous screen sharing for fast back-and-forth, include motivation and design notes in the commit, reduce tone problems from written comments, and aim for two reviewers — a second adds ~50% of remaining findings, a third adds little.

AI-written summary · about

" chapters (8)

1. 0:00The case for code reviews
2. 1:43Debunking bug hunting
3. 3:28Core benefits and purpose
4. 6:18Types and tools
5. 9:01Effective feedback culture
6. 13:00Practical best practices
7. 15:29Cultivating review culture
8. 20:11Q&A and closing

" related talks

• 45mHow to Get More Out of Your Code Reviews.Joe Kilner · Develop:Brighton 2021
• 48mEffective Code ReviewsFrank Sons · International PHP Conference Spring 2018
• 40mCode Review - How to Do It Better?Sebastian Malaca · Confitura 2015
• 43mCode Review, you said?Venkat Subramaniam · Voxxed Days Ticino 2024
• 53mCode Review - how to do it better?Sebastian Malaca · Voxxed Days Ticino 2017
• 45mHow to get the most out of code reviewsMaria Khalusova · JavaDay Kyiv 2015
• 44mEffective Code ReviewDave Liddament · phpDay 2018
• 38mImplementing a Strong Code-Review CultureDerek Prior · RailsConf 2015