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.
On 26 Jul 95 at 13:30, Renee Cornelisen -at- SLC -dot- unisysGSG -dot- com asked:
> The digest of July 26, 1995 included a post regarding a job for a
> senior tech-writer at Novell, in Utah. It required knowledge of C
> and the ability to read and understand source code. Is that
> something tech-writers do?
It's something that is very useful to be able to do.
It serves two purposes: first it adds to your credibility with the
programmers, second, it enables you to understand the process of the
software. You should not need to be able to *write* or debug code,
but knowing what stack and heaps and pointers are can often help you
to unpack some of the mysteries to the masses.
Remember too, that job postings are often wish-lists...
Grant Hogarth, Information Services/Technical Support
Onyx Graphics Corp.
"If they have to look it up, they're already aggravated"
--B. Block, San Diego Technical Writer