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.
I may not have communicated my thought properly. Never said there
should be a lack of knowledge.
IMNVHO you can have all the knowledge in the world, but it will not
help anyone else if you cannot effectively communicate that knowledge.
A solid liberal arts background will train folks in how to think and
communicate their thoughts. Then the technical training should take
place. That training need not be formal. It can be self paced,
informal or formal classes, or on the job. Think of tech writing as
both an art and a craft. The craft being the understanding of the
medium, i.e.. Framemaker, Robohelp, etc. The decision of which tool to
apply and how to apply it is an art. Understanding a need and the
difference between a perceived and actual need is an art. Convincing a
client or manager that a perceived need may not be the actual need is
a definite art. (as is knowing when not to do it. <g>).
Reply to pnewman1 -at- home -dot- com
----- Original Message -----
From: Horace Smith <hsmith -at- wt -dot- net>
To: Peter <pnewman1 -at- home -dot- com>
Sent: September 16, 1999 11:50 PM
Subject: Re: Technical Writing Courses
> I beg to differ. I don't care if you can outwrite Shakespeare, if
> know anything, it won't work.