4 ms·
A big working ball of mud is still better than a big ball of gold, that doesn’t do what it is supposed to do. The thing you can do to prevent it: continuous re
by andix 4y ago
A big working ball of mud is still better than a big ball of gold, that doesn’t do what it is supposed to do.
The thing you can do to prevent it: continuous refactoring. It’s better to ship features on time and clean up afterwards, than cleaning up a lot before and never ship things.
- whstl 4y agoIf you start with a simple ball of mud, sure. But a rigid architecture that's also a ball of mud is harder to refactor, and things also don't get done. As I said, using escape routes for some time, for speed, is acceptable. The problem is making this into a rule. Refactoring a bad abstraction is easier than refactoring an abstraction that is messy and bad. So either refactor sooner (and create proper abstractions) or skip the “ball of gold” altogether (eg: use the original framework directly).