This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-12
Channels
- # aws (3)
- # beginners (28)
- # boot (3)
- # cider (28)
- # clara (5)
- # cljs-dev (107)
- # cljsrn (1)
- # clojure (40)
- # clojure-austin (2)
- # clojure-brasil (5)
- # clojure-canada (1)
- # clojure-italy (1)
- # clojure-spec (39)
- # clojure-uk (38)
- # clojurescript (33)
- # community-development (11)
- # cursive (11)
- # datomic (43)
- # duct (6)
- # emacs (7)
- # flambo (1)
- # fulcro (68)
- # graphql (11)
- # jobs (1)
- # jobs-discuss (8)
- # leiningen (16)
- # luminus (2)
- # lumo (1)
- # off-topic (38)
- # om (2)
- # onyx (15)
- # parinfer (32)
- # portkey (5)
- # re-frame (50)
- # reagent (50)
- # reitit (1)
- # shadow-cljs (63)
- # spacemacs (10)
- # sql (27)
- # unrepl (6)
- # yada (2)
Maybe they need OO skills because the Clojure stuff will be interacting with OO stuff in other languages, and it'll be easier to communicate & collaborate with the other team if you have some familiarity with OO stuff?
I hope the reason is that maybe it's a full stack job using cljs. ...But why have cljs on the FE and the other langs on the backend, I'll never know
CLOJURE ENGINEER Requires: - Some OO lang experience - Lots of OO - Definitely OO - Preferably in an OO language (or C) - HTML and JS, too ... - Oh yeah, and Clojure
although, really distilling the good parts of OO is orthogonal to Clojure. In my latest team I was the only one strongly pushing for defprotocol
usage. Also I recall using Composite pattern (admittedly a easy/universal one, but you get the idea)