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.
>And to bring in another techwr-l thread, at that time (a dozen years
>ago), I had only heard the term "technical writing" once and had
>*no* idea what a technical writer did ... I was planning to go back to
>school for linguistics because I thought that my undergrad. studies
>in Computer Science only qualified me as a programmer (and I
>don't like working as a programmer). Even now, I find that many
>people don't know what a "technical writer" does.
>
What a tech writer does is a variable. I was once a tech writer, but I
would have to start from scratch to be a tech writer today, as most of today's
tech writers might be unable to handle the tech writing of my day--the Cold War
and arms buildup era. And perhaps the tech writing of few years from now will
be markedly different again. - Herm
====================================================
Herman Holtz, Writer-Consultant - Latest book: The Concise Guide to
Becoming an Independent Consultant (John Wiley & Sons, 1999).
Writing support services. Recommendation & estimates, no obligation.
