3 ms·
> Refactoring has a fixed cost, not refactoring has an ever increasing cost. That means that refactoring has an increasing cost as well (with increased frequen
by sokoloff 3y ago
> Refactoring has a fixed cost, not refactoring has an ever increasing cost.
That means that refactoring has an increasing cost as well (with increased frequency, the total money spent on refactoring increases).
- jacquesm 3y agoNo it doesn't because you only write so much code.
- sokoloff 3y agoI think you’re then arguing that refactoring doesn’t have a fixed cost per occurrence, but rather that the more code you write between refactorings, the cost of the refactoring increases (which I agree with).
- seadan83 3y agoIf time is cost, then yes, everything has an increasing total cost. The question is more about complexity and interactions. Does a specific subsystem interact with N modules, or with 1. If N+1 module interacts with N, then the cost of maintaining that system will explode very quickly. OTOH, if the system is revisited after that test goes green to increase modularity, reduce dependencies, then complexity is now potentially growing sub-linearly to the number of modules rather than O(n!)