Re: What should I say to a *nix community? -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: What should I say to a *nix community?
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Tue, 26 Aug 2008 16:07:47 +0100
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>
Openpgp: id=D1980033; url=http://pgp.mit.edu:11371/

James Lampert wrote:

Running "old stuff unmodified" is a perfect expression of the old
engineer's maxim, "if it ain't broke, don't fix it."

Then DeLong, Eric wrote:

I gotta say, I'm really starting to hate that old phrase.... The
problem with it is NOBODY ever defines what broke means.

IMO it's pretty simple ... Broke means the application no longer does what it was designed to do.

If an application no longer performs the function that the business requires ... then it's broken. If it works as designed and performs the functions the business requires, then it ain't broke.

david

Follow-Ups:

Re: What should I say to a *nix community? , David Gibbs
Re: What should I say to a *nix community? , smorrison

This mailing list archive is Copyright 1997-2026 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.