liveBook · Manning

Tech-debt ratio

As explained in Crack Any Codebase with AI

A tech-debt ratio is a measure of the share of engineering work devoted to addressing technical debt or maintenance rather than new features.

A tech-debt ratio measures whether engineering effort is shifting from new features toward fixes and maintenance. Classifying commit messages makes that shift visible across product eras. section 6.4

A rising maintenance signal

Ghost's fix-rate rose from 18% to 24% across era 2. The increase signals that maintenance was crowding out new work before examining a pull request. section 6.4

Figure 6.6 The four eras of a product's lifecycle as seen in its commit history: founder-led prototyping, maintaining a fading bet, a chaotic pivot, and mature, distributed development.

Use the lifecycle view to relate changing fix rates to broader shifts in product development and team structure. section 6.4

How Crack Any Codebase with AI covers it

How deep it goes
Defines an era-over-era fix-rate signal but does not specify a complete classification procedure.
Examples
Compares Ghost's fix-rate share, which rises from 18% to 24% across era 2.
What it assumes
Assumes access to commit history and the ability to distinguish fixes from features.
What you can do after
Evaluate maintenance pressure by classifying commit messages and comparing fix rates across eras.
How it connects
Connects tech-debt ratio to lead time, bus factor, commit history, maintenance, and feature development.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Crack Any Codebase with AI. The section links point to the parts of the book it draws on.