2 ms·
> BusinessAbstractFactoryIBuilder While I understand and agree with this meme[1], I think that's the other extreme, where everything is a Factory Builder thing
by delta_p_delta_x 4y ago
> BusinessAbstractFactoryIBuilder
While I understand and agree with this meme[1], I think that's the other extreme, where everything is a Factory Builder thing.
Even so, I would rather too much information than too little, which is what FP programs tend to do. Over-abstraction is also a problem, in my view. Even in a LINQ lambda, for instance, I might write
someEnumerable.Select(what_is_actually_inside => doSomething(what_is_actually_inside))
rather than
someEnumerable.Select(x => doSomething(x))
[1]: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
- toastal 4y agoFunny example since currying requires no intermediate variable to speak of someEnumerable |> select doSomething
- somebody1234 4y agoeven funnier when you realize that doesn't even need to be curried so it also works in c#: someEnumerable.Select(doSomething) to be fair, i guess doSomething was supposed to be an actual function body instead of a helper function from somewhere else