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.
Just wanted to say, thanks to everyone for the burnout thread...I'm starting
a new job now, moving from being the Documentation Queen at a bad software
company to being a midlevel documentor/tech writer at a good software
company, so it's good to know that new job queasiness isn't just me.
The main issue here is the other documentor where I work now; she was the
lone tech writer before I started. She is 180 degrees separate from me as
far as her philosophy of tech writing goes. She never made a deliberate
decision to get into tech writing, doesn't identify as a writer (and said so
to me!), and, upon being asked, wasn't interested in either joining the
local tech writers' organization, nor in signing up for this mailing list.
"I'm not interested in any of that," says she. As an example of how she
approaches learning new document-related software, she tried installing
Adobe Acrobat and ran into problems. Instead of calling tech support, or
trying to troubleshoot, she gave up. Although she only has one year of
experience in tech writing, she's an expert in the product and the manuals
she has done are competent--but not created with any knowledge of online
help conversion/navigation issues. She is very sharp, and I think she's as
antsy as I am about our different perspectives/experience/surrendering lone
This software company has no online help. Bupkes. My goal here is to bring
this company into the 21st century as far as documentation goes (they tried
having developers create online help, and then they hired me), and making
some fairly radical changes, while at the same time trying to build a
working relationship with this documentor.
Ahem. Thanks for letting me vent. I'm treading very softly right now,
listening more than talking, indexing manuals (800 pages of user
documentation sans indexing), learning their programs, waiting until she and
I have built up some rapport with each other before getting radical with