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 am amazed when I hear writers say they wrote documentation for an
>application and have never used the application...
And Barb Philbrick responded:
>Please say it ain't so! ...
>Do many of you write documents without using the equipment or
I think (hope?) this happens less often than it used to. In my hardware
writing days I sometimes turned out hardware manuals for a relabeled
of equipment from the original documentation, without ever seeing the
equipment itself. At that same company, I distinctly remember arguing
long and hard that I needed to have admin priviledges on the system if
I was going to write the System Administration Guide. I won that one.
It certainly isn't the case now, though I could wish we had a longer
cycle for the docs after development finishes an upgrade.
Back to the original topic of this thread, I'm interested to hear that
that a knowledge of programming languages is more of a hiring litmus test
a real job requirement. Just as I always suspected!