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: What does it mean to be technical? From:"Victoria Nuttle" <vnuttle -at- cauto -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 23 May 2003 12:01:33 -0500
>What happens if FedEx goes on strike, what happens if the city you are
in has a
>power outage, or what happens if you come down with the flu. Does
documenting a
>spreadsheet require that you have knowledge of how overnight shipping
works, how to
>run a power station, and how to synthesize a vaccine?
>
>Aren't we getting a little carried away here?
Ok... then how about this one: A basic understanding of your PC &
operating system can help you identify a difference between a bug in
what you're documenting and problems with your own PC. It's good to
know with absolute certainty that the fire shooting out of the back of
your PC's power supply can in no way be caused by the spreadsheet. And
yes, I have seen people document "bugs" near that stupid and bring them
to developers.
--------------------------------------------
Victoria J. Nuttle
Technical Writer, Creative Automation
vnuttle -at- cauto -dot- com
---
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.