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.
[An STC article stated that the] ...general areas of competence" [for a
Technical Writer] are:
Plan the project
Co-ordinate the project
Research the project
Organize the information
Write the project copy
Plan the illustrations
Conduct project review
Produce the document
Perform administrative functions
Continue professional growth
Train and supervise employees
What would people add or subtract to this list?
Tony Markatos responds:
The above is a typical description - many books that describe "what a
Technical Writer does" state, basically, the same. It fails to state the
MAIN things that need to be done to create clear and concise documentation -
especially for complex software products. It states a lot of the "other"
things that are often needed - but not the main things required. I identify
the main things in a separate posting (today).
Tony Markatos
(tonymar -at- hotmail -dot- com)
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
