Code Review, you said?
summary
Argues code review is feedback-driven engineering and gives concrete rules: never review uncompiled code or code without passing automated tests, review the tests first, ask for reviews early and small so reviewers give useful design changes, rotate reviewers (junior and senior) to reduce the truck factor, and when finding a bug write a failing test for each bug so CI signals the author; warns against gating production on ritual reviews and urges review incrementally for faster, safer improvements.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:00The power of peer review
- 2:51Quality and development
- 3:26Redefining Agile
- 6:35Types of feedback
- 9:16The dread of reviews
- 11:37Empathy and humility
- 15:07Technical and social
- 17:24Benefits of reviews
- 22:25Collective ownership
- 26:16How to review code
- 28:10Effective review processes
- 30:45Early and frequent feedback
- 33:43Reviewing for quality
- 35:24Handling bugs in reviews
- 37:43Culture of safety
- 39:42Tactical code reviews
related talks
46mCode Review, you said?
40mCode Review - How to Do It Better?
45mHow to Get More Out of Your Code Reviews.
22mThe truth about code reviews
59mCode Reviews - Why, what and how
53mCode Review - how to do it better?
29mCode review, do you speak it?
41mCracking the Code Review from Guesswork to Automated Guidance