Too much code, not enough writing

[William la Forge]

I long ago concluded that code should, for me, be mostly something to write about rather than an end in itself. Yet I persist in writing a lot of code and doing very little writing. The consequence is that the code goes largely unappreciated and remains quite opaque to others as I have not established the context nor defined the utility of that code. I remain way to close to the code and it is so clear to me that I rarely appreciate the need for any explanation at all!

From my perspective then, I am failing to accomplish anything worthwhile. I have learned much from my limited exposure to Clojure, and those lessons are very important to me. But the path I am on now promises only greatly diminished returns.

[Raoul Duke]

Dunno if literate coding would be a way to have cake & eat it?

[William la Forge]

Played with it in Clojure, but the tool was limited. Happily clojure has helped me make my code stable enough that including code snippets into the docs has become reasonable. :-)

I'm thinking I need to write more about my intentions. Release notices do not seem to encourage participation. :D

On Mon, Nov 16, 2015 at 11:57 AM, Raoul Duke <rao...@gmail.com> wrote:

Dunno if literate coding would be a way to have cake & eat it?

--
You received this message because you are subscribed to the Google Groups "AgileWikiDevelopers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilewikidevelo...@googlegroups.com.
To post to this group, send email to agilewiki...@googlegroups.com.
Visit this group at http://groups.google.com/group/agilewikidevelopers.
For more options, visit https://groups.google.com/d/optout.