Code review beyond code style
summary
Argues that code review focused on concrete practices — Git-based PRs, atomic commits, test‑first workflow with PHPUnit, and CI checks via StyleCI/Travis — makes reviews faster, reduces style arguments and surface bugs before deploys. Recommends Git add -p, keepachangelog.com for PR descriptions, GitHub review flow, and a docs repo or GitBook for rules. Uses the sandwich and suggestive language techniques to avoid interpersonal blowups. Teams report higher maintainability, fewer style debates, but occasional micromanagement needs offline resolution.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:19Code Reviews beyond Code Style
- 10:06Atomic Commits
- 15:15Check Your Code Duplication
- 16:49Things That You Should Do as a Reviewer
- 17:45Design Patterns
- 27:19Reptile Brain
- 28:27Use Suggestive Language
- 33:36Who Should Click this Button
- 41:01Git Book
