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:Learning/researching phase of writing From:Richard Sobocinski <"Richard_G_Sobocinski%~WHC207"@CCMAIL.PNL.GOV> Date:Thu, 19 May 1994 16:54:00 -0700
*Text item: Text_1
I'm curious how folks on the list tackle the learning/research phase of
writing.
What do you find most beneficial: Interviewing developers, hands-on
experience
with a beta product, looking at actual code, design specs, etc.?
What works? I'm asking because I find interviewing developers is the least
efficient and most frustrating. But maybe that's just me. :-)
Erik Larsen
Erik_Larsen -at- ccm -dot- jf -dot- intel -dot- com
-=-=-=-=-=-=-=-=-=-=-=-=-
I find hands on experience the most helpful along with some
knowledge of the code (on a *very* basic level - I'm a
writer, not a code jockey). I contact the developers when I
have specific questions about holes in my understanding (some
of these guys can go on and on about the most arcane
details). In my experience I also find that if possible, it
helps to be around at the beginning to provide some "human
factors" input.
