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.
> I think rates are low because people don't know they can ask for more
> and writing is crap partly because of apathy and partly because of
> lack of experience/knowledge in the industry or domain in which they
> are working as a technical writer.
> > There's a huge abundance of people claiming they are writers...there
> > just isn't an abundance of writers who can walk the walk.
> Walk the walk how? Really, if you want to talk certification, you
> really need to be specific. We can generalize all day and still not
> have a shred of evidence that technical writing certification does or
> does not have merit.
One of the great things about being a tech writer is that it's a very
individual experience. Each assignment is different. Each writer is
different. The tools are different. The requirements are different.
You get the point. ;)
What works for me here at WRAMC would probably be considered chicken
feed to most senior TW's. But then again, I'm doing things that many
people with the same job title as I have are not getting to do--like
actually take part in the creation of the documentation. Wow, what a
concept! :) Excuse me while I snap my gum and take some notes. :)
I hate certification with a passion. One reason I got out of the
programming field was that I was repulsed by the very idea of having
to pay for my own training in all these newfangled apps every time
Microsoft arbitrarily decided my skills were worthless. Worse yet, I'd
be competing with people much younger and less experienced, who would
get jobs over me because they had the piece of paper...and were
willing to work for less because they had less experience.
Don't get me wrong! I love the idea of learning and bettering my
skills. I just don't love the idea of being FORCED to do it,
especially when the net result in terms of better production and
increased skill is negotiable at best.
The best way to become a better tech comm is to WRITE. Write
constantly. Write everything you can. Review it. Write some more.
Learn from other writers. Find other assignments to write about.
Lather, rinse, repeat.
When it comes down to crunch time and the manual needs finishing, I'd
rather be the guy who gets it done than the guy with a million
certificates who doesn't know how to open a Table of Contents in Word
WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo: http://www.webworks.com/techwr-l
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.