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: [TCP] certification (was: ranting STC) From:"Evans, Diane L (Rosetta)" <diane_evans -at- merck -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Mon, 5 Mar 2007 12:05:50 -0800
>Diane -- and I ask this question with respect -- do you tell the story
partly to identify the shortcomings of *not*
>having gotten the expected training?
OK, the moral of the story:
If you are sufficiently talented, you can get hired without a degree.
A degree, on the other hand, will give you valuable assistance towards
getting a job.
No, I am not against certification. I will have a master's degree in
Technical Communication on May 4 of this year; over a year ago, I earned
my CSQE -- which verifies that I understand the software development
life cycle from requirements through testing.
My only objection to certification is that there are so many types of
technical writing. I work in an analyst role most of the time; I
haven't written a user manual or help file for quite some time. On the
other hand, some people specialize in those types of documents.
So, that is the biggest problem I see -- there are so many types of
technical writers, how can we find a certification criteria that fits
them all?
On the other hand, a physician is first certified as a general
practitioner, then works towards other certifications such as surgery or
internal medicine.
Any certification program would need to have a multi-tiered approach as
well -- skills that all technical writers should have, and skills that a
subset of these writers should have.
Of course, then we have to decide who can set the criteria.
I knew there was a reason I keep out of this debate :)
------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station,
New Jersey, USA 08889), and/or its affiliates (which may be known
outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD
and in Japan, as Banyu - direct contact information for affiliates is
available at http://www.merck.com/contact/contacts.html) that may be
confidential, proprietary copyrighted and/or legally privileged. It is
intended solely for the use of the individual or entity named on this
message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then
delete it from your system.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
