Re: Documenting a Mess

Subject: Re: Documenting a Mess
From: Linda Moore <lhmoore -at- pobox -dot- com>
To: TechWR-L <techwr-L -at- lists -dot- raycomm -dot- com>
Date: Fri, 12 May 2000 12:05:46 -0700

This is what I would do under similar circumstances, which I might add,
I have been in. Explain to your management that to document this program
is its present condition is going to require more time by a factor of 2,
3 or 4 times as much as it would normally take you, if the product was
well designed. Suggest that they hire a VB guru to test the code to see
how solid it is and to provide an estimate of how long it would take to
modify the current program or redo the program. I can almost guarantee
that this marketing guy has left logic holes big enough to drive a truck

If the current path is maintained, poin out that n addition to the
increased documentation costs, there will also be increased support
costs as well as increase in dissatified customers. One of the benefits
of getting a top VB guru is that even if he redoes the code, it will
take him far less time to complete the task. You can be documenting and
testing behind him so both products will be completed in a timely

Linda. Moore

Previous by Author: Re: Need help with a term
Next by Author: Re: TOOLS: MS Word numbering frustration
Previous by Thread: Re: documenting a mess
Next by Thread: RE. Documenting a mess?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads