RE: Rule of thumb for doc time based on development time?

Subject: RE: Rule of thumb for doc time based on development time?
From: Chris Gooch <chris -dot- gooch -at- lightworkdesign -dot- com>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Mon, 12 Dec 2005 12:47:15 -0000

John Posoda wrote:

it's probably an
inverse number. By that, I mean that if development spends ALOT of
time on creating a truly inteligent feature with lots of analysis, it
will probably take a short period of time to document it. OTOH, if
they just slap it together, it is going to take MUCH longer to
document it because you have to deal with something that is not
intuitive and needs lots of qualifications.

This corresponds with my experience too. Well designed
and put together software is easier to document than
poorly thought out software. Guess which takes less
time to develop?

Christopher Gooch, Technical Author
LightWork Design, Sheffield, UK.

Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today!

Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release.

You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

Previous by Author: Re: RoboHELP baby
Next by Author: Re: Word Problem
Previous by Thread: RE: Rule of thumb for doc time based on development time?
Next by Thread: Wiki vs. RoboHelp

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

Sponsored Ads

Sponsored Ads