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.
-> I don't put inappropriate stuff in documents because I never know
-> when a review copy is going to be xeroxed. Remember, a review copy i
-> always newer than whatever the reviewer has already, and it doesn't
-> take long for copies to diffuse through the organization, and even
-> to customer sites, without your knowledge.
There is always the chance that something like that will make it into
the final version. I have in my posession a software manual that rambles
poetically (and irrelevantly) about the program's features, then
suddenly stops, and says
ASK ZACK FOR MORE HERE
then continues with more content-free narrative. If Zack had had a
chance to contribute, no doubt it would have said something rather than
nothing.
The moral of the story? Don't be a Zack. Don't put anything in your .DOC
files that would make you look like an idiot if it were to make its way
into print.
