Effective Code Review
summary
Code review cuts long‑term costs by catching mostly evolvability bugs (traditional bugs are only ~20% of defects) and by improving team knowledge; studies in the talk say new features take ~28% longer and bug fixes ~36% longer in low‑evolvability code. The stack used includes automated tests, static checks like PHP CS Fixer, CI (Travis/Jenkins/Circle) and repo rules in Github (protect master, require up‑to‑date branches). Keep reviews small (≤400 lines, ≤1 hour), link commits to tickets, and the Github workflow is set up under 5 mins.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 3:50We all make mistakes
- 5:05Agenda
- 7:00Why Code Review
- 9:45Evolvability
- 10:35Security
- 12:43Spreading knowledge
- 13:17Bus factor
- 14:35Mentoring
- 15:53Being watched
- 17:33Automation
- 19:20Tests
- 20:52Have they covered everything
- 22:24When I understand this code
- 26:29Project conventions
- 28:00Questions of uses
- 30:46Technical vetting
- 36:13What makes a good commit
- 36:49What I dont like
- 38:31Comments
- 39:38Code View Tips
- 42:21Summary
