Code Review Beyond Code Style
summary
Argues that concrete rules and tooling — a company PHPCS ruleset with a trailing comma rule and disabled alignment — plus CI checks (Travis, Scrutinizer, linters) and disciplined PRs (clear changelog, links to issue, atomic commits) cut review noise, surface only functional diffs, and raise team knowledge. Reports spending 15 hours a week on reviews. Recommends specific checklist items (tests first, reviewers assigned, check migrations, pull locally) and suggests tone techniques like the sandwich to keep feedback constructive.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:14What Is Code Review
- 2:19Feedback Loop
- 8:35Making a Pull Request
- 16:52Braces
- 18:31What Should the Submitter Do What Should the Reviewer Do
- 29:50Lizard Brain
- 40:58The Feedback Loop
