NetNews Usenet Archive 1992 #23/NN_1992_23.iso/spool/misc/writing/3112

Text File | 1992-10-08 | 7.9 KB | 161 lines

Newsgroups: misc.writing
Path: sparky!uunet!psinntp!dg-rtp!harpo!goolsby
From: [e-mail] (Chris Goolsby)
Subject: Re: Technical Writing...need advice
Message-ID: <[e-mail]>
Sender: [e-mail] (Usenet Administration)
Date: Wed, 7 Oct 92 14:44:41 GMT
References: <[e-mail]>
Organization: Data General Corporation, RTP, NC.
Lines: 149

In article <[e-mail]> [e-mail] (Peggy Brown) writes:
>I've been reading the responses about Technical Writing and hope
>more technical writers will respond and give me advice on how to
>get started.  I may wish to be self-employed for awhile, but
>would like to hear about contract agreements, and how to land a
>full-time job too.
>

Okay, my wife and I are both technical writers and have been for the
past few years.  I have a full time job and she works on contract.
From our joint perspective, it is definitely easier to get contract
positions than full time positions--at least in the computer industry.
(As an aside, there are lots of different types of technical writing.
We do computer hardware and software documentation, but there are also
medical technical writers and such in our area.)  Companies are laying
people off in record numbers in the computer industry, and the trend
seems to be using temporary contract people to do the work formerly
done by full time staff.

>I'm a computer programmer now, with an MS in Information Systems
>Management, extensive computer experience with a wide range of
>languages, software, and operating system.  For the past 3 years
>I've been an Oracle Database developer/dba and systems manager
>of a VAX 4000.  I learn computer "stuff" very fast.  Most of my
>programming has been done for applications in the health field.
>

Well, you definitely have a good technical background.  That's
important.  It's also important that you can learn very fast.
Technical writers often have to learn about the product they are
documenting very quickly--the less lead time spent learning, the more
available for writing.  It's also good to have an advanced degree.  I
have a M.S. in Information Science, which has given me some advantage
in getting a permanent position.

>I also have a BA in English Literature and wrote extensively
>in my previous job - reports, grant proposals, user manuals,
>administrative memos, etc...  Now I just update user manuals now
>and then, but my writing skills are still intact.  Oh!  I also
>did graduate work in instructional design and wrote a few manuals
>as an internship with my alma mater's Center for Instructional
>Design.

Having an English degree is good, as is having some experience writing
manuals.  However, technical writing is somewhat of a specialized art
and is very different from the sort of academic writing done in
universities.  You might consider looking around your area for some
sort of training on technical writing.  A lot of universities offer
technical writing as a continuing education class, some offer BA and
advanced degrees in it.  My wife and I met in a community college
program set up by several companies in our area specifically to train
technical writers for their consideration.

You might also read a few books on the subject.  I don't have my
library to hand here, but I'm sure some of the other technical writers
in the group can supply a few citations.  One I do have here that is
a good resource is _Writing Better Computer User Documentation: From
Paper to Online_ by R. John Brockman (ISBN 0-471-88472-3).

If you aspire to something besides an entry level position in
technical writing, then you probably need to show companies some sort
of education, training, or more experience in the field.

A further consideration is what sort of word/text processing packages
you know.  A contract writer needs to know several:  from PC standards
like WordPerfect and MS-Word, to more advanced stuff like Framemaker
and Interleaf, to mark-up languages like nroff/troff and IBM's
Bookmaster.  A good knowledge of various operating systems is also
important.  At one job I, I was simultaneously using for various
projects an MS-DOS based PC, a Macintosh II, and a terminal hooked up
to a UNIX machine.  A successful contractor needs to be able to use
whatever equipment and software the client has on hand.

>So there's my background.  I think I have both the writing skills
>and technical expertise in computers to make a go of it.  But how
>does one get started?  How well, in your experience, does
>self-employment work for technical writers.
>

I think I covered most of this above.  As far as self-employment, I'm
not really sure what you mean.  Do you mean you would like to try and
find the contracts, set rates, and such yourself?  That would be a LOT
of work, especially if you don't already have some job leads or
contacts.  Also, you need a lot of equipment and software to do the
work your self, such as a powerful computer, a good desktop publishing
package, and a printer capable of producing camera ready quality
drafts.

A better way to go, IMO, is to find work through contract houses.
That's how my wife finds here contracts.  There are numerous companies
in our area that bid for technical writin contratcs, then hire
contract writers to fulfill the terms of those contracts.  These
include some of the larger temporary agencies, such as Manpower and
Monarch (both of which have a technical services division), and a
whole bunch of regional and smaller firms.  My wife has gotten
contracts through a good number of these firms.  Virtually all of
them have her resume and will submit it as part of their bid to
obtain a contract (with varied success).  Some of these places would
rather use their own staff to fulfill these contracts, and more than
one has offered my wife a permanent position.  However, the money is
better as an independent contractor, and my job takes care of our
benefits.  On the other hand, my wife is rarely paid for sick leave,
vacation, or even holidays.

>There is a reorganization going on now where I work.  So far I've
>been spared, but there is a possibility I'll be laid off.  Since
>I'm pregnant and expecting in late April, I think I'll have a
>tough time getting a new job until after the baby comes.
>(Employers really don't hire pregnant women, do they?)  So I'm
>weighing all my options and if I do get laid off, this might be a
>good time to explore technical writing.  Also, with the cost of
>daycare, being self-employed (if I can get any work done) might
>work out well.
>

Sorry to hear about the "reorganization."  I can definitely
sympathize, as my employer laid off some of my fellow writers very
recently.  Congratulations on your pregnancy.  My wife is also
expecting and also has a due date in April--small world. . . .
Employers are definitely reluctant to hire pregnant women.  My wife
has manged to find a short term contract for the next few months.  You
might consider trying to find something like that.  It would give you
some valuable experience and a nice item for the resume, a good
postion to seek a longer contract after the baby is born.

Unless you have a lot of equipment and appropriate software, you
probably won't be able to find a contract that will let you work at
home.  Oh, they do exist, but they are pretty rare.  The best my wife
has been able to get was a contract that let her work at home when she
was editing or proofing a manual and didn't require any computer time.

>Any suggestions?
>

One last thing.  There should be a Society for Technical Communication
(STC) chapter somewhere in your area.  This is the technical writer's
professional organization and is a very valuable source of contacts
and information.  I don't have any STC information with me, but I'm
sure there is a number or something you can call to ask about local
chapters.  Mayber someone else can supply it.

>- Peggy -

Good luck.  Hope I wasn't too long-winded and that you found this
helpful.  Let me know if you'd like some clarification, etc.

Chris

[e-mail]