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.
Subject:Re: Tool knowledge versus Task knowledge From:Chris Hamilton <chamilton__ -at- YAHOO -dot- COM> Date:Fri, 2 Oct 1998 04:55:43 -0700
---"Eric J. Ray" <ejray -at- RAYCOMM -dot- COM> wrote:
>
> That said, I'm often struck by just how much effort > we could save
by really understanding the
> technologies and tools that we use. Based on
> postings to this list and others, it seems that many
> of the confusing aspects of being a technical writer
> stem from not fully understanding the tools and
> technologies we use.
But what does that stem from? Lack of time, maybe. A lot of technical
writers need to know the documentation software, the product, delivery
methods, project management, how to win friends and influence people,
and the coming thing on both the documentation side and the product
side. I'm not griping about that; it's part of what makes the job
exciting. But it doesn't leave much left over for learning tools just
for learning's sake.
==
====================
Chris Hamilton
chamilton__ -at- yahoo -dot- com (double underscore)
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
