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. Learning your (A,B) C language From:Geoff Hart <geoff-h -at- MTL -dot- FERIC -dot- CA> Date:Tue, 7 Nov 1995 13:04:06 LCL
Jane Bergen asks if all tech. writers should be required to
learn C programming to exercise their craft in a
programming/software company. Jane, whether or not this is
required, it's certainly a useful asset if you need to
proofread (worse yet, to create) examples of code in your
software manuals.
There's no good reason this skill should be required. Your
company hired programmers for programming, and writers for
writing. Different, if occasionally overlapping, talents.
Ask your boss if s/he expects the programmers to be writing
documentation while you're busy programming the telephones
instead of doing what s/he hired you to do.
--Geoff Hart @8^{)}
geoff-h -at- mtl -dot- feric -dot- ca
Disclaimer: If I didn't commit it in print in one of our
reports, it don't represent FERIC's opinion.