I decided to buy a book on Clojure. I attempted to get a recommendation out of someone who had encouraged me to learn Clojure in the first place. He said he was working through Programming Clojure, but mostly wanted to re-recommend the language.
There still seems to be a lot to take in. There are a lot of basics. This is in no way helped by the fact that many of the fundaments can be written in two different ways. Why oh why did anyone think that this was a good idea? Perhaps later in my learning I will be glad of this, but for now it just makes learning twice as hard. (As a parallel aside, having two ideas in my head about where the keys should be on my keyboard also confuses things (and by things, I mean me!))
If I were to write a Clojure tutorial I would stick to one way until the reader had grasped the basics quite thoroughly. Until I do, I shall stick with the tutorial I have. And wait for my book to arrive. And charitably hope that what makes a tutorial a little overwhelming to begin with, makes it a better reference resource in the long run.
P.S. I am no longer referring to the Dvorak cheat sheet that I printed out to get going. And as I'm on a physical QWERTY keyboard, there's no temptation to look at what's printed on the keys. In fact I'd cite that as a major advantage. The downside is that it can take a while to hunt around for the more obscure keys. For example, it is quicker for me to type "Square Bracket" than "[".
No comments:
Post a Comment