Implementing a Strong Code-Review Culture
summary
Claims that code review’s primary value is knowledge transfer and team awareness rather than bug catching backed by a 2013 Microsoft and University of Lugano study. Concrete practices: authors give two paragraphs of context and keep changes small so reviews take ~10 minutes. Reviewers follow ask don't tell phrasing and favor questions over commands. Tooling recommendations include style linters and bots such as HoundCI (rubocop jshint sass lint) to automate style and reduce bike-shedding.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 0:28Show of Hands
- 1:08Catch Bugs
- 1:42The Problem with Code Reviews
- 2:41The Microsoft Study
- 4:06What is CodeReview
- 5:17What is a Strong CodeReview Culture
- 7:06Gary Vaynerchuk Quote
- 10:15Provide Context
- 11:32Ask Dont Tell
- 13:10Extract a Service
- 14:48Provide Feedback
- 16:02Ask Questions
- 16:18Why didnt you just
- 16:28Were just right
- 17:00Just as gone
- 17:32Be positive
- 17:51Socratic method
- 18:23We are in it
- 18:49Conflict is good
- 22:13What to review
- 22:58Single Responsibility Principle
- 25:49Style
- 26:55Style Guide
- 27:57Tools
- 28:17Strong CodeReview Culture
- 30:57Questions
