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 have a couple of points to raise or counteract based on the curriculum
discussions:
I am a recent graduate of the Seneca College 1 year Post-Diploma Co-op
Technical Communications program in Toronto, Canada.
By far the most valuable term in the program was the 4 month co-op
placement. Not that the classes were weak - there is nothing to beat
real-life experience.
Somebody suggested reading a $30 book instead of taking a $3000 course. That
is ridiculous. There is far more to this profession than any book, or series
of books can cover.
I know a friend who took the technical writing course at University of
Toronto. No 'tools' were discussed or used in the program. He is still
looking for work. I was talking with current students enrolled in the course
that I took. most of their questions had to do with 'tools.' I told them to
change their focus. It is important to know some tools but that is a small
part. You won't get an interview if you do not mention in your resume that
you can use FrameMaker, RoboHelp, a graphics tool etc.
However, once you have that job (likely a short term contract or very junior
position) your tools skills will be a minor factor. It is the ability to
turn complex technical information into concise, logically organized and
USABLE documentation that will turn that contract into a full-time position.
It is these skills that the colleges need to emphasize in their programs:
Information gathering, organization, understanding the user, the ability to
write in the appropriate manner, time management skills, editing,
communications. Tools have to be taught, but only enough to be at a point
where they can create a regular document - and teach themselves (or take
evening courses) in advanced tools skills.
One more thing. I do not know of any courses that put enough emphasis on
learning computer technologies. Documenting software development (as opposed
to creating end-user documents) is an area with a lot of scope for technical
writers. My belief is that any good technical writing program should include
as much classroom time on topics such as IDE's, database design, systems
analysis and design, and computer networking as it does on teaching tools
such as Frame and RoboHelp.
My three cents (Canadian) worth
John Neil
Technical Writer
CIBC Mortgages Inc., Toronto, Canada
neilj -at- firstline -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
---
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.
