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.
At 09:49 AM 9/29/99 -0700, Anthony Markatos wrote:
>I have noticed an increase in job listings for combination
>Programmer/(Technical) Writers. ... write end user
>documentation directly off of code.
>What is the demand for such people? Is this some sort of major new trend?
>Can you recommend any good written materials on this?
>... I had a job where ... the interface
>was so ... poorly designed...I had to tear apart the code to
>figure out what the thing did! ... this a real step backwards.
One would hope that the requirement for writers with programming
skills was not for the reasons you describe. Here's my take on
the issue that makes the requirement a couple of steps forward.
Increasingly, companies are packaging their code to share with
other companies. Object-oriented programming allows a development
team to package up their code in discrete modules and sell it to
other companies. The nature of the code stops the purchasing
team from nosing around, making changes, and pirating the code.
More and more writers are being called upon to produce API and
SDK documentation, and they are unprepared. A company that
anticipates generating multiple APIs may look to a combination
programmer/writer as the best fit for the job.
(Note to STC'ers -- I'll be delivering a session on creating
API docs at the upcoming Region 8 conference. I've also submitted
the session for presentation at Orlando, but acceptance notices
are not due out until December.)
Then too, programmer/writers have an advantage when it comes
to embedding documentation within an application. They're the
folks that get to do wizards and cue cards and the like because
they don't need much in the way of development-team support
to get the job done.
And then there are the writers who actually produce docs for
programmer end users...