Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I do agree. While I made all my projects in mostly Clojure, I absolutely cannot imagine hiring & onboarding other drvs.

And if I had a tough day, my clj code will look like rubbish, while my typescript code will still look decent.

It's really not a language for big team.



I have onboarded developers coming directly from university and it went fine?

In fact, at my old job, the entire team learned Clojure on the job. I was the only hire who had learned it prior to being hired. Our codebase was fine and very maintainable.

The other teams were similarly new to Clojure. Most people spent a few months doing increasingly more advanced things until they were comfortable with the language and the codebase.

The main issue for complete beginners is learning to grapple with the different development setup compared to what they might be used to, i.e. interactive development on a live system using an editor-integrated REPL. We basically set everyone up with IntelliJ and parinfer. Paredit was optional, as was alternative editors such as emacs.

IntelliJ + parinfer is a similar development experience to Python. The only part that is foreign in that case is the interactive development of a live system which the new devs quickly come around to seeing the benefits of. It helps having seniors who point out the new concepts.


> It's really not a language for big team.

Not my experience, but you do need senior devs who are good at Clojure to be reviewing and helping the juniors

> if I had a tough day, my clj code will look like rubbish

This may not be a reflection of the language




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: