I recently came across a problem where the journey to the solution reminded me how awesome the notion of community can be.
First, a brief overview of the problem: we wanted to create and deploy a Clojure application, which would get access to the continuously-deploying, load-balancing, status-monitoring goodness offered by our infrastructure team. To do so, we had a responsibility to get our Clojure application to report it’s version number at runtime. It was one of those seemingly simple problems that gets a bit trickier when you realise it not only involves our code, but also our continuous integration (Jenkins) and build tool (Leiningen).
One of the aspects to solving this involved Leiningen, and I’d like to use this post to praise the Leiningen community, who helped us with our problem. In the #leiningen IRC room on Freenode, some friendly folk listened to our questions, responded for further details, and offered helpful and sensible advice. From the comfort of my house, I was able to chat with the likes of Chas Emerick (co-author of O’ Reilly-published “Clojure Programming”) and Phil Hagelburg (aka technomancy, the creator of Leiningen). I don’t think that kind of accessibility and approachability should be underestimated. It’s brilliant.
Our team is still new to Clojure and it’s community, but I’m impressed with my first interaction. I wanted to take that kindness and pay it forward somehow. Intersecting with another great community, StackOverflow, hopefully achieves that. I’ve described the advice I got on #leiningen, and the other steps we had to take to fix our issue, in StackOverflow’s Q&A format. This way, the time spent by those kind folks answering my questions can be saved, made searchable, and improved upon in the way that the StackOverflow site and community is great at.
Happy community-ing everyone.