Elements of Clojure
therepl.net
Elements of Clojure
1–10 of 71 posts
Re: Elements of Clojure
#2Bought it, read it, liked it. Most of it is applicable to any programming language. I remember there being very little code examples in the book.
Re: Elements of Clojure
#3Bought it, read it, liked it. Most of it is applicable to any programming language. I remember there being very little code examples in the book.
Definitely! Chapter two deals directly with Clojure idioms, but other than that the content is quite general. Zach has said in multiple interviews that one of his future projects could be something like an "Elements of Software". Fingers crossed!
Re: Elements of Clojure
#4Don't let the title fool you - 90% of the advice given in this book isn't specific to Clojure, and boy is it good advice.
This book contains some of the deepest programming insights I've encountered, to be put on the same level as SICP or the Pragmatic Programmer.
The discussions on naming and abstraction are particularly illuminating, exposing some fundamental tradeoffs like synthetic vs natural names, or principled vs adaptable systems of abstractions. Were these notions more widespread, a lot of the pointless rants and debates we hear in programming circles would disappear.
I would not recommend this book to beginners - this book is most useful when you are experienced enough that your struggle is to make choices, not to get things to work.
Re: Elements of Clojure
#5Don't let the title fool you - 90% of the advice given in this book isn't specific to Clojure, and boy is it good advice. This book contains some of the deepest programming insights I've encountered, to be put on the same level as SICP or the Pragmatic Programmer. The discussions on naming and abstraction are particularly illuminating, exposing some fundamental tradeoffs like synthetic vs natural names, or principled…
Then why use 'Clojure' in the HN post except to advertise for that mostly dead programming language?
It's not 2014 anymore, the world moved on. I'm as upset about it as anyone.
Re: Elements of Clojure
#6Don't let the title fool you - 90% of the advice given in this book isn't specific to Clojure, and boy is it good advice. This book contains some of the deepest programming insights I've encountered, to be put on the same level as SICP or the Pragmatic Programmer. The discussions on naming and abstraction are particularly illuminating, exposing some fundamental tradeoffs like synthetic vs natural names, or principled…
the sample chapter on naming is a great example
Re: Elements of Clojure
#7This is great! I really enjoy the author’s use of philosophy as a guiding context/point of analogy—I feel like the majority of software engineers aren’t necessarily aware that nearly that many of the principles of software development date back to developments in logic and mathematics in the 19th century (we are doing little more than using formal langauges, after all) (actually the use of the term “indirection” is a great example of this—in the software industry, people have invented terms for things that have had long standing names and terminology around them already in logic and philosophy).
Hope this book also introduces some engineers to analytic philosophy too, a discipline that I feel is crucial for understanding any formal pursuits, and that is given far too little attention (thanks to the hyper-specialization of domains and knowledge).
Re: Elements of Clojure
#8I thought I wouldn't live to see the day for Clojure related link to be the top link on HN. I had to reload 5 times.
Clojure's cool, I am glad I got to work with it professionally. I did go back to Javascript, but it made me a better developer. It strikes a nice balance between being a pure functional language and being practical.
Re: Elements of Clojure
#9I thought I wouldn't live to see the day for Clojure related link to be the top link on HN. I had to reload 5 times. Clojure's cool, I am glad I got to work with it professionally. I did go back to Javascript, but it made me a better developer. It strikes a nice balance between being a pure functional language and being practical.
5-8 years ago, Clojure was constantly on HN! Then it fell out of HN attention.
Re: Elements of Clojure
#10I thought I wouldn't live to see the day for Clojure related link to be the top link on HN. I had to reload 5 times. Clojure's cool, I am glad I got to work with it professionally. I did go back to Javascript, but it made me a better developer. It strikes a nice balance between being a pure functional language and being practical.
Was going back to JavaScript your choice or an external factor such as job-related reasons?
As someone starting out with Clojure and ClojureScript I'd be interested to hear about your experience.