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:FW: re-creativity in technical communication From:Shlomo Ramon <ramsol -at- NETVISION -dot- NET -dot- IL> Date:Sun, 30 Mar 1997 18:17:47 PST
---------------Original Message---------------
Date: Sun, 30 Mar 97 17:38:15 PST
From: ramsol -at- NetVision -dot- net -dot- il
Subject: re-creativity in technical communication
To: TECHWR-L -at- LISTSERVE -dot- OKSTATE -dot- EDU, midannen -at- SL -dot- BOSH -dot- DE
Return-Receipt-To: ramsol -at- NetVision -dot- net -dot- il
X-Mailer: Chameleon V0.05, TCP/IP for Windows, NetManage Inc.
Message-ID: <Chameleon.970330180538.ramsol@>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hello Mike,
you wrote: "technical writing requires creativity, otherwise the engineers
could do it..."
I beg to disagree with that statement, without starting a new major war.
Admittedly, I have not researched the educational background of accomplished
technical writers, yet my hearsay and experience presume that quite a
significant number has some kind of engineering/scientific background. And
why the assumption that good engineers must be devoid of creativity? IMHO,
both concept, system and detailed designs of any program or even of a humble
device involve a fair amount of imagination and of creativity, on top of
regular qualifications and specific skills.
It just occurred to me that many good engineers lose the interest in their
tasks once the design is completed and just could not be bothered to write
proper user documentation because of lack of interest and because most were
not taught the basics of how to..This might be connected with the different
doctrines for training engineers: the current technology versus the basic
sciences oriented approach - but that is another subject.
Speaking only on my behalf, as former (more or less) successful EE turned to
technical writing on his own volition.
-------------------------------------
Name: Shlomo RAMON
E-mail: ramsol -at- NetVision -dot- net -dot- il
Date: 03/30/97
Time: 17:38:15
This message was sent by Chameleon
-------------------------------------
----------End of Original Message----------
-------------------------------------
Name: Shlomo RAMON
E-mail: ramsol -at- NetVision -dot- net -dot- il
Date: 03/30/97
Time: 18:17:47
This message was sent by Chameleon
-------------------------------------
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
