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.
> Meaning no disrespect but, shouldn't a good technical writer be able to
>get around any aspects that make a product difficult to document?
The problem is, as someone wiser than me --Edmund Weiss, I think--has said:
"If it's hard to document, it's hard to use."
So every time I get a developer to change the software so that it is easier
for me to document, I'm also doing our users/customers a favor. And maybe,
if I do that part of my job well enough, they won't even need to open my
silly manuals. (What a life!)
--Heli
=======================
Heli L. Roosild
helir -at- msmailhq -dot- netimage -dot- com
