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: Knowing prog. lang. +s to a TW's $? From:KAREN_OTTO -at- HP-SPOKANE-OM2 -dot- OM -dot- HP -dot- COM Date:Fri, 10 Jan 1997 11:08:52 -0700
Item Subject: cc:Mail Text
It definitely helps in my job. However my job differs from the
"average" TW job in that it is specifically an ENGINEERing position.
Programming is definitely part of the job. I regularly have to test
the syntax that I provide in my manuals, and this is best done with a
program. I also have to write tutorial information about programming,
with example being a big part of this.
On the subject of job titles:
I own the noteworthy title of Learning Products Engineer. To be that,
I must have an engineering degree (or a very significant amount of
related experience).
My department (Learning Products Department at Hewlett-Packard) has
these titles:
LPE (Learning Products Engineer):
a degreed Engineer, preferably EE. Job is to understand and create
content. Team management of individual documentation projects is
expected (about 3 people per team).
LPD (Learning Products Developer):
a non-degreed content creator, usually with some college. Expectations
of team management and performance is less than that for an LPE.
Graphics designer:
technical illustrator, frequently with no formal illustration
education. Does some content creation, but usually follows the team
leader's requests. Is now developing into web document creator (web
docs are based on the technical content from the paper).
Project specialist:
More than an administrative assistant, but performs many
assistant-type activities. Responsible for publishing the docs (paper
or web), and does final formatting and light editing (typos and such).
Technical editor:
edits all documents. Comments for style and technical content.
Primarily focuses on writing style and consistency. Also leads team
process development and monitors projects (some 40 projects are our
list). Was formerly a project specialist.
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
