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.
In the letter on page 195 of STC's May '93 Technical Communication journal,
Rita Wetterhan described her encounters with technical writers who perceived
what they do as "just a job" or as a springboard to a "real"profession.
At the end of the letter, she wondered:
"...is it time for the Society for Technical Communication to
establish a licensing or registration program that makes it easier
to weed out those who just want 'a job?'"
I, for one, am all for it! I've met too many people on the market who call
themselves tech. writers/editors/communicators because they like to write or
are interested in technology. Despite their good intentions, these people
not only diminish the quality of communications as a whole (e.g., poorly
written software manuals, jargon-filled reports, etc.) but are also
reinforcing the notion that tech. communication isn't a *real* profession,
that it's just a line of work you can go into if you've got the urge.
Any thoughts out there on the usefulness of certification? What kinds of
tests could be devised to measure our skills?