Re: 4 the FAQ: Are Commercial DBMS Truly Relational?

From: Laconic2 <laconic2_at_comcast.net>
Date: Sun, 10 Oct 2004 15:26:18 -0400
Message-ID: <VdCdnRJRru1xEfTcRVn-rQ_at_comcast.com>


"Andrew McDonagh" <news_at_andrewcdonagh.f2s.com> wrote in message news:ckc0ch$3qm$1_at_news.freedom2surf.net...
> Also, IMHO, premature optimisation tend to create designs that are
> fragile to future changes.

Agreed.

And also, it tends to create logical designs that are ... well... illogical.

I like the term premature optimization.
In an earlier lifetime, when dealing with intelligent programs, we used to run into another phenomenon: premature binding.

In my experience, if the design is simple, sound, and relevant, and if the hardware isn't underconfigured for the load, most of the resulting system will perform satisfactorily. You then focus in on those few parts of the system that need to be sped up.

But often, when repairing the work of premature optimizers, you end up with a complete rat's nest, and one that performs lousy, to boot.

Again, going back to an earlier lifetime: "I know we aren't supposed to use GOTO, but it's more efficient this way!" Sigh! Received on Sun Oct 10 2004 - 21:26:18 CEST

Original text of this message