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.
"Goldstein, Dan" <> wrote ...
>
> Don't take the bait... don't take the bait... <lunge>
>
> Let's say you start a job *without* professional background in the technical
> material to be documented, learn it on the job, and write entirely new
> material -- spec sheets, validation protocols, end-user docs, etc. Are you
> an "author" or a "tool monkey"?
This is that gray zone. Sure, you can become an author this way. This is how
many people, get into technical fields.
Its really a matter of what you value and where you place your focus. If you
spend the majority of your time tweaking templates, making up style guides,
cleaning up other people's work, and doing straight editing, then you're an
editor (or tool monkey). If you're spending your time learning, digesting, and
writing (about the subject matter), then you're a writer.
The difference is that many writers have no scientific or technical background.
As such, when they approach a project, they lack basic knowledge that empowers
them to make rational judgments regarding information. This puts them at a
disadvantage and makes them wholly dependent on SMEs to educate them. Many SMEs
don't want to educate tech writers or do so in a haphazard or misleading way.
This results in haphazard or misleading documentation.
As such, if you do get a job in an area where you don't have a background
education, you need to acquire one, quickly. That means doing some independent
research. It means focusing on the topic and the science.
Tech writers should really only use SMEs to validate their own knowledge or
fill-in gaps. As I have always said, never ask an SME a question you don't
already know the answer.
The problem is that most people calling themselves technical writers, give
content lip service. They say its important. They acknowledge its value. But
they don't really invest the time or energy to make their content better. This
is largely because these technical topics stray outside their comfort zone. And
rather than embrace the unknown and learn something new, they make up excuses
and justifications for why they don't need to know the unknown. This leads to
absurd rationalizations for why writers can be totally ignorant and somehow be
of value to a team.
The answer is quite simple. Define your tech writer jobs clearly. You want
authors or editors? You want somebody who can write content or clean up
somebody else's content. Test thoroughly, select carefully, and hire
accordingly.
Andrew Plato
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
NEED TO PUBLISH YOUR FRAMEMAKER CONTENT ONLINE?
?Mustang? (code name) is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to Web, intranets, and online Help.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! See a live demo that
will take your breath away: http://www.ehelp.com/techwr-l3
---
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.
