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 mostly lurk on this list, but I'm coming out to applaud your categorization of
tech writers -- technical communcators, I call us.
I've been in the biz for 14 yrs nows. I LOVE it, even the crummy parts of the
job.
After sinking my teeth into TC, I quickly found that if I wanted to succeed in
the field and be respected as a TC, I needed to go back to school. I live in
Cincinnati, which has several colleges and universities close by. I found the
best program in my area, succeeded in getting accepted, and am now on my way to
finishing a Master's Degree in Technical Communication. It's taken me 7 years,
but has been well worth the effort/cost [I've paid out of pocket, no employer
tuition aid].
Why did I do this? Because:
1. I grew tired of the TC competition beating me on projects because they had
degrees/certificates specific to the field.
2. A degree in TC helps to overcome employer/HR perceptions that "anyone" can
document.
3. I wanted respect from the technical people and end-users. By taking the time
to study the TC discipline, theories, and publishing methods/tools has given me
an ever-growing knowledge base that is invaluable and helps tremendously in
working w/end users and technical people.
4. Most importantly, I realized that I didn't know what I didn't know -- such
ignorance was hampering my ability to succeed professionally [i.e., staying
employed]. Solution: go back to school.
What frustrates me about other TW/TC I have worked with:
1. Many come from various backgrounds/disciplines and profess to "have a knack"
for TC. Please -- if you have a knack, back it up with REAL training. Get a
degree in the field or at least a certificate. Someone professing to be a TW/TC
that has no real training in the discipline will quickly be identified
dis-respected by those who DO have training in the field.
2. I can't think of a #2 right now.
Thanks for the soapbox.
Janet Murphy
Cincinnati OH
David Lettvin wrote:
> <snip to wonderful soapbox>
>
> Technical Writers
> --------------------
> This person loves to communicate. They may like technology, or write poetry
> in their free time, but at the core they love their craft. There is nothing
> they would rather do than make the light go on in the user's brain. Real
> technical writers are passionate about their discipline, their craft, and
> their challenges.
>
> I regret to say that they are the smallest group.
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
Check out RoboDemo for tutorials! It makes creating full-motion software
demonstrations and other onscreen support materials easy and intuitive.
Need RoboHelp? Save $100 on RoboHelp Office in May with our mail-in rebate.
Go to http://www.ehelp.com/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.