I have recently been playing with Clojure for personal projects. It is quite addictive. Also I am shocked by its leverage and how productive I am in it.<p>Now at work (Java and C++) I am constantly thinking of ways of getting my next Clojure fix.<p>How should I solve this problem? The problem is that I would rather program in Clojure than anything else. Here are some ideas and issues with them.<p>1. Switch jobs. Except that most of the jobs on Craigslist (SF Bay) that mention Clojure list it with five other buzz words. It sounds like interview bait. There is no guarantee there will be Clojure on the job.<p>2. Ask my company to use Clojure. I suspect they will not be open to this because they have a mob of Java programmers who won't understand the code. They rejected another person's request to use Scala a few months ago. Still worth a shot. But I can see the PHB eyes glazing over.<p>3. Create a web-based start-up using Clojure. Despite Clojure's productivity this will take some time. This is the path I am working on right now. But it seems like such a long slog.<p>Ideas?
I am a "PHP" developer at work. All day I sit around writing "PHP" code. Here is how I start my day: <i>"You guys want this done quickly and reliably or should I do it in PHP"</i> ..<p>We're a PHP shop with a huge Common Lisp code base.
Use Clojure to generate your Java code. As far as anyone else is concerned you're writing Java.<p>I've used code generation at work quite a bit, whenever I've had somewhat repetitive code to write that I couldn't factor away. It makes my job a lot less tedious and more fun.
Get some busines knowledge in some domain. A lot of business folks do not care about what technology one uses as long as one can solve their problems using it.<p>We are actively using Clojure, located in New York City and looking for programmers with financial experience. Send resumes to (->> ["dimitry" :dot "gashinsky" :at "picotrading" :dot "com"] (replace {:at \@, :dot \.}) (apply str))
I recommend #3. Hang out on IRC & the groups, open source the non-secret-sauce from your startup. Build a brand around yourself as a badass Clojure programmer. Best case scenario, you have a successful startup. Worst case, you're a well known Clojure expert, and someone will hire you to work for them.
There is a company named WeatherBill which I personally know is interested in hiring Clojure users. (I think the only online advertising they did was a tweet which was maybe picked on disclojure.org.) One person there recently told me that they're very friendly to telecommuting -- but only within the US.<p>(This telecommuting thing probably doesn't matter much to you, given they're IIRC in SF, but others might like to know that...)<p>BTW, have you tried going to Clojure meetings, if there are any in your area? Some people prefer to go to them to find coworkers.
You can sneak a lot of functional style programming into Java/C++. It's easier with C++ because they have first class functions, but you can do a lot even with Java. I think it's not optimal to do a 100% functional style, even though you can, because all the syntax junk gets in the way, but just by thinking in terms of higher order functions instead of objects it will make a lot of the pain go away.
Challenge yourself by thinking whether you could write better java code, in the light of your new knowledge from the clojure side. Straightforward example: produce far more orthogonal java code by using composition and the strategy pattern more, programming more to interfaces and delegating more some "general" work on interfaced objects to static methods in helper classes, etc.<p>That is, don't throw the baby with the bath water. Though coming with more "boilerplate" (as in "more ceremony"), there are still ways of programming in java that can make you happy at the end of the day: when you feel that your code is more DRY (which does not necessarily mean less code, BTW), and more orthogonal (more interfaces -e.g. callback interfaces- are generally a step in the right direction, though not necessarily a general rule).
Don't ask for permission. Recognize the need for something important at work and write it in Clojure and often coworkers/bosses will be so glad to have it and not have had to write it themselves that they won't care what language it's in. Of course now you're responsible for it.