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.
> > If you plan to write for the IT industry, I recommend
> > learning as much as you can about technical subjects
> > such as programming, networking, and databases.
> I don't want to rekindle the "how techie? is ignorance an asset?"
> debate here, but I want to point out that these topics (and
> certifications like the MCSE) are NOT necessarily useful if
> you're writing end-user software documentation.
I don't want to speak for Dawson here (but I will), by saying that
"learning as much as you can" doesn't necessarily mean getting a
degree or certification in the subject. I means learning as much as
you can so you have the knowledge to get the job done.
I have been writing s/w documentation for several years. Now why
in the world would I need to know about networking, TCP/IP
protocols, etc? Because I write help files & manuals about
software.... And because this software supports our datalogger
hardware... And because this datalogger hardware has a
communications device which allows you to contact it over a
TCP/IP network... And because if I can't at least have some sort of
working knowledge about how all these pieces fit together, my
documentation isn't going to be worth a wooden nickle.
As others have mentioned, be flexible. Be willing to learn what you
have to, to write good, technically accurate, USEFUL
documentation. Anyone can regurgitate. Good writers can sit down
with a product, learn how to use it, and write about it so others can
use it to. If not, YOU won't be worth a wooden nickle to your
employer.
From: TDean -at- envirosys -dot- com
> Now my face turned red and I was blistering mad that anyone would
> question my judgement over an administrative assistant's
Years ago, I was an administrative assistant. I am, partly, where I
am today because I DID have better judgment than the person who
thought because she had a degree she had all the answers. I did
have better ideas about how to justify text or choose a font for an
ad piece, and my employer recognized that.
From: "John David Hickey" <jdhickey -at- sympatico -dot- ca>
> have a thick skin (to be able to rise above the pettiness of some
> people),
And thanks, John, for your thoughts. As you alluded, another skill
is knowing when to stop...
Dana W.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Announcing new options for IPCC 01, October 24-27 in Santa Fe,
New Mexico: attend the entire event or select a single day.
For details and online registration, visit http://ieeepcs.org/2001
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
---
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.
