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.
>Don't interview programmers until you know what you're documenting. You'll
>just come off as unprepared and irritating.
And it's better to ask questions that show that the programmers do not know what
they're doing. IMHO, if you hoist them by their petards, they'll give you better
I think it works because it shows the programmer that you're not afraind of
running the system to find yr information.
Heck, I had a few programmers, in a previous position, that *wanted* me to run
thru new features, knowing that I, in trying to doc the damn thing, would find