Actually, I am no longer getting any headaches since I started using
Fusedocs. However, I can certainly see the benefit of what you are saying.
I will certainly work on that. I think that it will mostly be a matter of
discipline ("I am just the programmer now, I am just the programmer now").
There is always that huge temptation to wear both hats at the same time. I
must resist!
Thanks!
Steve
At 10:59 AM 5/24/2002 -0400, you wrote:
> > Steve Bryant wrote:
> >
> > I am certainly no expert on this, but for myself I
> > try to do both. I write my Fusedocs and then my code. After
> > my code is all written, I go back and clean up my Fusedocs
> > to make sure that they match how my code was actually written.
> >
>I can imagine that would be a headache! The trick is to take
>off your architect hat when you're coding. Make the code do
>what the Fusedoc specifies. Pretend you don't know anything
>about the rest of the application, and all you have to go on
>is that Fusedoc. That way, the code should be perfect with
>respect to the Fusedoc. If there's a problem at integration
>time, the problem will be at the Fusedoc level. So you fix
>the Fusedoc, and then update the code accordingly.
>
>Think of it this way: The only reason you should ever write
>code is in order to satisfy the requirements of a Fusedoc.
>
>
>Patrick
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
