Re: Slow Tech Writers (offshoot of "Looking for advice -- up to the j ob?")

Subject: Re: Slow Tech Writers (offshoot of "Looking for advice -- up to the j ob?")
From: letoured -at- together -dot- net
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Sat, 06 Jul 2002 08:41:31 -0400


In <3936FA5B910BD411BC0600902771C7F201F2C6BC -at- prism -dot- cisco -dot- com>, on 07/05/02
at 12:44 PM, Jason Willebeek-Lemair <jlemair -at- cisco -dot- com> said:


>I work with "slow" tech writers. By slow, I mean that they work at the same
>pace, no matter what. Last-minute changes are incorporated with the same
>celerity as features known months in advance. Technical knowledge drips into
>their head at a steady pace. And there is nothing you can do to speed them
>up. Any attempts to do so only stresses them out. We call these types of
>tech writers "grinders".

>We also have "sprinters", those people who blast out new stuff at the speed
>of light. They soak up new features and technologies like a sponge, and go
>through about a keyboard a day producing new documentation for those
>features.

Call it what you want, but some of us think in different terms; like
first-tier projects that need first-tier writers, second-tier projects, etc.
Usually the first group comes from experience in writing that has to be
correct. Why there are even industries that expect it to be done right because
people can be killed, and/or thousands of dollars lost if the writer makes an
error and no one catches it before they turn the juice on during a test -- you
know, the little things that count world or writing.

And some of us are even old enough to know that if you don't do it right the
first time, it takes a lot longer to fix it. So when you find someone who is
slow -- to you -- you might just find that he has learned to be careful and
correct, by working on things that more important then you have seen yet.


-----------------------------------------------------------
letoured -at- together -dot- net
-----------------------------------------------------------


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
Save $600: Create great-looking Help files and software demos with
RoboHelp Deluxe. Get RoboHelp and RoboDemo - our new demo software - for one
low price. OR Save $100 on RoboHelp Office in June with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l
---
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.



References:
Slow Tech Writers (offshoot of "Looking for advice -- up to the j ob?"): From: Jason Willebeek-LeMair

Previous by Author: Re: Anyone had experience writing laboratory analytical procedures?
Next by Author: Re: Slow Tech Writers
Previous by Thread: Re: Slow Tech Writers (offshoot of "Looking for advice -- up to the job?")
Next by Thread: Re: Slow Tech Writers (offshoot of "Looking for advice -- up to the j ob?")


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads