How do we code review at Slack
summary
Slack enforces crisp, small pull requests with a PR template with revertability flag that includes JIRA links, before/after UI, monitoring and test checklist. Automated tooling runs a PR length and description checkers, test detector and a code health score before merge. Domain experts hold office hours for heavy reviews, reviewers budget ~20% time, CI deploys main branch multiple times a day behind feature toggles and dogfooding, and team retrospectives plus agreements drive gradual improvement.
AI-written summary · about
chapters (8)
- 0:00Introduction and Acknowledgements
- 3:25Understanding Code Reviews
- 4:25The PR
- 7:00The Reviewer
- 9:38The Reviewee
- 14:47The Role of AI in Code Reviews
- 16:54Code Reviews and Team Culture
- 19:58Q&A Session
related talks
01h 05mGetting Good (or Better) at Code Reviews
28mPull Requests: Merging good practices into your project
21mContinuous Improvements of The Code Review Process
43mCode Review Tools
29mCreating a Code Review Culture
22mContinuous Improvements of The Code Review Process
17mThe Perfect Code Review
19mBetter, Faster Code Reviews in an Agile World