3 ms·
That cruft is due to "requirements". It's easier to modify a system with less cruft, because modifying a system means adding, deleting or changing requirements.
by kazinator 8y ago
That cruft is due to "requirements". It's easier to modify a system with less cruft, because modifying a system means adding, deleting or changing requirements. This is easier to do when there are fewer of them.
If you think of a new requirement, it's easier to be sure that it doesn't conflict with six requirements than with sixty, or six hundred.
Additionally, requirements are hard to remove/change once their implementations are deployed and depended on.
Basically we are already saddled with debt at the requirement level, before we even consider the implementation quality.
Thus, the first tool in the fight against technical debt is to very carefully manage the acceptance of new requirements. If a requirement doesn't exist, then its code doesn't exist, and that's as clean and maintainable as code can possibly be.
Secondly, try to gather all of the requirements up-front before implementing anything, and then resist futher requirement creep. If most of the requirements in a system were gradually introduced after implementation began, that will tend to degrade the quality.