Code Review Tools
summary
Shows concrete tools and workflows: Review Board + GitHub webhook integration creates reviews from pull requests, a Juju bot enforces merges only after signoff, and Gerrit and internal systems get compared. Describes human processes that make reviews work: on‑call reviewer rota for timely feedback, mentored reviewer graduation, forced-submit with flagged post‑review and rollback strategies for emergencies. Compares pair programming with code review and recommends design docs and CRC cards to catch architecture earlier.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 11:20Code Review vs Pair Programming
- 15:30Importance of Code Review
- 20:05How long does it take
- 22:45Language
- 25:35Emergency
- 28:35Review
- 35:35Gamification
- 40:40Design reviews
related talks
29mCode review, do you speak it?
38mCode Review vs Pul Requests
33mCode review for Open Source
19mBetter, Faster Code Reviews in an Agile World
33mCode Review for Test Automation
41mCracking the Code Review from Guesswork to Automated Guidance
31mMay the Code Review Be with You
28mCode Review as a Collaborative Journey
