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.
In many cases, I would agree with Andrew that existing technical
knowledge
is invaluable when writing technical material about a certain subject.
I've been
writing in and around network computing for umpty-ump years now, and the
concepts and acronyms are nearly second nature. This certainly lets me
get
started quickly on new projects in related fields. But I find the
ability to talk
to my different audiences (users, programmers, potential customers) and
analyze their needs is at least as important as my technical background.
FWIW, my educational background is English and communications. So I
guess I count myself as both a technical (when needed) and non-technical
writer. (But I do my best to never get drawn into the bullet shape,
color,
and font wars. A total waste of time for any project worthy of the name
"technical," IMHO. Now you know why I _like_ being a technical writer.)
I also believe that the ability to think analytically and learn technical
material is more of an individual trait than anything else. Tarring any
program
or school with the "political correctness" brush to account for
individual
deficiencies strikes me as (ahem) sloppy thinking.
