Continuous Improvements of The Code Review Process
summary
Avoid giant changes like a 100-file PR and prefer small commits — she shows a real before/after where a 3-file PR cuts ping‑pong and merge conflicts. Add a pull-request template with ticket link, description, before/after screenshots and a “unit test added” checkbox; set rules (e.g. reviewers required, PR awaiting time 5 hours up to 1 day), use “ignore spaces” diffs or IDE compare, adopt a PR pool and async picking, leverage AI linters for initial feedback, and schedule reviews to avoid a 25-minute context switch.
AI-written summary · about
chapters (9)
- 0:00Introduction and icebreaker
- 4:22Breaking tasks into smaller PRs
- 7:13Providing PR context and templates
- 8:17Setting PR rules and expectations
- 10:30Assigning PRs and avoiding bystander effect
- 12:20Balancing code review workload
- 14:06Being kind in code reviews
- 16:35PRs as learning opportunities
- 17:39Q&A session
related talks
22mContinuous Improvements of The Code Review Process
39mEffective Code Review
29mThe Art of Humanizing Pull Requests (PR’s)
17mThe Perfect Code Review
30mEffective Pull Request Reviews
28mPull Requests: Merging good practices into your project
01h 05mGetting Good (or Better) at Code Reviews
26mThe Art of Humanizing Pull Requests