Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-adm!brl-smoke!smoke!gwyn@BRL.ARPA
From: gwyn@BRL.ARPA (VLD/VMB)
Newsgroups: net.lang.c
Subject: Re:  questions from using lint
Message-ID: <901@brl-smoke.ARPA>
Date: Thu, 15-May-86 19:29:15 EDT
Article-I.D.: brl-smok.901
Posted: Thu May 15 19:29:15 1986
Date-Received: Sun, 25-May-86 11:44:04 EDT
Sender: news@brl-smoke.ARPA
Lines: 11

You seem to have missed a key word in my posting.
I urged "a proper job of analysis and design"
before coding.  A proper job of systems analysis
addresses the issues you raised.  Structured
software development even encourages early hands-
on use of prototypes, to REFINE the design, not to
try to ARRIVE at a design by trial-and-error.

There IS a lot of knowledge about user interaction;
like structured software development, however, few
practitioners appear to have bothered to study it.