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: Keeping track of software changes From:Laurence Burrows <burrows -at- IBM -dot- NET> Date:Wed, 4 Nov 1998 15:26:23 +1100
Kathy Stanzler wrote:
--------------snip
How do you make sure Doc gets notified of ALL changes to
the GUI? Is there a system or a software product that ensures that this
information isn't lost?
--------------snip
At one site I convinced management that Tech writers also made great beta
testers -- because they had to access all parts of the product in order to
analyze procedures and understand the underlying concepts.
The manager agreed, so the systems development team routinely burnt a CD
with the latest beta and passed it on, claiming 'caveat emptor'.
I did uncover some really interesting quirks that way, including interface
problems with companion products that were not part of the testing cycle.
