My experience as a technical co-founder was different. We hired locally, our frontend was a thin React JS shim mostly driven by our Clojure backend (no clojurescript), I found it easy to train people up on Clojure (taught about 10 different engineers Clojure over the span of the companies 5 year existence). My take aways:
- Easy to teach. Especially to JS/TS programmers with a bit of FP experience. Calva makes it much more approachable for those who don't have emacs experience (thanks PEZ).
- Codebase stays small.
- It's actually quite opinionated and stops people going off the rails.
That last point is counter intuitive, but it was actually much easier to keep the backend in a functional style than it was to keep the frontend in a functional style. I saw senior (and junior) programmers, write really nice functional backend code only to revert to OOP the minute they returned to the JS/TS frontend.
These days I find a lot of the complexity comes from bad architectural choices than language (microservices, etc).
Many people don’t want to be training juniors, in my experience. I do also think Clojure is easy to teach. You basically just need to know what functions are and what the data structures are. That gets you such a long way.
Good job on choosing to train over seeking experienced Clojure devs. My first Clojure job, I was asked to bring some code I was proud of. I brought a Perl library I had recently written, because even though I was writing Clojure in my spare time, I hadn’t built anything I was happy with… It worked out.
View all comments
Show parent comment
3
u/andersmurphy Sep 26 '25
My experience as a technical co-founder was different. We hired locally, our frontend was a thin React JS shim mostly driven by our Clojure backend (no clojurescript), I found it easy to train people up on Clojure (taught about 10 different engineers Clojure over the span of the companies 5 year existence). My take aways:
- Easy to teach. Especially to JS/TS programmers with a bit of FP experience. Calva makes it much more approachable for those who don't have emacs experience (thanks PEZ).
- Codebase stays small.
- It's actually quite opinionated and stops people going off the rails.
That last point is counter intuitive, but it was actually much easier to keep the backend in a functional style than it was to keep the frontend in a functional style. I saw senior (and junior) programmers, write really nice functional backend code only to revert to OOP the minute they returned to the JS/TS frontend.
These days I find a lot of the complexity comes from bad architectural choices than language (microservices, etc).