Complexity hotspots
Where should the refactoring budget go? The map ranks the most tangled points of the system with numbers, and shows how far a change reaches.
Transcript
There is always less money for refactoring than needed, and the question is where to spend it. This video shows how the map ranks the most tangled points of the system, with numbers. The map tells you which object is the most expensive to touch.
This loader procedure tops the list, with 946 connections. Below it you see what it reads and writes: it reads from 314 objects and writes 157. And the answer to the question: 263 objects depend on it, across three levels.
This ranking is the basis for the refactoring decision: not a hunch, but a measured degree of dependency. And if this procedure must be touched, we know in advance how far the change reaches.
