This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-05
Channels
- # architecture (3)
- # aws (4)
- # beginners (100)
- # boot (14)
- # cider (59)
- # cljs-dev (1)
- # cljsrn (24)
- # clojure (53)
- # clojure-dev (58)
- # clojure-italy (2)
- # clojure-spec (1)
- # clojure-uk (25)
- # clojurescript (7)
- # cryogen (1)
- # cursive (1)
- # datomic (9)
- # dirac (9)
- # duct (3)
- # off-topic (52)
- # om-next (3)
- # onyx (42)
- # portkey (28)
- # re-frame (3)
- # reagent (11)
- # rum (3)
- # shadow-cljs (12)
- # specter (7)
- # tools-deps (18)
- # vim (1)
- # yada (4)
It seems suitable to me for a system that is strictly defined with relation to some domain, especially when that domain is based on fairly immutable concepts, e.g. a mathematical foundation. Low chance of code intent changing means literate docs will likely remain fairly stable as well.
@fellshard Yeah... but I don't think I've ever worked on a system that is like that... the real (business) world seems very fluid in terms of requirements and domain rules... 👀