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: Reversing errors is trivial? From:Brenda Ruetschi <Bruetschi -at- ALPHA88 -dot- COM> Date:Thu, 24 Dec 1998 09:50:32 -0500
> What are the priorities? Making it easy for the programmers or
for the users.
What is the budget? When is the release date? How many programmers
do you have? How good are your programmers? How fast is the machine (or
network) on which the application will run? How much memory does your
workstation have? What about the servers? What other technical issues might
conflict with undoing information? Is information generated and ported to
different systems? Is this going to run on a single computer or will it
dynamically send processes to different machines throughout a network to
lighten the load?
All of these things will determine your priorities. Unlimited Undo
will eat memory, may significantly slow system performance, and could
drastically burden the system that the application is woreking on.
Making users your priority may very well mean the unlimited undo is
not an option.
Alpha Technologies, Inc.
bruetschi -at- alpha88 -dot- com