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.
Subject:Re: Need Professional Advice From:John Posada <john -at- TDANDW -dot- COM> Date:Tue, 25 Aug 1998 20:35:00 -0400
I would suggest that instead of looking for a reason to leave, that you find a
reason to stick around, at least for the minimum amount of acceptable time.
IF you are a contractor, this will not be the last time you find yourself in
this situation. Therefore, why not use it to learn something:
- mainframe stuff (yes, they are out there and will continue to be out there)
- how to deal with an environment that isn't exactly to your liking
- how to learn
- how to adapt
The last three are probably the three most important skills you can learn.
Learning financial and manufacturing systems is easy. As a tech writer, you
don't have to be a programmer to write stuff for programmers, right? (take it
from one who knows). It's knowing HOW to learn that is the hard part.
Besides...think of how sure of yourself you'll be in the future when you
interview and are able to say, with conviction, that you know you take on
anything they throw at you. As a professional, you cannot run away from things
you don't know...there is more of it then things you DO know.
John Posada
> In any case, I hate this job. I have no desire to continue working on
> mainframe systems, and I am completely out of my depth regarding the
> financial/manufacturing knowledge.
