Better Code Reviews FTW!
summary
Gives ten concrete tactics that change code reviews from painful to useful: make PRs small and include a short context and test logs, automate boring bits with Prettier, editorconfig and pre-commit hooks so humans focus on design, use LMs/copilots for first-draft cleanup, prioritize reviewing over starting new work, approve trivial remaining nitpicks, prefer pragmatic progress over perfection, use examples like switching to Python f-strings, frame feedback as questions, and award ties to reviewer unless the team agrees otherwise.
AI-written summary · about
chapters (16)
- 0:00Introduction to code reviews
- 3:39Code reviews beyond bug hunting
- 6:30Feedback in code reviews
- 8:00Being open to feedback
- 11:15Write PRs you'd review
- 15:13Settle style arguments
- 17:02Automate boring bits
- 18:51Review PRs immediately
- 20:59Don't overwhelm the author
- 23:32Perfection isn't required
- 26:53Approve trivial fixes
- 27:56Give positive feedback
- 29:45Frame feedback as questions
- 31:53Don't take it personally
- 33:40Resolve stalemates proactively
- 37:29Summary and Q&A
related talks
01h 01mBetter Code Reviews FTW!
32m👍 Looks GREAT To Me: Getting Past Bare Minimum Code Reviews
18mHow To Review Someone's Code While Not Being A Jerk!
17mThe Perfect Code Review
23mDrama-Free Code Review!
32mLooks GREAT To Me: Getting Past Bare Minimum Code Reviews
41mCracking the Code Review from Guesswork to Automated Guidance
40mCode Review - How to Do It Better?