TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Software documentation on the critical path From:Sandy Harris <sharris -at- dkl -dot- com> To:Pierre Roberge <proberge -at- famictech -dot- com> Date:Wed, 20 Oct 1999 10:37:32 -0400
Pierre Roberge wrote:
> I started writing my guides based on the specification documents, which
> lacked a lot of details. I used the alpha version developers release
> internally every 2 weeks to update/modify my guides. I worked in parallel
> with them during the coding phase and will work that way until they finish
> coding. Is there another faster/better way to work? If the specs were
> frozen I could have finished the documentation before the developers
> finished coding but the specs are too vague and they change along the way.
> I have no choice to use the actual product to really know what it does and
> how it does it.
Why is working from a spec like walking on water?
Most people cannot do it unless it is frozen.
