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'm not sure anyone is saying that the writer should be a complete
novice. I think what some people argue -- myself among them -- is that
you can do a better job of writing about a product if you START OUT by
bumbling around with it as a novice, because then you can see all the
things a new user will trip over.
-----Original Message-----
From: Mark Baker [mailto:listsub -at- analecta -dot- com]
Sent: Monday, March 01, 2004 1:13 PM
Subject: Re: RE: Documentation Architect vs. Technical Expert !
[snip]
The argument on this topic often breaks down into sniping between two
equally untenable positions, one that the writer must be an engineer on
par with the lead developer, and the second that the writer must be a
complete novice who knows nothing of the product or the tasks for which
it is used. Both of these positions are nonsense. The writer needs to be
knowledgeable in the trade and tools of the audience he is writing for.
