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.
Subject:RE: Brief introduction and request for advice From:"Barry Kieffer" <Barry -dot- Kieffer -at- worldwidepackets -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 15 Jan 2002 16:24:15 -0800
Greetings Laurence,
Sorry to hear about your misfortune.
My suggestion is going to be the suggestion of a hundred others. Lucky for you the answer is right in plain sight, and you even wrote it in this missive:
Learn new tools and technologies. It is not as hard as it might sound. Take a beginning programming class in something (almost) universal like the programming language C or Java. You are not expected to get an 'A' or start a new career as a programmer, but rather to understand how the programmers around you are thinking by association with programmers in your class; and have a cursory understanding of structured programming.
Learn a new tools and technologies. Do web searches on .NET, Java, XML, Network Security, what ever interestes you. Look to the STC where they have seminars, presentations, and workshops on tools so you can at least say: "Web Works Publisher? yeah, I know about that, played with it once, I am very interesting in working with it more."
Best of luck Laurence, be patient, I know it is not easy, but you will get there.
-Barry Kieffer
-----Original Message-----
From: Laurence Starn
I have been looking for work for the past
couple of months, but it seems like the qualifications for being a technical
writer have changed. Instead of being qualified by virtue of the fact that
you can write, employers now want to qualify you strictly on the basis of
your knowledge of tools and technologies.
I would be grateful for any suggestions you people might have.
Laurence Starn
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Attention ForeHelp and Doc-to-Help Users! Upgrade your existing product to
RoboHelp for FREE, through January 15th. RoboHelp can import your existing
Help projects! Learn how else RoboHelp can benefit you. www.ehelp.com/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.
