Code Hotspots, Culture Champions, and Why Static Analysis Falls Short

Code Quality Through the Lens of Version Control History

TLDR: Adam Tornhill, author of Your Code as a Crime Scene, argues that static analysis alone is fundamentally insufficient for understanding code quality. By analyzing version control history instead, teams discover that development work concentrates in just 2-3% of the total codebase, which means technical debt should be prioritized by activity, not complexity.

Sharing your culture, finding your allies, and reliable code quality

Finding Allies: The Real Mechanics of Engineering Culture Change

TLDR: Improving engineering culture or quality is a two-part problem: identifying what needs to change and actually making change happen. The second part requires finding champions who drive a progression from lone crusader to coach to system-wide adoption.

Sharing your culture, finding your allies, and reliable code quality