docs

About docs of Clojure & libs
2017-12-28T20:04:59.000052Z

Thanks! I should have looked harder…

2017-12-28T20:28:34.000192Z

@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

arrdem 2017-12-28T20:37:54.000255Z

@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.

2017-12-28T20:41:18.000068Z

> 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).

arrdem 2017-12-28T20:49:47.000116Z

Yeah that was kinda Allan's argument today - the code is incidental and it's particular behavior is aspirational towards some actual goal(s)

arrdem 2017-12-28T20:51:21.000064Z

Particularly for business systems not libraries

2017-12-28T21:29:57.000140Z

> Allan’s argument today I think im missing some context. Who is Allan?

seancorfield 2017-12-28T21:34:11.000290Z

Allan Rohner -- the @arohner mentioned above.