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
Combine friction per change with change frequency to estimate where improvement has the greatest impact. section 7.2.1
