3 ms·
This is true of any sufficiently general abstraction. Like a multi graphs and effects systems. In fact overly general abstractions are an anti pattern in pract
by duped 5y ago
This is true of any sufficiently general abstraction. Like a multi graphs and effects systems.
In fact overly general abstractions are an anti pattern in practical software development, at least in my opinion. Any problem can be successfully extrapolated to a more general case, that doesn't mean it's worth doing it.
- zaphar 5y agoThey do give you a template for approaching certain problems though. Even if your implementation of the template in your head is specific and therefore easier to follow in the implementation. It's useful to have an understanding of them for that reason.
- eternityforest 5y agoThe results of those templates seems to be a lot different from regular old boring industry standard reusable code, which has design patterns(Developed over the years for everyday practicality) as the templates instead of abstract logic(Seemingly chosen for beauty and ability to express original ideas). They say you can find monads everywhere, but doesn't that mean that by using monads as a starting point, you'll have more freedom and less structure and predictability than if you used a GoF pattern?