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: Re: Where does Documentation belong? From:"Gene Kim-Eng" <techwr -at- genek -dot- com> To:turnleftatnowhere -at- yahoo -dot- com, techwr-l -at- lists -dot- raycomm -dot- com Date:09 Feb 2004 23:36:59 GMT
The specific question asked was where Documentation
(capital "D," as in the group) should be where it
would receive the greatest support with regard to
budget, championing within the company, etc. This
is not necessarily the same place where documentation
(small "d," the function) works best. Certainly, a
technical writer will be more effective and the documents
more "technical" if the writer is functioning as part of
the product development team, but if R&D couldn't care
less about docs, being a part of a different group
may well be the path to getting that writer accepted
onto the team. And if not, I suspect that most tech
writers would agree that writing technical documents
with a marketing/sales spin to them still beats surfing
the job boards while collecting unemployment because
the org you previously reported to considered its writers
expendable.
Gene Kim-Eng
------- Original Message -------
On
Mon, 9 Feb 2004 13:07:59 -0800 (PST) k k?wrote:
Technical documentation should remain on the technical
side of the company. That's the only way it can remain
technical documentation.
