Why PHP?
summary
Shows how to improve reliability and lower onboarding/style conflicts in PHP projects by using php-cs-fixer with PSR-12 for consistent formatting, using PHPStan (levels 0→9) to catch bugs without running code, and making features testable with PHPUnit or Pest PHP. Recommends versioning configuration files, adding tools to composer scripts, and running them in CI pipelines (example: GitHub Actions); notes statistics that still place PHP as the leading web language.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:30Who I am (and why I’m here)
- 5:54The Code
- 7:45History
- 8:57Statistics
- 10:35No comparisons
- 14:32Tool selection
- 16:37The programmer’s oath
- 19:22Versioning configuration files
- 20:26Tools to approach reliability
- 25:14Execution orchestration
- 27:45Reliability pipeline
- 28:47Roberto’s contribution
- 29:38The structure of Why from the programmer
- 32:26Useful documentation tools
- 35:01Why I prefer PHP?
related talks
12mWhat are Coding Standards in PHP?
28mReformat, Refactor, Replace: A practical guide for dealing with legacy software
38mWhy you should be using PHPStan in all your projects
36mLiving peacefully with Laravel
51mModern PHP
01h 00mIn Defence of PHP
01h 11mPanel Discussion: PHP - The journey so far (and what's ahead)
48mPHPStan: How the Sausage Is Made
