Re: Whither book "Developing Windows Error Messages"

Subject: Re: Whither book "Developing Windows Error Messages"
From: AlQuin <cbon -at- WXS -dot- NL>
Date: Sun, 27 Dec 1998 21:35:39 +0100

On 22-12-1998 22:45 Chuck Martin wrote:

>to continue to design bad software as long as the error messages are clear.

>one of my goals was not only to make the interface understandable, but
>to advocate design that would avoid error messages by not allowing the
>users to take actions that would result in errors.

This is really the core of my view on Total Quality. Especially the 2nd
part of this quote: preventing is cheaper than healing.
The more obvious the use of systems will be, the less need for additional
documentation will remain. "Designing Well Brings Manuals To Hell..."
Too few documentation reflects this approach.
It's another solution to badly read manuals... ;-)

Kees de Bondt



*****************************************
The Quality Professionals from Holland
wish you and yours
a prosit neujahr
*****************************************
AlQuin Total Quality - cbon -at- wxs -dot- nl


From ??? -at- ??? Sun Jan 00 00:00:00 0000=



Previous by Author: Re: Information Mapping
Next by Author: Re: Whither book "Developing Windows Error Messages" 2
Previous by Thread: Re: Whither book "Developing Windows Error Messages"
Next by Thread: determine success


What this post helpful? Share it with friends and colleagues:


Sponsored Ads