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.
RE: Is this a typical technical writing environment?
Subject:RE: Is this a typical technical writing environment? From:"Lippincott, Rick" <Rick -dot- Lippincott -at- flir -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 20 Feb 2004 13:23:29 -0500
Lucy Connor asked:
Will I always be the last to know about new developments? Or is this
something that varies from job to job? Do any of you deal with this?
How?
Frequently, yes. It does vary from job to job, but what you've described
is not an isolated incident.
Much of the advice already given is true: you need to attend meetings,
follow up with developers, integrate yourself into their process so that
you know as much as possible about what they're doing.
Sometimes, though, this isn't enough. And some of the suggestions may
not be possible. For example, sitting with the group is a good idea, but
there may not be space there.
What you have to keep in mind is that when dealing with engineers,
you're frequently dealing with a mind that works entirely differently
than a tech writer's mind. The priorities as seen by the engineer are
sometimes so different that it's as though we're speaking different
languages. Case in point, you mentioned added menu screens. I had a
similar situation once, and when I mentioned to the engineer "This is
the type of information I'm looking for when I ask you if anything has
changed in the software." The response was an incredulous "You wanted to
know about THIS?"
Or, to put it another way, how many tech writers would do the following:
I mean, this opens a -whole- can of worms regarding nomenclature.
Although the last lines of the story say that the son of "2.0" would be
"3.0," I think you can make a fair case that "3.0" could be used just as
well on a sibling.