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.
Welcome to the world of software! Yes, it is generally this bad but John was
right - getting involved really early makes a huge difference. Planning also
makes a huge difference. Get and read like it is the holy word JoAnn Hackos'
book Managing your documentation projects. And every time I re-read it I
learn more, again. It is a great book and the principles have saved my butt
a few times. She is a goddess!
If you are not an adrenaline junkie, you might think of another area of
writing. I have friends in other industries and it is not as bad in others.
To really be successful here, you have to really like technology and really
like to work. But John was also right - making over $100,000 makes the
deadlines OK. And a very understanding family really helps. And take
advantage of the quiet times, they do happen and grab them when they do. It
gives you something to remember when the crazies live at your house! And
they will!
sharon
Sharon Burton
Anthrobytes Consulting
Home of RoboNEWS, the award-winning unofficial RoboHELP Newsletter
www.anthrobytes.com
anthrobytes -at- anthrobytes -dot- com
-----Original Message-----
From: Cassandra Lidgerding <clidgerding -at- PREMIS -dot- COM>
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU <TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU>
Date: Monday, 18 May, 1998 9:57 AM
Subject: Documentation cycle
>Hello,
>I've search the archives, but couldn't find any posts that addressed what a
>documentation cycle should be or what documentation cycles are really like
>in different companies.
>
>I'm new to the corporate world (graduated 1997) and have been working at my
>first "experience" job for the last year. I find myself working under
>incredible deadlines (for example, all the online help for a product in two
>weeks) and I'm wondering if this is typical for software? Should I
>specialize in another area (not software) if I expect a decent amount of
>time to complete my documentation?
>
>What is an ideal documentation cycle and what are the documentation cycles
>like at your companies? I appreciate any advice you can give me.
>
>Thanx!
>
>Cassandra
>
>Cassandra L.S. Lidgerding
>Technical Communicator
>clidgerding -at- premis -dot- com
>
>
>
