3 ms·
I'd restrict that further. "Use abstractions only when you can see a valid present use." I've also spent days and weeks thinking about how to architect a solu
by nostrademons 17y ago
I'd restrict that further. "Use abstractions only when you can see a valid present use."
I've also spent days and weeks thinking about how to architect a solution, and then been wonderfully gratified when I can add new functionality with just a couple lines. More often, however, I find that the new function ends up being something totally unexpected, which I would never have thought of at the time I was writing the code. And then I have to throw away all those carefully crafted abstractions, because they just get in the way and slow me down while the software changes in unexpected ways.
It's easy to remember the successes. But more often, initial overarchitecting just results in lost time and wasted effort. Worse, it can be actively counterproductive if you don't have the courage to throw away dead code that's no longer useful.
- tetha 17y agoIn fact, even at the danger of being annoying, I would rephrase that once again. "USE abstractions when you can see a valid present use". Not listening to your code asking for a common abstraction of several things which already exist just for the sake of not using an abstraction ("well, because!") will result in an even bigger mess than most abstractions cause.