The Clojure Style Guide by Bozhidar Batsov.
From the webpage:
Role models are important.
— Officer Alex J. Murphy / RoboCopThis Clojure style guide recommends best practices so that real-world Clojure programmers can write code that can be maintained by other real-world Clojure programmers. A style guide that reflects real-world usage gets used, and a style guide that holds to an ideal that has been rejected by the people it is supposed to help risks not getting used at all — no matter how good it is.
The guide is separated into several sections of related rules. I’ve tried to add the rationale behind the rules (if it’s omitted, I’ve assumed that it’s pretty obvious).
I didn’t come up with all the rules out of nowhere; they are mostly based on my extensive career as a professional software engineer, feedback and suggestions from members of the Clojure community, and various highly regarded Clojure programming resources, such as “Clojure Programming” and “The Joy of Clojure“.
The guide is still a work in progress; some sections are missing, others are incomplete, some rules are lacking examples, some rules don’t have examples that illustrate them clearly enough. In due time these issues will be addressed — just keep them in mind for now.
Please note, that the Clojure developing community maintains a list of coding standards for libraries, too.
You can generate a PDF or an HTML copy of this guide using Transmuter.
Another example where Ungoogleable Symbols from Clojure may be of interest.
A good index to Clojure resources needs to overcome the limitations of Google‘s search engine as well as others.
I first saw this in a tweet by LE Minh Triet.