3 ms·
It's also possible that we try to hard to generalise things and for a handful of lines of code it's just as valid to provide different implementations for each
by weego 6y ago
It's also possible that we try to hard to generalise things and for a handful of lines of code it's just as valid to provide different implementations for each rather than spending time evaluating an abstraction that's as likely to only be identical in implementation due to incomplete use case or just the product of the sheer coincidences that appear in immature code.
- striking 6y agoI think it's worth noting that the examples in the article are the way they are for the sake of demonstration. In that context, I very much appreciated the explanations even as a fairly seasoned programmer; I knew more or less how to do these transformations, but not what they were called and how I might explain in words why I'm doing them.
- stopachka 6y agoAuthor here: Indeed, this could be an option right before "Configuration" on the spectrum I shared. For that specific example, I don't think it would make sense to do, but in many cases it can be valid. I hope the point of the essay came through, that there is an abstraction spectrum, and where certain ideas fall onto that spectrum. Thanks for reading!
- deleted 6y ago[deleted]