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.
it is a big step, wave the specs now.
User need the program and the documentation at the same time. But the
development process of software is a long process, as well the development
of documentation.
The Specification helps us a lot writing the documentation. The program
will reach the specification requirements at the end. So it will meet the
documentation.
Formerly I wrote documentation using the ready part of the program. On next
day it worked otherwise, because of development was going on, or there was
bug fixing.
Even during acceptance test this is an advantage; normally, if the program
does not work as described in documentation, the documentation is right.
