This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-18
Channels
- # admin-announcements (1)
- # beginners (4)
- # boot (18)
- # cider (4)
- # cljsrn (17)
- # clojure (77)
- # clojure-austin (6)
- # clojure-greece (6)
- # clojure-spec (81)
- # clojure-uk (6)
- # clojurescript (32)
- # code-art (2)
- # core-async (12)
- # cursive (1)
- # datomic (1)
- # emacs (15)
- # funcool (1)
- # hoplon (108)
- # om (9)
- # onyx (83)
- # planck (1)
- # re-frame (3)
- # reagent (4)
- # specter (6)
- # spirituality-ethics (4)
- # yada (9)
I think it is wise to start with a low risk project/tool when trying a new language
and if the experience is good, it is natural to use the new lang in more complex things
at IG, we started by building a very low risk/value microservice, just to prove that clj will play nicely with the other enterprisey tools and apps
now we have 2 teams (~10 people) doing clj for new services/projects, but still have to maintain old services, so maybe 50% of the time doing clj at work
but again, IG has like 150-200 devs, so still a small portion