PHP's Kitchen Nightmares
summary
Keeps focus on specifics: quantify technical debt, run composer update regularly and a security checker in CI, use Rector to automate upgrades, and apply the scout rule to leave code cleaner than found. Call out legal risk—James Robert Liang gets 14 months for emission fraud. Avoid one‑size‑fits‑all frameworks, prefer simple scripts over a full stack when appropriate, and note the concrete result from a case study where Sunday lunch takings have doubled and overall turnover is up by 30 percent.
AI-written summary · about
chapters (20)
- 0:00Welcome
- 2:04Speaker and context
- 3:09PHP’s Kitchen Nightmares
- 7:21Clean code and technical debt
- 11:36Daily habits for clean code
- 13:20Updating dependencies
- 14:47Supported PHP versions
- 16:33Right development tools
- 18:20Tools for each project
- 20:48Customer in development
- 22:56Developer communication
- 26:49Legal responsibilities
- 29:40Speaking up about wrongdoing
- 30:42Breaking rules and creativity
- 32:29Recipes versus innovation
- 34:55Avoiding complexity
- 36:39Start simple
- 39:29Keep skills updated
- 41:12Professional development
- 43:17Summary
related talks
01h 00mIn Defence of PHP
31mLearn to appreciate legacy
28mReformat, Refactor, Replace: A practical guide for dealing with legacy software
44mPHP reviews for busy people
36mLiving peacefully with Laravel
44mWhy PHP?
01h 01mSecurity: From basic principles to PHP specifics
35mPHP is evil (Defensive programming)