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:Test Phase From:"USA::MU17692" <MU17692%USA -dot- decnet -at- USAV01 -dot- GLAXO -dot- COM> Date:Fri, 3 Mar 1995 19:54:00 EST
One of the roles I played as a technical writer during the test phase of
software for which I was writing documentation was to liaise between
the testers and the programmers. The relationship between the testers and
the programmers was often strained because testers only produce negative
results. Has hard as they try to praise the good work they see, what they
actually produced in writing were problem reports. What I tried to do was
get problem information from the testers to the programmers *before* the
testers wrote them up officially. In this way, the problems never existed.
I was able to update my documentation and the programmers corrected the
code and management was never the wiser. ;-)
-Mike Uhl (uhl~m -at- glaxo -dot- com)
Glaxo Inc. Research Institute
Research Triangle Park, NC
