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: Managing Engineers (long) From:mpriestl -at- ca -dot- ibm -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 27 Nov 2000 17:04:01 -0500
Ceri Williams writes:
>Similarly the Technical Writer needs to understand enough of the
programming to
>understand how an application works, as this will at times make it easier
to
>explain to an end user how the application works. However, the Technical
Writer
>does not need to understand the full details of how the application works.
For
>example, a good Technical Writer does not need to know the technical
details of
>how the information is transferred from A to B. Generally it is enough to
>understand that the information *is* transferred from A to B.
What she said. I'm quoting this particular bit because it seems to be the
main bone of contention between Andrew and me. I may have stated too
strongly at various points that the writer doesn't need to know what goes
on in the guts of the app - certainly there are cases where, at least in
general terms, the reader should know what's happening, which means the
writer does too in order to explain it.
For example, in the case of a compiler, having docs that explain exactly
what a compiler does, and what a linker does, are some of the basic
background info that would go into the user's guide. However, the details
of how the tools work would not only be out of place, but potentially
revealing of trade secrets.
Speaking on my own behalf,
Michael Priestley
IBM Toronto Lab
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY. http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by SOLUTIONS, Conferences and Seminars for Communicators
Publications Management Clinic, TECH*COMM 2001 Conference, and more http://www.SolutionsEvents.com or 800-448-4230
---
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.
