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'd prefer the writing skills (and creativity) over technical expertise.
>> but that could depend on the type of project.
Rosie Crowe responded:
>..I cannot find much use for a writer without a love for
>and an aptitude with technology. A writer who is a technophobe
>is handicapped in the field of tech writing, and these writers
>drag down the field as much as do the technical-apt-but-unschooled-
AMEN!! Writers who hang their professional hats solely on the fact that
they have outstanding writing skills are a discredit to those of us who work
hard to have the entire package.
Simple truth: This profession, done well, requires a broader range of
skills than almost any other I can think of. If you're a tekkie who can't
write, or a writer who can't "tech," please don't argue that the employers
are wrong-headed in their approach. Go out and get the skills that they're
asking for!!! That way, when I inherit one of your projects, I won't have
to spend the first two months convincing the project team that I am, in
fact, willing to learn how the product works (or worse, spend two months
implementing an intense structure edit, as a direct result of someone else's
As arrogant as that may sound to some, I think it's the key to us getting
the professional respect we've all been longing for. As it stands, we do a
job that's more difficult than software development (IMHO) and get paid a