Had to work with some code I wrote a few years ago where I went maximally polymorphic for the hell of it - it was just as painful as when working with badly documented and poorly tested dynamically checked code.
Show this thread
-
It really has to be a balancing act: how reusable can you make the first implementation? How likely is it that you'll need it? How difficult is it? How opaque will the implementation be?
I think writing highly generic code is challenging, fun and motivated mostly by personal enjoyment. The reaction to that is to outlaw it. But I think it's the reason why there's so much code in existence, which creates a huge space for bugs to hide.
-
-
I absolutely agree with your first sentence but don't understand why it leads to the second one. Knowing you, there *must* be a logical reason I'm not seeing. Would you mind filling in the bits?
-
Yes, sorry. I think that "it was more fun" is (correctly) seen as a bad reason for spending more time writing more general code, so we (as an industry) are starting to see early generalization as bad, because we assume there are no benefits other than the developer's enjoyment.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.