Bullet-proof projects
summary
Gradual, low-effort measures that actually reduce breakage: run PHPStan at level 0 then raise levels to catch real type and API mismatches; run PHP CS Fixer automatically to stop style debates and auto-fix files; use a composer security checker (caught an outdated stream wrapper and blocked deployment) and composer-unused to remove dead deps (TYPO3 edge cases noted); harden tests with Infection (mutation testing) and Faker for randomized input; adopt blue‑green deployments and feature switches so releases can be rolled back or staged.
AI-written summary · about
chapters (11)
- 0:00Introduction to bulletproof projects
- 1:48Why projects need hardening
- 5:00Starting with small improvements
- 8:46Q&A on stack upgrades
- 11:59Code analysis tools overview
- 16:35PHPStan static analyzer
- 21:15PHP CS Fixer for code style
- 23:02Handling dependencies safely
- 30:59Improving test robustness
- 36:46Deployment strategies
- 39:15Summary and closing
