Code Review: We Didn't Come Here to Suffer!
summary
A team describes turning code review into a practical process by introducing a concrete pull-request template with checkboxes (why, how, tests) and a short label set (praise, suggestion, nitpick, issue) so reviewers convey intent and blocking severity. They recommend tools and practices: linters and static analyzers (e.g. Sonar), formatters, GitHub saved replies, an automated check to catch var_dumps, plus training exercises and an ego-less programming mindset (inspired by Weinberg) to reduce friction and speed delivery.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:06What is code review?
- 6:21Why code review hurts
- 10:55Unclear or toxic comments
- 15:11Conventional Comments standard
- 20:25Automatable or useless comments
- 23:41Hard-to-use comments
- 25:03Egoless programming
- 31:27Code review as a skill
- 35:35Criticizing code today
- 38:26Team and review improvement
- 40:24Q&A
related talks
22mCode Review: We Didn’t Come Here to Suffer!
40mCode Review - How to Do It Better?
41mCracking the Code Review from Guesswork to Automated Guidance
29mCreating a Code Review Culture
49mBetter Code Reviews FTW!
29mCode review, do you speak it?
17mThe Perfect Code Review
11mTransforming Code Review into a Learning Tool for QA Teams