This is actually a rather good cheat-sheet. I'm usually a fan of using cheat sheets, lists of commands, etc. to pick up new languages, but I have my reservation

This is actually a rather good cheat-sheet. I'm usually a fan of using cheat sheets, lists of commands, etc. to pick up new languages, but I have my reservations specifically with regard to a cheat sheet for Haskell. The trouble with the cheat-sheet approach to Haskell stems from the fact that Haskell is quite unlike most other commonly used programming languages, i.e. substantially unlike the languages that someone reading the cheat sheet is likely to know. As a rather strictly FP language with a very strong type system, it is unlike the more mainstream languages on both a deep, technical level and on a superficial level (e.g. syntactically, the 'look' of the code, etc.). This means that you could use a cheat-sheet to write some trivial programs, but it would be hard to progress further, because you would, on a very fundamental level, not know what you are doing. The same goes for C. While a cheat-sheet can tell you all about the printf function, data structures, types, etc., it is unlikely that a cheat sheet will be sufficiently informative on memory management, using the heap and the stack, pointer arithmetic, etc. --- the really crucial things that one needs to know to write C effectively. While a Python programmer could use a cheat sheet or learnxinyminutes.com to pick up and write some basic programs in Ruby, it's hard to do the same for languages like Haskell or C, which really require understanding beyond what a 'cheat sheet' communicates.