Managing Technical Debt

Explore the concept of technical debt in software development through this insightful EuroPython 2016 conference talk. Delve into the pervasive nature of technical debt across service and product-oriented businesses, examining its inevitability and potential prevention strategies. Understand the distinction between technical debt and its associated interest, analyzing their qualifications and management approaches. Investigate the various levels at which debt and interest manifest in projects, and consider whether technical debt is truly unavoidable. Learn about clean code principles, Martin Fowler's perspectives, and strategies for identifying and addressing technical debt. Discover methods for measuring technical debt, implementing the Boy Scout rule, and approaching legacy applications. Gain insights into effective code reviews, team communication, and techniques for avoiding technical debt accumulation. Cover topics such as code coverage, architecture, and their roles in managing technical debt throughout the software development lifecycle.

Introduction
Agenda
Clean code
Martin Fowler
Why the quadrant
Status quo
Do you have technical debt
Application level
Whos responsible
What to do
I dont care
Measuring technical debt
The Boy Scout rule
Pick it up
Approaching legacy applications
Code reviews
Team communication
How to avoid technical depth
Coverage
Architecture