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: Job Futures for Tech Writing -Reply From:"Bonni J. Graham" <bgraham -at- ELECTRICITI -dot- COM> Date:Wed, 7 Dec 1994 12:03:07 PST
Doug very graciously clarifies his point and it turns out that we WERE
saying the same thing: Contractor vs employee decisions are highly
individual to each company.
I hope I didn't sound too sensitive, but this history issue is one I have
to battle every marketing day. A suprisingly large number of potential
clients (for whom history is NOT as sensitive as it is in the case Doug
mentions) would rather have badly written doc done by a surly engineer who
doesn't WANT to write doc than ask a contractor to learn history.
Sometimes thay've had a bad experience, often with a contractor who is
contracting so he or she CAN get in, write, and get out. I have to explain
to them over and over that what they're looking for is part of the service
I provide.
So it shocked me to see what I interpreted as "contractor bad, permie good"
HERE, of all places. Glad to see that I was wrong.
Are there any other contractors out there facing this problem? What do you
do to solve it? If you're working permanently and wondering whether or not
to hire a contractor, what arguments would win you over on this issue?
Bonni Graham
Manual Labour
Director, Region 8 Conference
bgraham -at- electriciti -dot- com
