liveBook · Manning

Bus factor

As explained in Crack Any Codebase with AI

Bus factor is the number of contributors whose loss would make a system or area of work unmaintainable.

Bus factor measures how many contributors would have to leave before a system or area of work became unmaintainable. It exposes knowledge and maintenance risk that an org chart can hide. section 6.4

A revenue feature with a bus factor of one

For a period, one engineer was the only person committing to Ghost’s members feature. That concentration made the feature a single point of failure, even though organizational documents might not reveal it. section 6.4

Use the commit history to investigate contributor concentration:

  • Identify systems or features with only one active contributor. section 6.4
  • Treat concentrated ownership as a maintainability risk requiring closer attention. section 6.4

How Crack Any Codebase with AI covers it

How deep it goes
Defines the metric and contrasts commit-log evidence with organizational charts, but does not provide a calculation procedure.
Examples
Uses Ghost’s members feature, where one engineer alone committed for a period, as a bus-factor-one example.
What you can do after
Diagnose single points of failure by inspecting contributor patterns in the commit log.
How it connects
Connects contributor concentration with commit history, lead time, and technical-debt ratio.

Also explained in

Compare how 3 books explain bus factor →

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.