Philippe Kruchten on Managing Technical Debt

Episode notes

In this episode, Sven Johann hosts Philippe Kruchten, the author of the Managing Technical Debt book. They talk about the research leading to the book and the practical implications the book and the research offer. They start the conversation with discussing terms: technical debt, interest, principal and then start with technical debt on the code level, e.g. code smells, tests and refactoring followed by static analysis and the prioritization of the findings. They then move to technical debt on the architectural level and go through the possibilities on estimating cost and value on those improvement and how to sell it to the business stakeholders. This is followed by explaining technical debt on the infrastructure level and how great code can become technical debt by time passing by (technological gap, software aging). After that the conversation moves towards solving the problem tactically and strategically.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

• Eat your security vegetablesAdventures in DevOps · on Technical debt88 / 100
• Episode 106: [Value Boost] When AI Isn't the AnswerValue Driven Data Science · on Technical debt85 / 100
• DOP 368: The AI Productivity ParadoxDevOps Paradox · on Technical debt82 / 100
• Chris Coyier: The Long Game of Maintaining CodePenMaintainable · on Technical debt75 / 100
• Make the move successful: Replatforming content opsContent Operations · on Technical debt75 / 100
• AA254 - QA Is Dead!?! Why a MASSIVE QA Boom Is ComingArguing Agile · on Technical debt68 / 100

• Technology Governance with Sarah Wells64 / 100
• Agent Harness, State of Play, Risk and AI Company Culture93 / 100
• Data Marketplace, Data Products and Data Contracts95 / 100
• Data Architecture with Christoph Windheuser83 / 100
• Mirko Novakovic on Waves of Innovation and Observability Product Management86 / 100