5 ms·
Do you know what I miss about these explanations? Technical people can't go straight to the point. They go around, around, around, going into corners, etc (no
by raverbashing 14y ago
Do you know what I miss about these explanations?
Technical people can't go straight to the point. They go around, around, around, going into corners, etc
(not only on explanations, mind you)
For example, math has some very high-level/generic explanations, and curiously, I find them more understandable.
So, I've given up on understanding Monads (or at least Haskell ones), I'll probably understand them when I come up with a similar problem and think about how to solve them.
- gngeal 14y ago"For example, math has some very high-level/generic explanations, and curiously, I find them more understandable." That's because math always "goes straight to the point". There's nothing but the raw substance in it.
- kryptiskt 14y agoWhen I read math, I really like some motivating examples before digging into the definitions and theorems. For me, concrete examples makes it way easier to grasp abstract concepts.
- raverbashing 14y agoOh, I agree, sometimes it's too generic =) Especially if you don't know the names used in the description. The problem is that I can't stand explanations that would go like this if it was explaining Math: "So, we have a natural number, that is 2, 7, or 34232345 and by the way they're all integer numbers as well, also they are rational numbers as well, oh and there's equation you can do with them, but ok, so you can sum those numbers, etc" I'd rather go with "This turns the natural numbers (N, +) into a commutative monoid with identity element 0,"
- unconed 14y agoI find the best analogy is with optimized code. It's not like you're deliberately obfuscating it, but still, in trying to write it as succinctly as possible, some of the information has gotten lost.
- marco-fiset 14y agoIn this case, going around and around really helped me grasp the concept. Every other monad tutorial out there always go straight to the point and that is what made it difficult for me to understand them. I really like this series so far and I think this is the perfect way to explain something that complex. "You need to know where you came from to understand where you're going".
- papsosouid 14y agoI agree, monad explanations that use analogies are bad. There is no need for analogy, it is a simple concept, and is easiest to learn from an explanation of the actual concept, not semi-accurate sometimesish analogies. I think this is the best monad introduction I've seen: http://blog.sigfpe.com/2006/08/you-could-have-invented-monads-and.html http://blog.sigfpe.com/2006/08/you-could-have-invented-monad... It shows you why monads are a thing, what kinds of problems they can be used to solve, and then you see the overall pattern of how those different problems share the same underlying pattern (they are monads).
- lucian1900 14y agoLearn You A Haskell describes it quite clearly and with minimal analogies. You could give it a try.
- stuffihavemade 14y agoWhat do each of these equal? 1) Just 1 >>= \_ -> Just 2 2) Just 1 >>= \_ -> Nothing 3) Just 1 >>= \_ -> Nothing >>= \_ -> Just 2 4) Just 1 >>= \x -> Just(x+1) 5) Nothing >>= \x -> Just(x+1) 6) Just 1 >>= \x -> Just(x+1) >>= \x -> Just(x+1) 7) Just 1 >>= \x -> Just(x+1) >>= \y -> Just(x) If you can answer all of those correctly, you should have a decent understanding of monads. answers: 1) Just 2 2) Nothing 3) Nothing 4) Just 2 5) Nothing 6) Just 3 7) Just 1