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.
From: Price, Becca
Subject: RE: Need a definition for "server"
Date: Tuesday, July 11, 1995 9:39AM
Thank you to all who have helped me in my search for a non-technical
definition for "server." I also consistently got the question "why would
you need one?"
The people for whom the document is being written (the requestors, not the
users) believe that our user community should only be told the bare minimum
they need to know in order to do their job. Anything else "will confuse
This is a frustrating situation for me and for other members of our writing
team, and not everyone here agrees with this philosophy. We've been
sneaking in more and more contextual and process-based information in our
documents, but apparently in my brief description of our network as
background for a "switch server connected" procedure, I got a bit cocky and
actually put in some technical information, and got caught at it.
But I did get some very good and usable suggestions from people, and I thank
the many who responded to me.