The recent threads on documentation lit a small fire under my butt so I started a Code Genres <https://github.com/mobileink/codegenres> repo. For the moment it is there mainly for the wiki, which I offer as a place for any interested parties to contribute ideas, requirements, etc. I've posted a little bit of stuff there to get started, really more suggestions rather than fully worked out ideas, but they are (so I imagine) mildly innovative. One is that we should think of both code and documentation in terms of literary genres (the inspiration comes from Bakhtin on speech genres), and the other is that we should treat unit tests as documentation (in the sense that they record a trace of actual code behavior). I've got more stuff, but I don't know when I'll find time to write it up. In the meantime if you have ideas you want to record in a stable and relatively visible place (rather than buried in a mailing list) the wiki is open for business.
The main motivation (I think) is that by engaging in fundamentally rethinking code and documentation we may come up with new and better ways of attacking "the documentation problem". -Gregg -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
