Code Red: The Business Impact of Code Quality
summary
CodeScene-backed analysis shows organizations waste ~23–42% of developer time to poor code; red code modules are twice as slow to change, up to an order of magnitude more unpredictable, and contain ~15× more defects than green code. Combining code-health metrics with Git+Jira timing produces hotspot analysis and an x‑ray at function level (example: a 500‑line function, cyclomatic 112, 42 commits in a year) to prioritize refactors that cut time‑to‑market, reduce uncertainty and lower defect risk.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:28What is technical debt?
- 5:29Visualize technical debt & code complexity
- 14:39Quantify the business impact of code quality
- 18:20Does code quality matter?
- 27:01Prioritize remediation to large amounts of red code
- 37:29Resources
- 37:55Outro
related talks
36mCode Red: The Business Impact of Code Quality
45mCode Red: The Business Impact of Code Quality
46mCode 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
56mCode & Homicide: What Software Devs (..) from Offender Profiling
49mTreat Your Code as a Crime Scene
40mTreat Your Code as a Crime Scene