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.
Or Karen could not know what she's doing right, and so she
couldn't tell the interviewer, "I haven't had conflict because..."
My best response from engineers and other technical people has
resulted from my being able to explain what *I* was doing, and why, in a
clear way. Coupling the ability to articulate the documentation process
(data collection, doc specs, writing, and editing)
with a demonstrable effort to understand the language of the
engineers/technicians has been the key to gaining the cooperation of SMEs
for me.
Mary
Mary Durlak Erie Documentation Inc.
East Aurora, New York (near Buffalo)
durl -at- buffnet -dot- net
On Fri, 20 Feb 1998, Mark Baker wrote:
snip>
> So, if you have never argued with an engineer, it has to be because you have
> been incredibly lucky with the engineers you have had to deal with, or
> because they have never read your documents, or because you have failed to
> create documents which are functionally accurate.
>
