| I've been at an organization that went from Java to Clojure about 12 years ago. I think there were two main things that allowed us to make the move: * No one was in love with Java. It was fine but we were doing the whole spring style super verbose Java and it felt like a lot of ceremony to get anything done. There had been an experiment with Scala previously but that hadn't taken off. * We had a service-oriented architecture which meant we could try Clojure out on a few new services and see how it felt. We ended up going from 2 services to moving the whole org over really quickly. A lot of excitement built up and people didn't want to be left out. At the end of things only 2 people decided they didn't want to learn Clojure. A few other things we did: * Bought loads of books and left them lying around * Started a Clojure club where we booked an hour a week and did some exercises in Clojure * Had a big meeting where we convinced everyone that Clojure was worth an experiment * Brought in 3 consultants to do some Clojure training for everyone * Probably strong armed everyone into watching simple made easy - it helped that lots of people had already seen it live that year There are a few talks about it floating around although they are very very old now and I'm not sure they're worth the time! https://whostolebenfrog.github.io/clojure,/deployments,/clou... |
At strategic locations? Such as the bathroom?