Goldilocks And The Three Code Reviews

on YouTube ↗34m

" summary

A practical postmortem: a big merged PR causes staging to crash because a duplicate controller slips through review, prompting a ~500 responses survey that finds reviews make devs better (avg 8.6/10, Ruby ~9.2), most reviews take about 5–20 minutes, and historical methods show inspections catch ~60% of defects while short reviews cut error rates from 55% to 2%. Recommendations are concrete: use linters and PR templates, include screenshots and repro steps, review everyone, be concise and kind, and iterate on the process.

AI-written summary · about

" chapters (8)

1. 0:00Start
2. 0:12Goldilocks and the Three Code Reviews
3. 12:21defect-detection
4. 14:54working meetings
5. 22:39big commits, large PR's, no context
6. 29:232. concise w/ context
7. 32:17start the conversation
8. 32:35bettercode.reviews

" related talks

• 47mGoldilocks and the Three Code ReviewsVaidehi Joshi · RedDotRubyConf 2017
• 42mGoldilocks And The Three Code ReviewsVaidehi Joshi · JSConf Budapest 2017
• 47mGoldilocks and the Three Code ReviewsVaidehi Joshi · Red Dot Ruby Conference 2017
• 45mCracking the Code ReviewPaco van Beckhoven · Voxxed Days Ticino 2025
• 32mLooks GREAT To Me: Getting Past Bare Minimum Code ReviewsAdrienne Braganza Tacke · Infobip Shift 2023
• 31mMay the Code Review Be with YouEgor Tolstoy · FrenchKit 2017
• 23mDrama-Free Code Review!Maha Alsayasneh · Voxxed Days Luxembourg 2022
• 32m👍 Looks GREAT To Me: Getting Past Bare Minimum Code ReviewsAdrienne Braganza Tacke · DevOpsDays London 2024