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: Certification: Ernest and Scribbler From:Keith Hood <klhra -at- yahoo -dot- com> To:TECHWR-L Digest <TECHWR-L -at- LISTS -dot- TECHWR-L -dot- COM>, Steven Jong <SteveFJong -at- comcast -dot- net> Date:Sat, 17 Jul 2010 17:28:33 -0700 (PDT)
I see good and bad points in both. If these are the types of things they intend to use in their examples, they're going to badly confuse a lot of people. I think that will be a problem particularly in the case of "follows the style guide even if it's not very good." That's not a laudable characteristic, that's antlike slavishness. What good is a worker who is afraid to take initiative when it might do some good?
--- On Sat, 7/17/10, Steven Jong <SteveFJong -at- comcast -dot- net> wrote:
From: Steven Jong <SteveFJong -at- comcast -dot- net>
Subject: Certification: Ernest and Scribbler
To: "TECHWR-L Digest" <TECHWR-L -at- LISTS -dot- TECHWR-L -dot- COM>
Date: Saturday, July 17, 2010, 1:15 PM
[What follows is at heart a request for comments on one aspect of certification of technical communicators. I hope it entertains you and that you respond, but at the same time I really want feedback, and really will incorporate it into what we're doing. So it's fun with a purpose -- Steve]
As STC works on implementing certification, it's helpful to keep in mind the profile of a practitioner who should get certified and one who shouldn't. Doc managers can tell you who sits atop their ladder and who languishes at the bottom. There are characteristics of hIgh and low performers. We want to certify on attributes associated with high performers. But what are they?
Remember Goofus and Gallant, the characters from _Highlights for Children_ ? 60 years ago they set examples of good and bad behavior. I'm trying to imagine a pair of writers, Ernest and Scribbler, and see if they can show us the way. Here are some examples that come to mind. Do you have any others?
-- Steve
Ernest:
Takes extra time to use variables for product and company names; keeps source files clean; uses styles or templates
Copyedits (at least) all input
Works to a plan
Follows the style guide even if it's not very good
Reports status
Selects, captures, and crops screens wherever appropriate
Explains what every menu selection does
Takes time off for professional development
Scribbler:
Gets the work done fast and minimally; doesn't waste time fondling fonts
Copies and pastes input--why monkey with what the SME said?
Gets work done and turned around ASAP
Improves on the style guide
Is too busy writing to tell people about it
Throws in screenshots wherever possible
Shows where every menu selection goes
Is good at the job and doesn't need to change
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Gain access to everything you need to create and publish information
through multiple channels. Your choice of authoring (and import)
formats with virtually any output. Try Doc-To-Help free for 30-days. http://www.doctohelp.com/
---
You are currently subscribed to TECHWR-L as klhra -at- yahoo -dot- com -dot-
Gain access to everything you need to create and publish information
through multiple channels. Your choice of authoring (and import)
formats with virtually any output. Try Doc-To-Help free for 30-days. http://www.doctohelp.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
