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:eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 23 May 2003 14:23:04 -0400
>>You may not need to know how to repair your computer, but diagnosing is and
>>should be part of our job and part of your skill set. How else will you know
>>when the product is having a problem or it is you?
Well, if you're documenting something that polls all your computer hardware, you
had better know something about the concepts of the various protocols and the
hardware involved.
Thing is, I'm a power user when it comes to computers, many of my colleagues are
not. Does that make me a better techwriter? Not particularly. Our product is big
mass transit rail vehicles, subways, and light rail (All of which we rarely get
to see first hand).
There really are few generalisations that you can legitimately make about the
Techwriting profession.
---
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.