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.
Technical writing, in my opinion, has no set job description. Here's what I
do on a daily basis:
* evaluate software
* write instructions
* write functionality descriptions
* text software
* find bugs
* handle client-specific issues
* create graphics
* publish to print
* publish to PDF
* publish to HTML
* create online Help
* provide internal training
* troubleshoot documentation tools
* audience analysis
* research emerging technologies
* Web design
* template control
I'm sure I'm missing some things... Anyhow, the point is that it is
incredibly difficult to find a title that fits all these tasks. Am I a
writer? Yes. Do I do other stuff? You betcha. Is it expected of me? Uh huh.
The title "Technical Writer" has been around for quite some time. The word
"technical" compliments "writer" in such a way that it transcends the
traditional writer stereotype and includes such things as software, product
specialization, industry knowledge and technological aptitude.
I'll wear any title my employer gives me, however I feel that no title
better fits my work than "technical writer".
Bill Swallow
Technical Writer
Aptis Inc.
a subsidiary of Billing Concepts
phone: 518.433.7698
fax: 518.433.7680
<mailto:william -dot- swallow -at- aptissoftware -dot- com>
<http://www.aptissoftware.com>
