Better Code Reviews FTW!

on YouTube ↗01h 01m

" summary

Argues that code reviews are for sharing patterns, building shared ownership and faster solutions, not for scorekeeping; presents 10 concrete practices: ask for targeted reviewer input, write small readable PRs, run tests and CI pipelines, use linters/spellcheck and GitHub/Azure DevOps suggestions to automate the boring bits, prioritize quick turnaround and review immediately, favour grading up over blocking authors, and be open for feedback while framing comments as questions and pairing to resolve stalemates.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 3:54Why code reviews matter
3. 7:57Be open to feedback
4. 13:15Write reviewable PRs
5. 18:33Review PRs immediately
6. 21:49Avoid feedback overload
7. 25:01Accept code quality levels
8. 30:24Praise and examples
9. 33:37Frame feedback as questions
10. 39:02Resolve stalemates
11. 42:54Q&A

" related talks

• 49mBetter Code Reviews FTW!Tess Ferrandez-Norlander · NDC Copenhagen 2025
• 18mHow To Review Someone's Code While Not Being A Jerk!Maha Alsayasneh · DevFest Toulouse 2023
• 46mCode Review, you said?Venkat Subramaniam · Great International Developer Summit 2023
• 23mDrama-Free Code Review!Maha Alsayasneh · Voxxed Days Luxembourg 2022
• 17mThe Perfect Code ReviewVictor Rentea · Conf42 Enterprise Software 2021
• 38mImplementing a Strong Code-Review CultureDerek Prior · RailsConf 2015
• 40mCode Review - How to Do It Better?Sebastian Malaca · Confitura 2015
• 41mCracking the Code Review from Guesswork to Automated GuidancePaco van Beckhoven · Code Quality Conference 2024