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 say take the job if the project is going to make you happy. Personally
I'm less concerned about which tool they want me to use than I am whether I
have a cool, exciting project to work on and working for a supportive
non-micromanager. I can deal with Word, because I've worked with it for so
long. I couldn't deal with documenting a Windows 3.1 application over a DB2
database even if they gave me Framemaker, Documentum and a platoon of
flunkies to type it for me.
If I refused to work somewhere that only used word and robohelp, I wouldn't
have had half the fun I've had in the last few years. I'd love to learn
Framemaker, but it isn't going to make or break the project I'm working on
now. So I compromise between the two positions posters are espousing. The
right tools make a huge difference, but it wouldn't matter if I hated the
product. Besides, cussing at Word lets me vent when I need it :)
Connie Giordano
-----Original Message-----
From: John Wilcox
[snip]
Some respondents are saying take a job no matter what tool you have to
use; learn to be content and try to have some future input. I say
take a job where you're going to be happy. You could literally take
years off your life cussing at Word
