liveBook · Manning

Friction per change

As explained in Build High Value Software Systems

The additional time or effort a code smell causes for each modification to the affected code.

Friction per change is the extra time or effort a code smell adds to each modification. It helps prioritize cleanup by how much the smell slows work, not by how untidy the code looks. section 7.2.1

Estimate the added effort by:

  • Asking developers how much time code-quality issues consume. section 7.2.1
  • Comparing cycle times for similar changes in different modules. section 7.2.1
  • Observing time spent understanding code, testing manually, or tracing duplicated logic. section 7.2.1

Compare similar changes

A feature takes two hours in a well-structured module and eight hours in a legacy module. The six-hour difference estimates friction per change. section 7.2.1

Priority = Change Frequency × Friction Per Change

Combine friction per change with change frequency to estimate where improvement has the greatest impact. section 7.2.1

How Build High Value Software Systems covers it

How deep it goes
Defines added effort and offers survey, cycle-time, and observation methods, without prescribing a single measurement.
Examples
Compares a feature taking two hours in a well-structured module with eight hours in a legacy module.
What you can do after
Evaluate remediation priorities by estimating added effort through surveys, cycle-time comparisons, or direct observation.
How it connects
Connects code smells with change frequency, value streams, and prioritization.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.