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.
Dan, you raised some interesting questions. The most compelling was the
last one:
<
So, I'm curious about the comparisons between the two:
* Do the constraints and difficulties experienced by both cancel each
other out, so that we're back to a level playing field?
* Do the advantages tend to cancel each other out, so that we're back to
a level playing field?
* If we're back to a level playing field, then how is it that folks tend
to turn to outside doc to help them with a program, rather than the
inhouse doc? What does the outside doc do that we inhouse writers should
be doing?>
I have worked both sides of the fence. For about four years I contracted to
develop a help system for a company that produced internal software that
ultimately found it's way to a limited commercial market. I telecommuted
from my home. I found it an exhilerating experience. My only frustration
being that they had no one really "in charge" of the project who had any
depth of understanding about what I was doing. So there was very little
appreciation for my efforts, they were just taken for granted. However,
they paid me well, so that was appreciation enough.
As for your last question...I think it's a point of objectivity. Outside
writers are not harboring any false illusions with regard to their
knowledge. They have to take the time to get to know the user base, the
product, the SMEs and everything else that pertains to the project. Now
that I'm wearing my other hat which is developing documentation from the
inside, I've noticed that I make far more assumptions in each of those
areas. Most of my assumptions are made out of necessity because I'm so very
limited timewise.
As a contractor I had a little more authority to insist that they provide
certain things that I do not have the authority to insist upon as an
internal writer.
