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.
> But if you're documenting a system that requires installation,
> configuration, and various forms of integration with other systems, then
> you're not doing your readers any justice if you don't understand the
> technology.
But the subject was the *baseline* skills needed to be a tech writer. I'm not
saying we don't need technical knowledge, but the average tech writer does not
need this depth of knowledge of any one particular technology unless they are
writing for that audience. Any of our areas of specialization (including mine)
are not necessarily the lowest common denominator.
--
=======================================================
Tracy Boyington mailto:tracy_boyington -at- okvotech -dot- org
Oklahoma Department of Vocational & Technical Education
Stillwater, Oklahoma http://www.okvotech.org/cimc
=======================================================
