The Science of Code Reviews
summary
A concrete claim: code reviews top testing for improving quality according to the SmartBear survey of ~600 professionals, and local survey results show 96% of reviewers learn and 87% enjoy the process. Practical tools mentioned include GitHub/Bitbucket/GitLab, PHPStorm, PHP CS Fixer, PHPMD, linters and the composer security checker. A small project called MeetSpire is built during a five day retreat where code reviews prove the most useful practice, surfacing bugs, architectural issues and shared decisions early.
AI-written summary · about
chapters (29)
- 0:00Intro
- 2:29WeCamp
- 5:54BitBuckets
- 9:31Pair Programming
- 11:55MA Programming
- 14:38Audience
- 16:34Egoless Programming
- 17:21Accept Mistakes
- 17:55Dont Rewrite
- 18:45Respect Different Patients
- 20:46Dont Take Pictures
- 21:12What to look for
- 24:37Code review etiquette
- 24:54Code review examples
- 25:17Dont jump to conclusions
- 25:31Save some letters
- 25:48Im curious
- 26:11Example
- 26:32Use examples
- 26:48Thank you
- 27:03gifs
- 27:24up your dosage
- 27:34you own the code
- 28:14thoughts
- 28:39getting started
- 30:18how to improve code reviews
- 34:15architectural exploration
- 35:47survey
- 36:55tips
related talks
59mCode Reviews - Why, what and how
48mEffective Code Reviews
29mCode review, do you speak it?
01h 01mCode Reviews: building better code and stronger teams
38mCracking the Code Review: from Guesswork to Automated Guidance
38mImplementing a Strong Code-Review Culture
43mCode Review, you said?
56mCode Review — The Art of Growing