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: Documenting A Moving Target From:Bob Morse <morse -at- GLOBALDIALOG -dot- COM> Date:Wed, 21 Feb 1996 20:08:53 GMT
Karen Gwynn/Datatel <Karen_Gwynn -at- datatel -dot- com> wrote:
>Problem: I am trying to document a product that is still being developed, not
>just tweaked. By this I mean, something that I documented on January 31, now
>works differently. ......
Sorry I don't have any solution or suggestions for you; seems like this is just the
bain of we tech writers' existence. But I did want to share with you a comment I
heard from a fellow tech writer, who characterized software documentation as "trying
to change a tire on a moving car."
