David Craelius tells the story of Klarna building an online payment system in Erlang and their approach to solving the nightmare of technical debt accumulated during a period of fast expansion.
Mike Long describes techniques for managing large legacy restoration projects, using a roadmap, prioritizing technical debt remediation tasks and motivating devs and stakeholders during the process.
Michael Feathers advices on creating an organizational process and culture that can enhance software development in a way that reduces technical debt.
Christof Ebert discusses technical debt including a Netscape vs. IE case study and provides a framework with practices for managing technical debt.
Felipe Rubim discusses several forms of technical debt, emphasizing that every member of the team should consider it, and suggesting taking concrete steps in measuring and reducing it.