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.
Subject:RE: Most dreaded part of the job? From:"Rebecca Downey" <rdowney -at- matrox -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 24 Jan 2002 09:58:51 -0500
These are in order of dread.
* staying in the job when both friends and family are laid off around you.
Gives you a rather "survivor's guilt" type feeling.
* hearing your friends have no jobs and your company is officially in a
hiring freeze.
* having nothing to do while the rest of the group is up to their ears in
work, doing 60+ hours and telling you everything is fine and they'll have a
solid spec of a product idea upon which you can work in a month or two...or
three...
* being told the software build is waiting on the Online Help. Is it
checked-in yet? Oh. <pause> Well, <pause> we're waiting on you.
* being given a copy of something for the first time that's already released
and that has a dozen or so errors in the first paragraph. Then hearing the
boss say "I'm sure our big client will love it!" when he sees you reading
the copy.
* having a SME blow up because A) you forgot he/she said something months
ago and you asked the same question again, B) you still don't get it, C) you
said "cannot be changed" instead of "Read-Only", D) some other inane
difference that only he/she can see and he won't explain it to you.
* managing your own time and resources and "guestimating" your availability
for documents you might get to write. Maybe. If your ever-expanding document
plan doesn't get the hatchet.
* checking in your latest version of a document. Getting it all nice and
neat ready to ship and then, moments after you're done and moved on to the
next priority - receiving a dozen or so bugs of the previous document which
is higher priority and so must be fixed again. I believe someone previously
called this the "death by multiple edits". Reminiscent of death by
paper-cuts.
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Rebecca Downey
Senior Technical Writer
Internet Technologies Group
Matrox Electronic System
New Business Media Division
Email: rdowney -at- matrox -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Attention ForeHelp and Doc-to-Help Users! Upgrade your existing product to
RoboHelp for only $299, through January 31st. RoboHelp can import your
existing Help projects! Learn how else RoboHelp can benefit you. www.ehelp.com/techwr
---
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.