May the Code Review Be with You
summary
An explicit three‑step algorithm for code review: pick measurable goals with GQM metrics (examples: shared libraries, duplication, test counts), define who/when/how (limits on approvers, scheduled review windows to avoid breaking flow), adopt small PR rules and checklists, and automate checks with danger CI, up source, crucible, github and linters. Concrete outcomes include fewer open PRs, clearer ownership, caught defects earlier, and improved team empathy and review tone.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 1:26Three steps in organizing code review
- 3:27Shared code ownership
- 4:17Keep these goals prioritized
- 6:09Who when how
- 8:41Open community
- 9:11Flow state
- 10:13Best practices
- 10:50The paradox
- 11:37Dont submit too many changes
- 12:00Look through the code yourself
- 12:21Review Description
- 12:46Checklist
- 13:14Automation
- 13:34Danger CI
- 13:53Rules
- 14:27Rules Actions
- 15:35Tools
- 15:47Alternatives
- 16:09User experience
- 17:11AB Source
- 17:32Crucible
- 17:58GitHub
- 18:13Other alternatives
- 18:27Ethics
- 19:01Ask questions
- 19:40Thank others
- 19:59Special time
- 20:22Remember
- 20:36Consider
- 20:52Be Prepared
- 21:08Code Your Model
- 21:22Conclusion
- 21:54Pull Requests
- 22:10Engineering Practices
- 22:33Thank You
- 22:50Empathy
related talks
11mTransforming Code Review into a Learning Tool for QA Teams
41mCracking the Code Review from Guesswork to Automated Guidance
29mCreating a Code Review Culture
20mConducting Humane Code Reviews
39mEffective Code Review
17mThe Perfect Code Review
58mMay the Code Review be with you
22mContinuous Improvements of The Code Review Process