4 ms·
Not really a software anti-pattern, as it does not result in any particular software mechanism. If anything, this is a development-process anti-pattern (not ev
by TickleSteve 9y ago
Not really a software anti-pattern, as it does not result in any particular software mechanism.
If anything, this is a development-process anti-pattern (not even software specific).
Its also extremely obvious and non-specific so doubtful that its worth naming as an anti-pattern.
- hamandchris 9y agoThere is some benefit to naming common problems to help discuss them, but this name strikes me as too clever / not immediately clear enough. "Bit rot" is a somewhat similar phenomena with a much better name.
- squiggleblaz 9y agoIf it's so extremely obvious, why does it happen time and time again? I think I've spent all of my time arguing against this process. It's bad. It's better to improve on a bad design, than to make a bad design worse by adding another design to it. But it's hard to notice that.
- TickleSteve 9y agoBecause its extremely difficult to do something about it. Its normal for people to change what they're working on, this is inevitable.