Probabilistic-Programming-and-Bayesian-Methods-for-Hackers VS clojure-style-guide

Also this is quite nice practical introduction which might help with finding answers to your questions: https://github.com/CamDavidsonPilon/Probabilistic-Programming-and-Bayesian-Methods-for-Hackers

This is a good intro to probabilistic programming.

Probabilistic programming is a nice technique to have up your sleeve.

+1 for Statistical Rethinking. I’m also partial to Bayesian Methods for Hackers.

🔗 https://camdavidsonpilon.github.io/Probabilistic-Programming-and-Bayesian-Methods-for-Hackers/

You’re welcome! I would recommend Bayesian Methods for Hackers

All content is open-source: everyone is free to read, but also to contribute to the book using github. I know of one other book that followed this open-source 'publishing' model and became quite successful eventually through community efforts. I contemplated for a bit to create a book DAO but I think it's going to be overkill :).

Jake Vanderplas's Statistics for Hackers presentation is a perfect place to start. Bayesian Methods for Hackers is also very good.

Clojure developers also often make use of single-letter variable names, following conventions in `clojure.core`: https://guide.clojure.style/#idiomatic-names

My rule of thumb is to only use short names in the local scope of a function and have them follow conventions within the language community. Constrained like this, I see no harm in using them, since their meaning is clear within the context of their usage and there is usually no need to search for them. Of course, if the variable has a more specific meaning, I choose a more specific name.

Fixed link to that style guide entry: https://guide.clojure.style/#opt-commas-in-map-literals

Per that style guide, the above map would be formatted like this (on HN, just indent by two spaces):

  {:a 1

As for the broader question of Clojure style, there are style guides like https://github.com/bbatsov/clojure-style-guide and tools like clj-kondo to help learn and reinforce important practices.

Basically, you learn the expected places to put whitespace, make sure to edit your code accordingly and all of the parens will be automatically closed and adjusted. Using parinfer—which you can also combine with the more traditional paredit—makes writing Clojure code a lot like writing Python.

Also, there are guidelines, the styleguide, clj-kondo, kibit etc. And if you don't review your interns/juniors code to teach them good practices - you're doing it wrong (well, this one is true for any practical PL out there).

Another good resource is https://guide.clojure.style/ -- the (unofficial) community style guide for Clojure.

It's not an answer to your question but i can refer you to https://github.com/bbatsov/clojure-style-guide

The same could be said about the "Clojure Style Guide" from the Cider guy. As a matter of fact, there was an issue about it that was quickly declined https://github.com/bbatsov/clojure-style-guide/issues/232

Formatting is not that great, see https://github.com/bbatsov/clojure-style-guide btw