Clojure Design Patterns
Clojure is fantastic for its simplicity, and I worked on a Clojure code base full time for 5 years, coming up with ways of translating Java patterns into Clojure. But I&#x27;ve noticed it has not been gaining traction in the job market, and now I feel like that 5 years has been a waste of valuable career building time, which I wish I had spent gaining more experience in (<i>sigh</i>) C# and .NET, so that I could get the more local jobs which all seem to use the Windows ecosystem, so we don&#x27;t have to uproot our family and move to the city. Not that I don&#x27;t know C# and .NET, but I definitely don&#x27;t have 3+ years experience in it and I definitely don&#x27;t have any experience MS SQL. So being able to do really cool things in Clojure, and especially having excellent rapid development skills with REPL-driven development, has done me no good. The one remote job that I found that uses Clojure turned me down because they used zippers in the code test, and that&#x27;s literally the one Clojure construct I just can&#x27;t wrap my head around, which is ironic because idiomatic Clojure really doesn&#x27;t use recursion in the first place, favoring streams and transducers instead. My career future doesn&#x27;t really seem to have a lot of Clojure in it unfortunately. Plus most of modern JavaScript has most of the same benefits as Clojure anyway, especially in terms of FP.