Technical debt: prevention and cure
Legacy, migration, refactoring, rationalisation, technical debt
Most people in software development in ‘real life’ organizations have felt themselves being seduced into applying a quick fix while – deep in their hearts – realizing that it is making the application less maintainable and therefore less valuable. This liability is called ‘technical debt’ and the talks in this track address how to prevent or limit it occurring, and how to repair any damage that has already been done. Various aspects will be covered: how to avoid making the wrong decision in the first place, techniques for application migration and other forms of application rationalization, organizational measures including culture, and business cases based on the economics of technical debt and the political reality of it being the next generation’s problem.
ASL BiSL Foundation