The Science of Code Reviews
summary
A practical playbook: builds an open‑source Meetup clone to test review habits, shows pair programming and mob programming as tight feedback loops and recommends pull requests with small diffs, linting and CI. Reports a Twitter survey: 73% get peer reviews, 96% say they learn, 87% enjoy reviews. Use tools like PHPStorm diffs, composer security checker/security advisories, PHP CS Fixer, keep code coverage steady, require two code reviews plus one functional test and a third reviewer to break ties.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:40RICK KUIPERS
- 11:23NAVIGATOR
- 13:54DO YOU HAVE COLLEAGUES REVIEW YOUR CODE?
- 14:38DO YOU FEEL LIKE YOU LEARN A LOT FROM GIVING AND RECEIVING CODE REVIEWS
- 15:14DO YOU ENJOY GETTING YOUR CODE REVIEWED?
- 17:10THE TEN COMMANDMENTS OF EGOLESS PROGRAMMING
- 31:54GETTING STARTED
- 34:07IMPROVING CODE REVIEWS
- 38:59ARCHITECTURAL EXPLORATION
- 40:24WHY AREN'T CODE REVIEWS PART OF YOUR COMPANIES WORKFLOW?
- 41:27CONVINCING YOUR COMPANY








