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.
I think I did a contract there (my one all-software
job).
It's sort of like being tech writer on the Black Pearl
(multiple captains, processes and schedules more
what you'd call "guidelines" than actual rules, your
number one priority is not to be the guy who gets
chained to the cannon and thrown overboard). You
prioritize the topics, start with the most important and
work your way down, review constantly and post
regular beta releases. Anytime there's a delay in
the product release date, copy the last release,
start working on improvements you think you can
use the extra time to squeeze in but always have
the last one ready to go into product at a moment's
notice if needed. The "deer in headlights" look you
get from everyone when you respond to any change
in schedule by saying docs are ready to go gets to
be fun after a while.
Gene Kim-Eng
----- Original Message -----
From: "Victoria Wroblewski" <victoria -dot- wroblewski -at- eagletest -dot- com>
> I was recently talking with a non-TW who deals with some TW during the
> course of business. When the subject of deadlines came up and I was
> asked what I do when I miss a deadline, all I could say was "I don't."
> Cue the "deer in headlights" look from the other person. I tried to
> explain that really, I've never missed a deadline that was not due to
> a
> technical difficulty outside of my control. The blank stare
> continued.
> I tried to go further, explaining that if a un-movable deadline is
> approaching and it's looking tight, you go to the "good enough" place.
> Figure out what is important and not important, what can and cannot be
> done in the timeframe, and make sure everyone involved in the project
> knows what the situation is. The person really could not put it in
> perspective.
>
> I'd hate to be a tech writer at that shop.
ComponentOne Doc-To-Help gives you everything you need to author and
publish quality Help, Web, and print content. Perfect for technical
authors, developers, and policy writers. Download a FREE trial. http://www.componentone.com/DocToHelp/
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
