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?
_Any_ aspects that make a product difficult to document? Hmmm...
There was one release where I was in San Diego and all the product
engineeers were in the United Kingdom. Email couldn't handle my
document format, so we were snail mailing reviews across the Atlantic.
There weren't any specs, and I never had a chance to use the product.
I'm sure other Tech Writers have similar war stories. Yes, I finished
this release (Fed Exing 2,000 pages of final copy). But _any_ aspects?
>No-one ever said this job was easy--that's why tech writers are
>compensated as they are.
We are probably not fully compensated for our relative skill and
problem solving levels.
David (The Man) Blyth (dsb -at- thomsoft -dot- com)
Technical Writer
Thomson Software Products
My opinions are not necessarily those of my employer (but they should be).
