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 have never worked directly with an engineer to create documentation,
but I do have to parse a god-awful amount of technical data. The one
thing I can say is that most of the time I don't know whether the docs
have been written by an engineer or not, but whenever a document has
OBVIOUSLY been written by an engineer it's not a GOOD thing.
(That's right, Kia, I'm talking about your manuals!)
-BH
From: Gene Kim-Eng
The comments I usually get from engineers is something along the lines
of, "you repeated what I told you, but you managed to do it using half
as many words." I've worked with engineers who could have done as good
a job of writing their documents as I could, but just not as fast as I
could. And I've NEVER worked with any engineers who actually WANTED to
write their own documents. My experience with the SMEs I have worked
with has been that when they told me it would have been easier for them
to write a document themselves than to work with the last writer they
had, most of the time it turned out that they were right.
--
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
