Adam Tornhill: Prioritizing Technical Debt With Behavioral Code Analysis

EP-039 | January 20, 2020 | 42:39 | Last updated: March 27, 2024

Technical Debt Code Quality

Adam Tornhill

Founder & CEO, CodeScene

Creator of CodeScene and author of 'Your Code as a Crime Scene' and 'Software Design X-Rays'. Pioneered behavioral code analysis for managing technical debt.

Adam Tornhill: Prioritizing Technical Debt With Behavioral Code Analysis

Robby speaks with Adam Tornhill, founder of Empear and CodeScene. They discuss the benefits of having clear boundaries between teams, strategies for prioritizing where to start tackling technical debt, and how to improve the onboarding experience for developers new to a software codebase. Adam also shares a rare example of a successful rewrite project.

Subscribe to Maintainable on:

Or search "Maintainable" wherever you stream your podcasts.

Join the discussion in the Maintainable Discord Community

Frequently Asked Questions

What is behavioral code analysis?

Adam Tornhill's behavioral code analysis uses version control data to identify hotspots — files that change frequently and have high complexity. This data-driven approach helps teams prioritize which technical debt to address first.

How does Adam Tornhill recommend prioritizing technical debt?

Adam suggests using code change frequency combined with complexity metrics to find the highest-impact areas. Files that change often and are complex should be refactored first because they create the most friction.

What is CodeScene and how does it help with maintainability?

CodeScene is a tool created by Adam Tornhill that analyzes code repositories to identify technical debt hotspots, team coordination issues, and code health trends using behavioral data from version control history.