[johnny_utah]

Before getting into web dev with Clojure, I recommend reading and doing the exercises from Clojure for the Brave and True to learn the language itself. It is one of the most engaging technical books I have come across in some time. http://www.braveclojure.com/

After that, I would go to the clojure docs to get started with web dev in clojure: http://clojure-doc.org/articles/tutorials/basic_web_developm... The luminus framework has a good tutorial to get started as well: http://www.luminusweb.net/docs

Caveat: I do not code clojure as part of my day job.

[zura]

Looking at ToC, the odd thing about Clojure for the Brave and True is that the very last chapter is:

Chapter 13: Creating and Extending Abstractions with Multimethods, Protocols, and Records

... This chapter serves as an introduction to the world of creating and implementing your own abstractions.

Wouldn't it make more sense to introduce tools for creating your abstractions at least in the first part of the book?

[bgar]

No because the topics in that chapter are advanced.

[zura]

Multimethods - maybe, but I think Records should be introduced much earlier, and probably Protocols as well.

Creating abstractions shouldn't be the most advanced topic in the language.

[zura]

EDIT: One interesting observation (from the outsider's perspective) - As I see, Clojure encourages use of primitive/language-provided data structures such as maps, lists, etc.. instead of creating your own abstractions and "inventing languages" (this is mentioned in a negative context, in Clojure docs). This is radically different approach compared to e.g. SICP, where creating many mini languages is actually encouraged. I personally find Clojure approach messy and unstructured (Also browsing a code in the wild). Anyway, as I can tell, Clojure has enough support to create well structured abstractions.