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: Writing Specifications thread From:CASSIN Gilles <GCassin -at- MEGA -dot- COM> Date:Wed, 24 Mar 1999 16:48:17 +0100
Josee Mariann Proulx wrote:<snip>Scott Wahl responded:<snip>Valarie
Tassari threaded:<snip>
<snip>
Gilles Cassin adds:
It all depends on the organization you work for. This remembers me of a
meeting, a few years ago, on the 27th of December (Thursday):
-Development Team Manager: the Beta //euphemism for pre-alpha// is to be
delivered on January 2. (Tuesday)
-TW (I): OK, just give me the product
-Developer: Doesn' work yet
-DTM: You can use the specs, they are fine.
-TW (still I): If they are OK, just handle them to the client, it's only
for a Beta and the client knows.
-DTM: We can't! The specs outdated, they won't be able to use the
product with that //censored//
-TW : //the reader uses the onomatopoeia she/he prefers//.
In this company, I refused to edit//co-operate for the specs
Gilles CASSIN mailto:gcassin -at- mega -dot- com
+33 1 42 75 40 22
My opinions are mine, and neither you nor my company can take credit for
them. YOU can cite them if you think they were of use.
