From: Eric Armstrong <Eric.Armstrong@...>
Date: 2006-05-16T11:06:53+09:00
Subject: Re: Ruby & Emacs

Similar, but with an important difference. The user
guide tells someone how to use the program to do what
they need to do. It's necessarily use-case oriented.

Comments tend to be implementation-oriented. They
tell how the /program/ does what it does. The user
guide tells the /user/ how to do what they need to do.

James Britt wrote:
> Eric Armstrong wrote:
>> First, thanks to John for pointing out that FreeRide
>> is most likely exactly the thing I'm using for.
>>
>> Next, Pistos:
>>
>> After many years coding, I became a writer. But I
>> still code whenever I can. But the result of the
>> writing experience led me to start writing the user
>> guide as part of the design process.
>>
>>    Note for aqile developers:
>>    The user guide is one of process artifacts at
>>    every stage. You modify it at the start of each
>>    cycle to explain what you plan to have accomplished
>>    at the end of the cycle. If the plan changes, you
>>    modify the document accordingly.
> 
> Similar to what I call "comment-driven development"
> 
> 
>