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
-
I didn't mean to argue that doing the strict minimum to solve today's problem is always the best way to go, but that always making things as abstract as possible because it might be useful later isn't. It's possible I got lost on the way though.
Yeah, I didn't want to make a strawman out of that, because I saw your original point was about "maximally-polymorphic" code. But I wanted to take the opportunity to argue against "doing the minimum possible".
-
-
Yeah my tweets can clearly be understood to imply that. In a way, I do imply that, it's just that definition of "minimum" might not be the same as yours in this instance :)
-
I know that I prematurely generalize most of the time. I build things for reusability. One thing I think I've got better at with experience is knowing when to do it (and how), and when not to.
- 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.