On 8 Jun 2007, at 07:09, chromatic wrote:
Fiddling with the POD before I’m done is beyond pointless.
I'm willing to bet that you write documentation as the last task
before
bundling a release too. That's also my style.
Sometimes I write the POD as a storyboard of how the module's
interface should work then write the code to implement it - tweaking
the story the POD tells as I go.
Sometimes I write a bunch of code with no POD and then document it.
Sometimes POD and code evolve in parallel.
Aristotle's point about being able to read the POD as a continuous
narrative is a big factor for me.
I can see the benefits of keeping a method and its documentation
adjacent. Intuition would would pull me in that direction - but
practice pulls me in the other direction. When I have my
documentation head on I just want to see documentation.
--
Andy Armstrong, hexten.net
