Living the best life on a legacy project
summary
Argues legacy often means “working existing code” not junk and recommends concrete practices: use Xdebug to step through surprising flows, add static analysis baseline with PHPStan/Psalm and shrink it gradually, run PHP CS Fixer/PHPCS in CI, and containerize tests with Docker + GitHub/GitLab Actions. Start tests with a single happy-path test (or characterization tests) for core business flows, add a test whenever a bug is fixed, and prefer small incremental refactors only where business value and reduced developer pain justify the risk.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:36Legacy code stigma
- 7:55Stakeholder communication
- 13:17Remote team tips
- 16:06Documentation strategies
- 20:00Reading existing code
- 23:51Aligning code with goals
- 26:20Strategic refactoring
- 29:32Automated checks
- 33:24Testing culture
- 36:14Code review policies
- 41:30Minimal viable tests
- 44:18Sustainable legacy code
related talks
41mLegacy, for lack of a better word, is good
41mTesting Legacy Code & Safe Refactoring
48mLegacy, for lack of a better word, is good
50mWe ♥️ legacy
54mThe Future of the Past – Legacy Will Stay With Us
01h 31mClean(er) Code for Large Scale Legacy Applications
43mHow to Innovate in a Legacy
52mOMG, What a Beautiful Legacy