👍 Looks GREAT To Me: Getting Past Bare Minimum Code Reviews

on YouTube ↗32m

" summary

Explains concrete fixes: reviewers leave ego behind, focus on code, run 25–45 minute focus bursts and refuse giant PRs; write objective, pinpointed comments using labels like needs change / needs rework / nitpick and the Triple R: request, rationale, result format; authors self-review, run linters/formatters/static analysis and tests, and make PRs atomic so they’re reviewable in 10–20 minutes — studies show reviews under ~500 lines and <20 files get more useful feedback; use PR templates and CODEOWNERS to auto-assign.

AI-written summary · about

" chapters (7)

1. 0:00Introduction to LGTM problem
2. 1:07What’s wrong with code reviews
3. 7:10Fixing reviewer mistakes
4. 10:19Writing effective comments
5. 21:30Author’s common mistakes
6. 25:25How authors can improve
7. 29:37Going beyond bare minimum

" related talks

• 32mLooks GREAT To Me: Getting Past Bare Minimum Code ReviewsAdrienne Braganza Tacke · Infobip Shift 2023
• 49mBetter Code Reviews FTW!Tess Ferrandez-Norlander · NDC Copenhagen 2025
• 17mThe Perfect Code ReviewVictor Rentea · Conf42 Enterprise Software 2021
• 23mDrama-Free Code Review!Maha Alsayasneh · Voxxed Days Luxembourg 2022
• 39mEffective Code ReviewTahsin Dane · Android Summit 2019
• 01h 01mBetter Code Reviews FTW!Tess Ferrandez-Norlander · NDC London 2024
• 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