home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!umd5!shy.umd.edu!hunt
- From: hunt@shy.umd.edu (Brian Hunt)
- Newsgroups: news.software.nn
- Subject: Re: Why is NN so common?
- Keywords: poor design
- Message-ID: <hunt.721298877@shy.umd.edu>
- Date: 9 Nov 92 08:47:57 GMT
- References: <BxAuIy.4qJ@ie.utoronto.ca>
- Sender: news@umd5.umd.edu
- Lines: 17
-
- green@ie.utoronto.ca (Marc Green) writes:
- >'ve recent switched to a machine that uses nn and am stunned at what poorly
- >designed piece of software it is. It violates just about every human factors
- >principle in software design (consistency, dialog closure, smooth error
- >handling, etc). And of course, the documentation is a joke.
-
- >The only good thing about it is that it serves as a source of wonderful
- >examples for my software engineering course on how not to design systems.
-
- >Why is this damned thing so common?
-
- Gee, if the point of software engineering courses is to teach people
- how not to write software like NN, then no wonder most commercial
- software is so lousy...
-
- Brian Hunt
- hunt@ipst.umd.edu
-