An ensembling approach to making legacy code habitable
summary
Claims that ensemble (mob) programming plus trunkbased commits turns inherited PHP into habitable code: team builds shared maps, portable make targets like make check and make dev, and uses an outside‑in torch light feature to exercise integrations. Tools include PHPUnit, local make targets, replicated production subsets on Apple silicon. Cycles run in 10–15 minutes, legacy backlog had ~40 stale PRs, replaced by 20–30 small commits, and the approach ships value hour‑by‑hour while onboarding juniors successfully.
AI-written summary · about
chapters (13)
- 0:00Legacy code challenges
- 2:28Solo vs team work
- 4:11Ensemble programming solution
- 7:45Keep ensemble practices
- 9:53First steps in legacy codebase
- 10:57Trunk-based development
- 11:59Torch light feature pattern
- 13:28Frequent small changes philosophy
- 15:33Local dev workflows
- 17:41Commit transaction costs
- 19:08Portability and tooling
- 20:13Outcome of small commits
- 21:20Human impact of habitable code
related talks
01h 01mFixing the Ultimate Legacy System: You
37mLearn to appreciate legacy (Story about Zed)
57mLiving the Best Life on a Legacy Project
28mReformat, Refactor, Replace: A practical guide for dealing with legacy software
31mLearn to appreciate legacy
41mLiving the Best Life on a Legacy Project
42mMany Hands Make for Light Work: Empower Your Coworkers to Develop...
57mRefactoring a large legacy PHP Application: a case study