Goldilocks and the Three Code Reviews

on YouTube ↗47m

" summary

Code reviews catch bugs earlier: formal inspections historically catch ~60% of defects and reduce defects 20–30% per 1,000 LOC, while short reviews drop error rates from ~55% to ~2% (or lift correctness from 86% to 99.6%). A 1–2 reviewer workflow often spends 5–20 minutes per PR; problems come from huge PRs, no context, and nitpicky comments. Practical fixes: commit hooks, GitHub PR templates, linters/formatters, small focused PRs, assigned reviewers, pairing, and iterating on the review checklist.

AI-written summary · about

" chapters (11)

1. 0:00Start
2. 8:34catching problems at the "lowest-value" stage
3. 9:28collective ownership in construction
4. 11:22inspections
5. 13:49short reviews
6. 14:50walk throughs
7. 22:06Energy
8. 24:33Substance
9. 28:59SKYLIGHT
10. 30:301. commit hooks
11. 35:25I love code reviews in theory.

" related talks

• 47mGoldilocks and the Three Code ReviewsVaidehi Joshi · RedDotRubyConf 2017
• 42mGoldilocks And The Three Code ReviewsVaidehi Joshi · JSConf Budapest 2017
• 34mGoldilocks And The Three Code ReviewsVaidehi Joshi · RailsConf 2017
• 44mEffective Code ReviewDave Liddament · phpDay 2018
• 22mThe truth about code reviewsSebastian Greulach · Voxxed Days Zurich 2017
• 45mCracking the Code ReviewPaco van Beckhoven · Voxxed Days Ticino 2025
• 01h 02mEffective Code ReviewDave Liddament · PHP UK Conference 2023
• 01h 05mGetting Good (or Better) at Code ReviewsRhia Dixon · NDC Melbourne 2025