News for hackers. Stuff that matters.
Re:Beginner's guide to OCaml beginner's guides by cgag on Thursday July 10, 2014 @04:01PM (#8016892)

    - Don't read the monad tutorials.
    - No really, don't read the monad tutorials.
    - Learn about Haskell types.
    - Learn what a typeclass is.
    - Read the Typeclassopedia.
    - Read the monad definitions.
    - Use monads in real code.
    - Don't write monad-analogy tutorials.
http://dev.stephendiehl.com/hask/#monads
Re:Beginner's guide to OCaml beginner's guides by mercurial on Thursday July 10, 2014 @04:23PM (#8017031)
On the other hand, the classic http://blog.sigfpe.com/2006/08/you-could-have-invented-monad... takes you (gently) through code, and you find out at the end that you have written a monad.
Re:Beginner's guide to OCaml beginner's guides by cageface on Friday July 11, 2014 @06:29AM (#8019506)
I think the best way to explain monads, at least to programmers with any real experience, is just to show a lot of examples of how they can be used to solve real problems. I went through dozens of explanations before the light finally went on and I saw what a simple concept a monad really is. All the crazy analogies and jargon-heavy discussions only serve to obscure what is really not a complicated idea at all.
Re:Beginner's guide to OCaml beginner's guides by GregBuchholz on Thursday July 10, 2014 @08:21PM (#8018198)
I think the best way to learn about monads is to write a monad tutorial. If nothing else it is a rite-of-passage.
Re:Beginner's guide to OCaml beginner's guides by rwosync on Thursday July 10, 2014 @09:43PM (#8018461)
Please don't do this. We have enough problems communicating this concept as it is.
Re:Beginner's guide to OCaml beginner's guides by e12e on Friday July 11, 2014 @03:18AM (#8019160)
Please do write one. Please don't publish one. Writing is a great way to think.

Without yet really understanding monads, I've come to realize that their only real problem is the name -- being named after some rather obscure (for most!) category theory concept -- that itself seems just about as simple and trivial as monads are. I find they are a little like the y-combinator in that regard.

I'm not sure if what we need is category theory in elementary school, or a different framework for discussing monads as it relates to programming -- but I'm almost convinced the confusion has to do with the language used to describe them.

Programming is a very practical art that sits on top of the much more abstract art of mathematics. It's useful to know orders of magnitude, graph theory, statistics, logic... but the art by which these concepts are animated and put to use is rather prosaic. And the discipline of computing has forged a set of concepts that are "appropriately abstract" (much, I think due to Knuth) -- but monads seem to lie just outside the grasp of many programmers. And I don't think it is because they are a particularly intrinsically hard concept.