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.
> > we would have learned from our education was the ability
> > to figure out what references to look in to research the
> > answers to our questions. ...
>
> Or as I put it in interviews (and this is really my only good
> line):
>
> "I may not know everything on the subject. But I do know how to
> find out!"
Is this the best from the pespective of those hiring us?
The problem with this is you only get to know what you might already
know exists but you don't know the answer. In effect, where we go to
most resembles a SME who will answer your question but not give you
any more than you ask for.
However, when you know the subject, you can take that question a take
it much farther. Isn't this a more favorable situation?
For example. I'm describing the interaction between two servers. You
configure on one server, which then distributes the configuration
information to multiple servers using something called a dxa (having
nothing to do with bone density scans). Now, unless you know about
Directory Exchange Agents, you can address this topic at a
superficial level. However, if you know the subject, you can include
indepth information as it applies to your particular instance, in a
way that you may never find in the 842 google hits for "directory
exchange agent".
What I'm saying is, don't think that because it is a snappy response,
that it is the answer the other person most wanted to hear. It may be
better than a blank look and a dribble of spit, but you only get a
limited number of times you can use it.
John Posada
Senior Technical Writer
"I think the problem, to be quite honest with you, is that you've never actually known what the question is."
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
