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.
KG> Problem: I am trying to document a product that is still being
KG> developed, not
KG> just tweaked. By this I mean, something that I documented on
KG> January 31, now
KG> works differently.
I know this difficult situation :-(
There are a few strategies to cope with this problem:
- Try to delay the description of details.
- Leave many details to the online documentation.
- Concentrate (if they let you) on the user interface of the
program. If you improve that, you have less to explain afterwards.
No real solution, but a few ideas...
BTW: Many have known me as a regular contributor to this list but I had nearly
disappeared during the last months. Last week I moved to a new location and
that only was the final stage of a private disaster. But the future looks
Greetings from Germany,
|Fidonet: Alexander Von_obert 2:2490/1719
|Internet: avobert -at- twh -dot- msn -dot- sub -dot- org
| Standard disclaimer: The views of this user are strictly his own.