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: The user guide prescribes the program From:Peter Gold <pgold -at- NETCOM -dot- COM> Date:Mon, 6 Jan 1997 12:21:58 -0800
I can't quote "accepted standards" for this, but just think about it from
a slight distance:
Docs are the project blueprints. If all the people leave the project, and
the prototypes are lost, and the factory is lost, but the excellent docs
survuve, the project can be recreated more-or-less straightforwardly from
the blueprints. Without them, good luck!, no matter how many of the other
components remain.
Peter Gold
On Mon, 6 Jan 1997, joe rapp wrote: [snipped]
>
> This engineer told me it is standard thinking that the
> computer program IS the user guide, while the code is just
> the code. If the program "doesn't work" properly, then
> changes are made to the code -- not vice versa.
>
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
