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.
On Wed, Oct 19, 2016 at 8:50 PM, William Sherman
<bsherman77 -at- embarqmail -dot- com> wrote:
> This idea of certification comes up every so often, and has some merit.
> After all, anyone can say they are a technical writer, but how does the
> hiring company really know? The certificate sounds like the answer.
>
> But for a certificate to be good, it isn't enough to attend a class, or even
> a dozen, you need to test out to prove yourself.
>
> Here is the rub.
>
> What do you test?
>
> Do you test ...
I just want to say:
"What I do have are a very particular set of skills; skills I have
acquired over a very long career. Skills that make me a nightmare for
people like you."
I love that film. ;-)
Bob
In all seriousness, I think that what Daniel said is the key:
"... extract relevant info from SMEs quickly and turn it into
something laymen find comprehensible..."
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
