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.
In a product liability or patent lawsuit, one of the first
things that usually happens is the issuance of subpeonas
for internal documents relating to the development of the
product in dispute. My last company was involved in
several actions (patent), and the lawyers descended on the
Tech Comm office like a swarm of locusts, collecting all
kinds of internal stuff. Ironically, in a patent action,
the more of your employees' names are on development docs
the better, while in a liability action, it's the reverse.
Ideally, you want a lot of people listed as having been
involved, but as little info as possible identifying what
individual was responsible for any specific item. That's
why SW "easter eggs" usually display huge lists of
development team names with few clues as to who did what.
Gene Kim-Eng
------- Original Message -------
On
Mon, 8 Sep 2003 15:50:01 -0400 John Posada?wrote:
It's internal documentation read by and used by his peers.
