4 ms·
A lot of others have mentioned clear reasons that bloat happens in the normal trajectory of software lifetime: increase in requirements, bugfixes, etc. But som
by titzer 11y ago
A lot of others have mentioned clear reasons that bloat happens in the normal trajectory of software lifetime: increase in requirements, bugfixes, etc.
But sometimes constant employment on a project just creates bloat, too. Refactorings that are intended from the beginning to reduce complexity either don't end up delivering, or they are never completed, leaving systems in a half-migrated state. Most systems I am familiar with are in a perpetual state of transition between the old way and the new way. The more complex the system, the harder a migration is. The harder a migration is, the more likely it is not to be fully done. The more incomplete migrations, the more complexity. On and on.
It's why eventually we should keep trying to reboot software systems with from-scratch, feature-lean replacements.
- sievebrain 11y agoPeople are very bad at deciding they need to be made redundant. Hence the phenomenon that "software is never done". It actually can be done, but you won't get the developers to agree to that!