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.
> My first rule of thumb as a contractor, though, was absolutely do not
> take fixed-bid-only jobs. There are usually way too many variables to
> predict accurately, and the very fact that the client wanted one usually
> either meant they didn't have a clue what it was going to take to do the
> job, or they were fairly ignorant of the software development process, or
> they wanted to pull a fast one.
But sometimes, surely, it meant they knew what they wanted and what they
were willing to pay for it, didn't it? Most of the work we contract out
(including *all* of our contract writing) is done at a fixed price -- in
fact, we generally don't ask for bids, we say "this is what we pay for
this job; do you want to do it?" Because we send out the same type of
work over and over, we have a pretty good handle on what we expect. I'd
hate for novice contractors to think *all* fixed price jobs involve
clients who are ignorant or dishonest or both. ;-)
Tracy
who freely admits she is often ignorant and occasionally even dishonest,
but tries not to make a habit of it
--
===========================================================
Tracy Boyington mailto:tracy_boyington -at- okvotech -dot- org
Oklahoma Dept. of Vocational & Technical Education
Curriculum & Instructional Materials Center
Stillwater, Oklahoma http://www.okvotech.org/cimc/
===========================================================
