changing from programmer to tech writer (was: Webster Techwriters online course)

["Monique Semp" <monique -dot- semp -at- earthlink -dot- net>]

Hi Ben,

I don't have any info about the course, but did want to comment about the
career change you're considering.  I took the same route: I was a software
developer for a dozen years before switching to tech writing.  (And the
switch somewhat coincided with my move to the same Bay Area, assuming you
mean San Francisco Bay.)

What I wanted to comment on is that you may not need to constrain your
search to entry-level positions.  Instead, what you can do is look
specifically for API Writing positions.  The benefits are many:

* There's typically less emphasis on the more
creative/graphical/tech-writing-tools side (the emphasis is on the
programming/development tools).

* You're already more qualified than most writers to do API doc work
(because you've been a programmer).

* There's not usually an "entry-level" or "senior-level" designation
attached to API doc positions.

* Once you get an API documentation assignment, you can then say you're a
tech writer, and leap-frog past that entry-level point.

My first position was officially as a "Senior API Writer", but of course I
worked on many other tech writing projects, and was able to advance in the
"real tech writing" areas faster than I would have otherwise.

And you didn't ask, but my experience has been that I like tech writing
much more than I liked programming.  And by concentrating on API
documentation, I feel I get the best of both worlds: I still get to keep my
fingers in the code (I've used Javadoc and DoxyS, and other tools work
similarly in that the documentation is created from the source code itself,
where you embed the doc comments), especially since my primary client is a
small start-up with not a lot of process.  That means that there aren't
really detailed specs to work from, so I have to work my way through the
code.

But at the end of the day, I don't have to stay up until 3 AM trying to
find that errant semi-colon or bad logic.  I just document how it's
supposed to work, and then write the Release Notes to explain away the
Known Issues :-).

And on the creative side, I've had a chance to learn all kinds of wonderful
things and tools.  Illustrator still baffles me, but I use Visio routinely
to create architecture and flow diagrams, InDesign for page layout, and
FrameMaker for non-API work.  You can also put your programmer's analytical
skills to use with those latter two applications if you get into template
design and make it your business to search for plug-ins and tools anytime
you find yourself dealing with annoying repetitious tasks.

So maybe more than you wanted to know, but I consider it on topic.

-Monique


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help  
2009 tips, tricks, and best practices.
http://www.doctohelp.com/SuperPages/Webcasts/

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info. 

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat