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.
John Bell wrote:
>> So, hypothetically speaking, would you as a tech writer enjoy a job
where you were doing technical writing, client training, and client
technical support? If the company grows larger and the opportunity to
split into separate disciplines arises, should we split and which
discipline(s) would you want to work in? <<
About 8 years ago, I was in a position with a very small company in
which I, too, did documentation, training, and support. Oh, and I also did
software QA. It worked well. I would learn the software well through
my QA efforts, which came in handy when it was time to write about it,
train it, and support it. But during the busy spurts, it got to be difficult to
juggle all my various responsibilities and still do them all well. So I
decided to specialize, and I chose documentation, as it seemed the least