Effective Code Review

on YouTube ↗01h 02m

" summary

Code review reduces overall development cost by catching defects earlier; studies show roughly 20% of issues are bugs and most are evolvability problems that slow future work. Automated gates use tests, PHPStan and Psalm, CodeSniffer/PHP CS Fixer and CI (GitHub Actions) before humans review. Reviews go commit‑by‑commit, keep changes small (recommend 400 lines or fewer and <1 hour sessions), protect main with required status checks and protect main branch plus lightweight staging/Sentry checks.

AI-written summary · about

" chapters (10)

1. 0:00Start
2. 2:55Benefits
3. 5:31Benefits of Code Review
4. 11:33Feature-Based Development
5. 13:10Advanced Static Analysis Tools
6. 21:36Can We Remove Comments
7. 27:58Design Patterns
8. 31:40Everyone Should Do Code Review
9. 35:11Make Your Commits Tell a Story
10. 43:10Keeping on Top of Code Reviews

" related talks

• 44mEffective Code ReviewDave Liddament · phpDay 2018
• 45mCracking the Code ReviewPaco van Beckhoven · Voxxed Days Ticino 2025
• 45mCracking the Code ReviewPaco van Beckhoven · Voxxed Days CERN 2025
• 47mGoldilocks and the Three Code ReviewsVaidehi Joshi · Red Dot Ruby Conference 2017
• 29mCode review, do you speak it?Michał Ostruszka · AgileByExample 2013
• 48mEffective Code ReviewsFrank Sons · International PHP Conference Spring 2018
• 53mCode Review - how to do it better?Sebastian Malaca · Voxxed Days Ticino 2017
• 45mA Drupal Core Maintainer shares peer code review best practicesJess (xjm) · DrupalCamp NJ 2023