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.
On Fri, 28 Jul 2000 11:10:24 -0700 (PDT), Tom Murrell wrote:
>It tends to annoy me when people focus on one or the other of these two
>concepts as somehow the only one that is important. (As in, "Any idiot can
>write. What you need is to be technically competent." Or on the other hand,
>"I'm a Writer, not a mechanic, Jim!" <g>) I think a writer can be an effete
>snob, to quote Spiro Agnew, something I rarely do. And I think a geek can churn
>out words that may, or more likely may not, communicate something to an
>audience. But it takes a Technical Writer, a true Technical Writer, to marry
>the two into the discipline we practice under the rubric of Technical Writer.
I want to join the discussion for one second and describe my point of
view: "I am too _stupid_ to be a programmer and too _intelligent_ to be
a user only, so I become a technical writer".