2 ms·
Go ahead. Take 15 pages. It's why I - and I presume many others - clicked the article. As a bit of a motivator, I've now upvoted your blog post here. You ca
by logicallee 12y ago
Go ahead. Take 15 pages. It's why I - and I presume many others - clicked the article. As a bit of a motivator, I've now upvoted your blog post here. You can post the rest over the course of five or six articles. Add Part 1 to the title of this one. It's a good appetizer! :)
So as an intro it's a fine outline. Now get cracking on writing those 15 pages. :) Break it down into 5 parts. I'll upvote every one.
Make it suitable for someone coming from a language that doesn't have Monads. After all, it's a feature. If it can be learned - as you imply a way to do - then you can show and teach it, just as you've outlined.
(By the way, the difference between what you've just written of 'walking up to a musician' is that a student didn't ask you - you took it upon yourself to show a superior alternative to other people's blog posts on the subject. :))
So get cracking :)
Note: originally rather than post a critical comment here, I tried to email you, but didn't find an email address on your site, not even under "about" where you introduce yourself in two paragraphs - including your first name and city. Maybe add an email address there :)
- kybernetikos 12y ago> Make it suitable for someone coming from a language that doesn't have Monads. Most languages either have or support particular examples of Monads, but what is missing from many is the ability to write code that works on all Monads. Writing a Monad tutorial is pretty cliche now, because basically everyone who finally gets what the fuss was all about then blogs their own way of explaining it (guilty of this myself), so I'm not at all surprised that the author of this post didn't want to add yet another to pile.