A Crystal Ball to Prioritize Technical Debt

This session introduces techniques for analyzing code evolution and team activity to prioritize technical debt and detect organizational issues. It illustrates the approach with case studies from real-world codebases, including the .NET Core runtime.

Syllabus

Intro
Questioning Technical Debt
Collective Intelligence Uncover Evolutionary Patterns In A System
Case Study: The .NET Core Runtime
Normalization of Deviance
Supervise your complexity Trends
Code is Auto-Destructive Art
Temporal Coupling
The Microservices Shotgun Surgery Pattern
Process Loss
Measure Team Coordination The Diffusion of Responsibility
Measuring Conway's Law
The Perils of Feature Teams