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.
Hi again, folks. I sort of started a subthread here about creating a
TWBOK and using that as the basis for certification; then I left town
for a couple of days. Time to jump back in.
In response to the Keith/Bruce exchange snipped below, I would
specifically avoid including specific tool knowledge (I think I said
that already). You should probably know something about the role of
style guides in a tech writing organization, but that doesn't mean you
have to have memorized my favorite style guide. I think it is useful to
know the difference between a raster image and a vector diagram. But
that does not mean you have to be a proficient user of Photoshop and
Adobe Illustrator. You should know the capabilities and limitations of
wysiwyg HTML editors; but that does not mean you have to be experienced
with (pick one) FrontPage or Dreamweaver. You should be able to carry on
an intelligent discussion about the way personality type affects the
relationships between SMEs and writers; but that doesn't mean you have
to have completed a Myers-Briggs training course.
In other words, there are fundamentals you ought to be familiar with in
a variety of areas--that's the TWBOK concept. With respect to
certification, perhaps you ought to be able to demonstrate proficiency
in some number of those areas (someone said something about a quorum
standard, or something like that). Maybe you ought to show that you can
master _some_ tools (but without specifying what tools those are).
My point is that we ought to be able to arrive at a consensus on these
broad questions before thinking about the details.
Dick
Bruce Byfield wrote:
kcronin -at- daleen -dot- com wrote:
Yes, we could put students through the wringer and make them learn a wide
base of skills. But many of those skills will become outdated within
years.
I'm not sure what skills would be outdated? I can't think of any skills
I've learned in the last eight years that are outdated, except possibly
specific tools. even though I haven't used WordPerfect for years, what I
learned while using it is still transferable to other word processors.
---
[This E-mail scanned for viruses at mail.fiam.net]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Purchase RoboHelp X3 in April and receive a $100 mail-in
rebate, plus FREE RoboScreenCapture and WebHelp Merge Module.
Order here: http://www.ehelp.com/techwr-l/
Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at http://www.raycomm.com/techwhirl/special/contests/
Happy birthday to you, happy birthday to you, happy birthday TECHWR-L....
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.