How To Review Someone's Code While Not Being A Jerk!
summary
Argues for a small checklist (unit tests, docs, style, short PRs) plus automation so reviewers skip nitpicks and focus on design; names tools like flake8 and black for formatting and Snyk/SonarQube for security/code-smell. Cites a Google 2018 study on modern code review and a Microsoft 2015 finding that negative comments are judged useful 57% vs neutral 80%. Shows concrete Python example: join fails on mixed-type list and needs mapping to str. Recommends precise, actionable comments, assume competence, and prefer “LGTM” when appropriate.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 5:00Why code reviews matter
- 7:07Three key review questions
- 9:18What to focus on
- 10:22Checklists and automation
- 12:08Respectful reviews
- 13:37Practical feedback tips
- 16:48Key takeaways
