A Crystal Ball to Prioritize Technical Debt

This presentation explores how code history and collective intelligence can help teams identify and prioritize technical debt in large software systems. It uses the .NET Core Runtime as a case study and considers links between code structure, team coordination, and software architecture.

Syllabus

Intro
Questioning Technical Debt
Collective Intelligence Uncover Evolutionary Patterns In A System
Case Study: The .NET Core Runtime
Hotspots X-Ray
Normalization of Deviance
Hotspots Summary
Specify Your Logical Components
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