|
There is a trade off. Sometimes you can spend more time making a program efficent than the users will ever save when they use it. If a program takes an extra hour to run over the course of a year but is easier to read and debug than it is a better program, IMO. Albert
----- Original Message ----- From: "Michael Ryan" <michaelrtr@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Subject: Re: QRCVDTAQ Date: Wed, 5 Jul 2006 13:33:24 -0400 I try to write applications that are inefficient and make up for it with more hardware. I'll put program calls in my code that call NO-OP programs and use For/EndFor loops to 1,000,000 just to get that inefficient look and feel. <snip> This encourages - forces shopsto write overly efficient applications with the minimum of features and accessibility.-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.