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.
Subject:RE: Quality of source material from Development From:"Jane Carnall" <jane -dot- carnall -at- digitalbridges -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 13 Dec 2001 16:28:45 -0000
Salan Sinclair wrote:
> Yes, Andrew, some writers are less technical than
> you are.
> Whether they should *all* be as technical as you are
> is a matter of debate.
Iggy responded:
That's not Andrew's point. His point is that the
writers should be as technical as they need to be.
They don't need to know what Andrew knows, they need
to know what they have to know in order to do their
job, which is NOT just to write manuals, but rather to
understand the industry, technology, its use, and the
product and relay this information as articulately and
as accurately as possible.
Well, if that's what Andrew meant, why didn't he say so? <g> But more to the
point, my *job* is to write the documentation. That's what they pay me to
do. To separate soma from sarx, my *profession* is, exactly as you say: "To
understand the industry, technology, its use, and the product, and relay
this information as articulately and as accurately as possible."
The means by which I do this range from looking at the code, reading the
specs, talking to the developers (and the project management and the
end-users <when I can catch them> and even marketing/sales and PHBs):
whatever's appropriate. Asking moronic questions <stitch> ...but they have
to be the *right* moronic questions... It would be as foolish to pin a
writer down to "You must find everything out by reading the source code" as
it would be to restrict that writer to "You must use only the written
material the development team supply". One of the things I do find faintly
irritating about debates on this list is that sometimes they become
ridiculously polarised. We are, as you said yourself, essentially in the
position of tying all the threads together. I liked a comment John Posada
made, early on in this thread; "Ask questions that the developer wouldn't
think of no matter what they gave you".
Jane Carnall
Most technical writers make their living describing the smile on the face of
a black cat in a dark room in a house that will be built next week.
Apologies for the long additional sig: it is added automatically and outwith
my control.
E-mail is an informal method of communication and may be subject to data corruption, interception and unauthorised amendment for which Digital Bridges Ltd will accept no liability. Therefore, it will normally be inappropriate to rely on information contained on e-mail without obtaining written confirmation.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Be a published author! iUniverse gives you: a high-quality paperback, a
custom cover design, and distribution to 25,00 retailers. And it's
affordable. Join our alomst 10,000 published authors today. http://www.iuniverse.com/media/techwr
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.