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.
RE: non-tech techwr better for end users (was "same boat")
Subject:RE: non-tech techwr better for end users (was "same boat") From:Christine -dot- Anameier -at- seagate -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 29 Dec 2000 13:41:25 -0600
Kathi DeGuzman wrote: "There is no point in trying to convince
me that a person would be able to teach someone about something that the
person knows nothing about."
You'd be surprised how much of that goes on in universities. When I was a
grad student, I did a couple of years as a teaching assistant before moving
on to teach my own classes. In most cases, placement was arbitrary. I was
an 18th century British lit specialist who wound up TA'ing for lecture
courses in linguistics, American short stories, 20th century drama...
And it worked. I'm not saying it's the best way to do things, but I was
able to learn the material fast, keep a step ahead of the students, and
perform competently. Just because I'm not a professor of linguistics
doesn't mean I can't put together an adequate lecture on the international
phonetic alphabet, suitable for a low-level survey course. I sure wouldn't
have tried to lecture to a hall full of linguistics professors, but I knew
enough to teach undergrads something.
Now I learn software and turn right around and teach it to end users.
Perhaps by "knows nothing about" you mean "has no aptitude for"? There are
a lot of us who figure it out as we go along but are good at formulating
what questions newbies might have, and good at explaining things. In fact,
while I hesitate to call ignorance of the subject matter a "bonus," I would
say that it could make a competent writer somewhat more likely to intuit
the issues a new user will encounter. Some of the development types may
well have forgotten the time they didn't know [insert basic concept
everyone learns at some point] and when confronted with that, they may
express contempt for the idiot user who doesn't know that basic concept.
I've seen it happen.
Kathi, you described your greatest strength as "the ability and willingness
to seek out information." I think that's an essential skill for a tech
writer, along with a certain level of empathy for the user. IMO, those
qualities count for much more than already knowing the material. Any facts
you learn will become obsolete at some point, but the ability to learn will
not.
Christine Anameier
(insert standard "I don't speak for my company" disclaimer here)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY. http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by an
anonymous satisfied subscriber since 1994.
---
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.