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 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
