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.
And on this list (or a similar list), I remember a thread on the idea that
the tech writer should write the Help file first so that the programmers
could use the Help file as the spec.
Some participants were quite taken with the idea.
Some participants argued that there was stuff that belonged in a spec that
had no business being in a Help file.
Note: I tried some quick searches of the archive but couldn't find the
thread.
Jim Shaeffer
jims -at- spsi -dot- com
-----Original Message-----Snipped.
From: Paul Hanson [mailto:PHanson -at- Quintrex -dot- com]
"If a programmer has to write up a spec with the information that is
used to create help text, why not have the programmer create the help
text? Why have a duplication of effort, since the help text is
information from the specs?"
