Re: Certification -- what's in it for writers

[Scott Turner <quills -at- airmail -dot- net>]

The real question is what do you certify? That you can spell?

In my career i've documented hardware installation, maintenance, hardware and software user manuals, software installation, business processes, regulatory guidelines. 

I've written API documentation, programming guides, release letters. I've written under myriad different style and quality standards, so where is the commonality that isn't present for any competent writer?

A good tech writer is a competent writer, and has the ability to learn quickly and synthesize that information into a documentation for a specific audience.

You don't have to be an expert in the field you are documenting. 

And since the STC hasn't the money or personnel how do you create a certification process that has meaning and validity?


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, 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- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com