Reformat, Refactor, Replace: A practical guide for dealing with legacy software
summary
Practical playbook: enforce a style and CI rule that fails builds on PHP‑CS regression and marks files changed >20% for cleanup, run PHP‑CS‑Fixer then refactor into Composer/autoloaded namespaces, delete dead code, and split the monolith with a strangler‑fig approach starting with users. Concrete results: 1.5 million lines deleted in one commit, 9604 mysql_ references converted to PDO over six months*, tools used: PHP‑Stan, Psalm, Rector, PHPUnit; outcome is incremental safety and eventual replacement. Slides: https://laracon.com.au/slides/2019/samuel-levy.pdf
AI-written summary · about
chapters (6)
- 0:00Start
- 3:51Secure Buying
- 4:59Ways To Secure Buy-In
- 12:34Namespace and Group Classes
- 13:59Split Monoliths into Smaller Pieces
- 17:35Replacing Legacy Software
related talks
57mRefactoring a large legacy PHP Application: a case study
44mWhy PHP?
31mLearn to appreciate legacy
41mLiving the Best Life on a Legacy Project
57mLiving the Best Life on a Legacy Project
40mRefactoring Huge Legacy PHP Applications - From 100 hours to minutes
37mLearn to appreciate legacy (Story about Zed)
01h 00mIn Defence of PHP