This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-28
Channels
- # adventofcode (6)
- # beginners (61)
- # boot (1)
- # chestnut (1)
- # cider (18)
- # cljs-dev (1)
- # cljsrn (3)
- # clojure (176)
- # clojure-android (8)
- # clojure-germany (12)
- # clojure-russia (4)
- # clojure-spec (7)
- # clojure-uk (5)
- # clojurescript (28)
- # css (10)
- # cursive (36)
- # datomic (7)
- # devcards (1)
- # docs (8)
- # emacs (17)
- # fulcro (29)
- # hoplon (28)
- # lein-figwheel (3)
- # leiningen (37)
- # lumo (1)
- # off-topic (54)
- # om (6)
- # re-frame (2)
- # reitit (7)
- # ring-swagger (23)
- # shadow-cljs (115)
- # sql (10)
- # uncomplicate (1)
- # unrepl (24)
Thanks! I should have looked harder…
@arrdem You have given a lot more though to documentation then i have. I was curious if you might have any feedback on an idea i have had that i sketched up here: https://github.com/drewverlee/narrative
@drewverlee cool! I'm flying in a minute here but I'll definitely get back to you. I agree largely with your premises that the narrative and goals are important and capturing those is definitely something I have in mind with stacks. Was talking with @arohner about this today and that's arguably more important than the code or generated docs. Don't particularly think that essays or artifact commentary belong in the code tho.
> Don’t particularly think that essays or artifact commentary belong in the code tho. I’ll need to think about that more, my gut agrees with you, its possible i can get the same effect another way with less coupling between documentation and business code (which i agree is a con).
Yeah that was kinda Allan's argument today - the code is incidental and it's particular behavior is aspirational towards some actual goal(s)
> Allan’s argument today I think im missing some context. Who is Allan?
Allan Rohner -- the @arohner
mentioned above.