Code Red: The Business Impact of Code Quality
summary
Claims that poor code causes measurable business harm with evidence: analysis across commercial repositories in 14 languages links a 25-factor code health metric to Jira-timed work and git hotspots, finding ~42% developer time wasted, feature work in green code is >2x faster, red modules show ~15x more defects and up to 10x longer worst-case fixes. Uses behavioral code analysis and hotspots to prioritize refactoring at scale and demonstrates CodeScene-style visualizations on multi-repo systems (examples: 8M LOC runtime, 14k-line C++ file).
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:12What is technical debt?
- 8:00Visualize technical debt & code complexity
- 17:27Quantify the business impact of code quality
- 21:51Does code quality matter?
- 33:05Prioritize remediation to large amounts of red code
- 43:33Resources
- 44:44Outro
related talks
51mCode Red: The Business Impact of Code Quality
36mCode Red: The Business Impact of Code Quality
46mCode Red: The Business Impact of Code Quality
38mCode Red: The Business Impact of Code Quality
35mThe Code Quality Advantage How Empirical Data Shatters the Speed vs Quality Myth
36mThe Code Quality Advantage: How Empirical Data Shatters the Speed vs Quality Myth
49mTreat Your Code as a Crime Scene
33mCode Quality Metrics to Measure and Quantify Quality of Code