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: Knowing prog. lang. +s to a TW's $? From:Deborah Meltzer <deborah -at- STARQUEST -dot- COM> Date:Mon, 13 Jan 1997 13:58:22 PST
>>Please say it ain't so! How can one even begin to address the needs of the
>>audience without working with the application or equipment?
>>Do many of you write documents without using the equipment or application?
>I didn't think I could even do such a thing, and had considered not even
>taking the job, but I'm glad I did. It isn't easy, but it IS possible.
Most of my projects have involved writing documentation without using the
application. Often when you are writing for a developer audience, many of
the tasks and functionality involved remain abstract. Initially, this is a
very difficult task to pull off. Intensive, focused interviews with
engineers, reading previous documentation about the product and its
peripherals (if such documentation exists) have been my primary methods of
coming to understand the products and how they work. When I do have the
occasional project now in which I can actually get my hands on the
application, the task of documentation has been relatively easy. I guess
it's a little like learning calculus and then doing some basic geometry for
dessert. So as Barb says, it CAN be done. And it can even be done well.
StarQuest Software, Inc.
email: deborah -at- starquest -dot- com