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.
Richard Wyatt asked for advice on Fri, 16 Sep 1994:
>I'm trying to make the jump from programming to tech writing, done a lot
>of reading and talking to other writers, but I'm still unclear about how
>to take the first active step.
...
>Though I've done a lot of writing in other
>capacities, and I've done a fair amount of tech writing as part of my
>work, I'm just trying to break in now.
....
You didn't mention whether or not you've updated your resume yet.
If not, then that's the place to start. Since you've already done
technical writing in the course of your work as a programmer, you
should highlight this on your resume.
Step two, gather together as many worthy examples of your tech
writing work as possible and arrange them in a portfolio. Be prepared
to discuss these with potential employers, who will ask questions
about how these were created (i.e., wordprocessor used, graphics, etc.)
Step three -- a bit tricky -- is to balance your value to prospective
employers. Some will see you as a programmer who can do a little
writing, which is NOT what you want. But others will see you as a
writer who can dive into the code to create software documenation
of a very sophisticated order. The latter are the potential employers
you want to attract.
Good luck! And please let us know how it goes.
Live long & prosper,
Mike LaTorra
Documentation Supervisor
Accugraph Inc.
mikel -at- accugraph -dot- com
......................................................................
The opinions expressed are my own, and not necessarily those of my
company -- but they probably should be.
......................................................................