A History of Clojure [pdf]
Prior to Clojure I feel that I didn&#x27;t really know how to do things well.<p>In the context of the domain I have the most experience with, web applications, I&#x27;d summarize the bulk of programming as defining data, data transformations and shoving data through APIs. Once you get the hang of it, Clojure makes it trivial to transform datastructures from A to B. This has enormously expanded the kinds of problems I can solve.<p>When Rich says
&quot;It was impossible to
avoid the sinking feeling that I had been “doing it wrong” by using C++&#x2F;Java&#x2F;C# my whole career.&quot;<p>I feel somehow that this is the case for the majority of people but they don&#x27;t realize it yet because their experience is the most popular trendy language or framework. I&#x27;ve seen many examples of libraries in different languages having enormous amounts of commits and hundreds issues for problems that are trivial to solve in Clojure.<p>I was in the same boat, constantly grabbing for frameworks and if one wasn&#x27;t available that made my task simple, would struggle trying to bend the frameworks or language I was using to come up with a solution.<p>I&#x27;m not a language geek and I don&#x27;t write code outside my work for fun. I want to spend the least amount of time possible in front of the computer and sleep knowing my web applications won&#x27;t topple over. Clojure has fit me so well that I don&#x27;t think I would have accomplished what I have in other languages.