I’ve been working with Clojure for a couple of years already. I’ve done Clojure work as a contractor, and Parts, the project I spend most of my free time on, is written in it. I learned Clojure the same way I learned most other programming-related things: by looking at examples and hacking stuff together, slowly building understanding along the way. However, last year, when I was trying to get my first Clojure job, I had a disastrous coding interview with BG (a kind of a legendary figure in the Clojure world), which made me realise that I didn’t actually really know the language: without access to examples, I was useless. In the debrief, BG shared some advice for actually getting good at Clojure: work through the problems on 4clojure using only the official documentation (not ClojureDocs, which include examples!) and the Clojure source code. 4Clojure is a collection of programming problems that teach you the standard library, each problem building on the one before it, kind of in the…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.