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 see your point, but I lost count of the number of times I had
conversations with other tech writers where my side went "My job
title? I'm a contractor. No, I get paid a salary. Yes, I get sick
time. Yes, I get vacation time. Yes, I get paid for holidays. Yes, I'm
on the retirement plan. No, there's no expiration date to the
contract."
So, perhaps we all here in our wisdom are in complete understanding of the term.
But I keep running into people who are not.
--Rick Lippincott
I explain things.
On 6/30/15, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
> Don't think it's really all that different. "Contractor" is the person
> or company that holds the actual contract to supply product or service.
> In DoD land, that's usually a company such as Lockheed-Martin, as
> opposed to a temp agency as it normally is for non-DoD, but it's not
> impossible for a temp agency or a single individual to be a defense
> contractor.
>
> Confusion often arises because some people call themselves "contractors"
> when what they really are is employees of a company or agency that is a
> contractor
>
> Gene Kim-Eng
>
>
> On 6/30/2015 10:49 AM, Ed wrote:
>> Please explain your point a bit more, I am interested.
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW
