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: Techwriting history From:letoured -at- together -dot- net To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 28 Aug 2002 12:15:39 -0400
In <200208280913 -dot- 17K2Ds2XI3Nl3pm0 -at- niles -dot- mail -dot- mindspring -dot- net>, on 08/28/02
at 02:13 PM, "Martin Page" <mpage -at- csl -dot- co -dot- uk> said:
>OK, you caught me being flippant. Mea culpa.
Oh, I wasn't trying to criticize. I was just trying to make the point that
life-experience changes the view, the perspective of what was intended -- and
that writer had the experience to place the instructions in the correct
context. I also should have pointed out more clearly that sometimes, there
are emotional -- human -- factors that alter the need to write in a cut and
dried structure -- especially for non-routine conditions.
I once came across a set of operating and safety questions written for a power
plant in the 1930s. My first surprise was to see they were not very different
from what is written today, even though the technology has changed time and
again. My second surprise, was to realize that there isn't a better way to do
it, without losing contact with the emotions that humans have to control if
the process is to be carried out correctly.
Most people never get to write material like that old Jap did -- and it takes
years of training and experience to do so -- but they are part of technical
instructions because people have to be prepared for the things that can't be
set down in steps. -- It's technical writing in the the human dimension that
controls how we respond to the unexpected when it matters most.
>As an example of writing from the user perspective, I thought it was
>extremely effective, hence its impact. It handled the delicate matter of
>sending the user to his death in easy stages. The young pilot would have no
>surprises along the way. The last time I read anything like this, it was in a
>self help book on dying. <shudder>
>It must lose a lot in translation, and by being taken out of cultural and
><letoured -at- together -dot- net> wrote in message news:166822 -at- techwr-l -dot- -dot- -dot-
>> Its an issue of perspective. Anyone who has been in the military, and
>> experienced the moment when death is near or possible or expected, would
>> understand the language. Anyone who has written manuals where know-how
>> the basis of the job, would understand the language.
>> Its actually quite well written. It would more interesting to know how
>> the impact is lost in the translation.
letoured -at- together -dot- net
Check out the new release of RoboDemo, our easy-to-use tutorial software.
Plus, buy RoboHelp Office in August and save $100 with our mail-in rebate.
Get details and download free trial versions at http://www.ehelp.com/techwr-l
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.