On the surface, the idea of code review is a no-brainer: why wouldn't we want a second set of eyes on our code, especially before deploying to production?
As we peel back the layers, however, we find that the topic of code review is much more nuanced. How detailed should the review be? Who is qualified to perform the review (hint: it's not just senior developers)? Can we afford to take another developer away from their project to review this one? What steps can we take to ensure reviews are constructive, rather than demoralizing?
Attendees will gain deeper insight into some of the arguments for and against systemic, peer code review, as well as pick up some useful tools to make code review a natural part of their teams' workflow.
✨ View slides ✨
- PHP Tek 2025 — May 22, 2025 (PDF, Joind.in)
- Cascadia PHP 2019 — September 20, 2019 (PDF, Joind.in)
- Beer City Code 2019 — June 1, 2019 (PDF)
- php[world] 2018 — November 14, 2018 (Joind.in, PDF)
- Cascadia PHP 2018 — September 15, 2018 (Joind.in, PDF)
- INN Labs Office Hours — May 25, 2018 (Video, PDF)
- WordCamp Dayton 2018 — May 19, 2018 (PDF)
Below are links to some of the tools referenced throughout the talk.
- PHP_CodeSniffer — Extremely popular linter (and fixer) for PHP
- PHP Coding Standards Fixer — Alternative to PHP_CodeSniffer from the Symfony ecosystem
- PHPStan - A very popular—and dare I say the best?—static code analysis tool for PHP
- Psalm - Another popular PHP static code analysis tool (from Vimeo)
- ESLint - Prominent linter for the JavaScript ecosystem
- Shellcheck - Shell script analysis tool
- RuboCop - Linter/formatter for Ruby
- PyLint - Linter for Python code