Re: Did I write a good (efficient) program?

In article <57qIj.23163$0o7.2366@[EMAIL PROTECTED]
>,
Michael Mattias <mmattias@[EMAIL PROTECTED]
> wrote:
>You know, I've always used three tests to decide if code is well-written:
>
>1. Does it work?
>2. Is it *relatively* efficient?
>3. Is it maintainable?
>
>You need a "yes" answer to all three questions to have well-written code.
>
>While 'works' is non-negotiable, I'll often often trade 'ultimate 
>efficiency'  for maintainability; e.g., "ultimate" efficiency can often
be 
>best achieved by using lots of GO TOs; but this comes at a
maintainability 
>cost I am generally not willing to pay.

Where has this been talked about before... ahhhh... from 
<http://groups.google.com/group/comp.lang.cobol/msg/5f032ffb073f4861?dmode=source>

--begin quoted text:

(T)hat is a Major Source of Debate, I believe... the more that code caters

to hardware functions the more efficient it is... and the less 
structured/maintainable/****table it is.  You makes your choices, you takes

the results.

[snip]

All that aside I rarely concern myself with what others think... no matter

what one does there are those who will say that one is a hidebound 
dinosaur and others who will say that one is a slave the the 
flavor-of-the-month.  If program-runs perform next-assignment else perform

code-like-hell until damned-thing-works... don't get much plainer than 
that.

--end quoted text

DD