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.
CC> I think the challenge is to structure the information so that the
CC> how-come information is available but avoidable (easy if you have
CC> hypertext!). Failing that, I've started putting the conceptual
CC> information after the procedure. This offends my writerly
CC> vanity, but I think it makes the topics more usable.
I agree whole heartedly.
I suspect the psychology of the engineer/documentor relationship
ruins a lot of good products. Seems to me that if the documentor
isn't in on the design of the product from the beginning, then
the battle is lost. Perhaps if documentors were renamed document
engineers, the engineers might give a few positive grunts.
Peter
*************************************************************
* Peter Montgomery Montgomery -at- camosun -dot- bc -dot- ca *
* Exitus effigium effigies exituum *
*************************************************************
