Getting Good (or Better) at Code Reviews
summary
If you write code you should also review code, period — regular PR reviews cut regressions, speed up delivery and shorten onboarding that otherwise takes about six to eight months. Keep PRs small (expect ~11–17 files for a component, not 72), use a pre-check PR template and leave contextual comments like [QUESTION] or blocker/suggestion/nit, build branches locally and use Netlify previews. Automate with SonarQube, pre-commit hooks, ESLint and configurable agents such as Kodo Merge AI, and require two approvers plus code owner to avoid single-person bottlenecks.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 5:04What code review is
- 15:19Code review as DevOps
- 20:35Collaborative learning
- 27:59Empowering juniors
- 32:15Quality with checklists
- 41:03Overcoming excuses
- 44:34Getting better at reviews
- 53:24Team norms and automation
- 1:00:53Recap and closing
