3 ms·

I think you have a very high bar of "minimum viable"! IME you don't need to have Java experience previously, you can just pick up needed bits of JVM as you go

I think you have a very high bar of "minimum viable"! IME you don't need to have Java experience previously, you can just pick up needed bits of JVM as you go - which is less than you make out. I'm sure you can approach things from a Java expert angle as well and leverage your tooling etc knowledge from there, no doubt it helps a bit in the beginning. I think (3) would be an equally valid requirement for a Python, JS, C++, or Java developer.

lmilcin 6y ago
I say this after observing Clojure project at the bank I work for and from other projects I observed in the past. The guys knew a lot but left a big pile of unmaintainable crap. IMO minimum viable developer should be able to not trip on their own feet. Generally be able to produce working, maintainable application. In Clojure (and other Lisps) this absolutely requires you to be able to structure application. If you use other languages, the frameworks that are there do the work of structuring for you. That's why when you are Java developer, every web app largely looks the same. That's because you don't actually structure application, as much as use structure that is offered with Spring ecosystem.