Clojurians Log v2

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)

Particularly for business systems not libraries