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: What to do in slack times? From:Deborah McDaniel <DeborahM -at- CAPTURA -dot- COM> Date:Fri, 9 Apr 1999 11:06:45 -0700
I use that time to read, take classes, work on tutorials for software I
"know" but haven't mastered, learn new software - the list goes on.
When all else fails, I nose around other departments (marketing, for
example) and see if there is anything I can do for them.
McD
Deborah McDaniel
deborahm -at- captura -dot- com
-----Original Message-----
From: Anonymous User [mailto:anonfwd -at- RAYCOMM -dot- COM]
Sent: Friday, April 09, 1999 9:46 AM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: FWD: What to do in slack times?
Name withheld upon request. Please reply on list.
*************************************************
Hello everyone,
I am not in the middle of a crisis, but I do need advice
about
how to handle an on the job situation.
I am working for a terrific company, I am paid well, and I
am
respected for the work I do. See, I told you there was no
crisis.
My problem is this ... When work is slow, I don't know what
to
do with myself. I like working under pressure and I feel
almost
dishonest, like I am not working hard enough, when the
pressure
is off. The other problem is boredom. After the tenth week
spent
editing and massaging the same documentation, I start
craving
something new.
Don't get me wrong -- I am not being unproductive. Bugs are
being fixed in the product and in the documentation. New
sections
are being added now that I have the time to write them.
Technical
details are being fleshed out with the help of the QA and
technical support departments. The staff are simply
maintaining
the existing (software) product and preparing for the next
push.
So, how do you deal with steady, predictable, post-release
work?
What tricks do you employ to add variety to your workday?
How
do you deal with (your own) impatience and desire for
front-line
action?
-Anon
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Message forwarded on request. Please reply on list.
