7 articles tagged with "Technical-debt"
The strangler fig pattern explained: replace a legacy system incrementally with a routing facade, parallel runs, and a ratchet, no big-bang rewrite needed.
Jonny Rowse 8 min read What is legacy code? A clear definition for developers, why Michael Feathers defines it as code without tests, and how to tell debt from legacy.
Jonny Rowse 7 min read Refactoring legacy code safely: a practical playbook with characterisation tests, seams, strangler fig, and small changes that keep production up.
Gareth Clubb 11 min read A practical guide to legacy code analysis: how to audit an unfamiliar codebase, identify risks, map dependencies, and plan a safe path forward.
Zubair Hasan 12 min read A practical Q2 checklist for tackling technical debt. Audit dependencies, clean dead code, fix linter warnings, and prioritise what to refactor first.
Jonny Rowse 8 min read A practical checklist for spring cleaning your codebase, covering dead code removal, dependency updates, and technical debt reduction.
David White 6 min read Learn when to fix technical debt and when to leave it alone. A practical framework for making smart tradeoff decisions.
David White 9 min read