Re: The MySQL/PHP pair

"Bill H" <wphaskettatTHISISMUNGEDadvantosdotnet> wrote in message news:G9ednfSZNJfhlA7cRVn-qg_at_adelphia.com...

> Several of my acquaintances have pointed out my difficulty to explain
> complex issues in a simple sentence. :-)

I have the same problem. When I aim for "concise", I usually hit "terse". And when I aim for "complete", my wife asks me, "is this going to be long" after about 7 seconds.

>
> We do, however, seem to communicate; but with a little give-and-take. I'm
> hoping this is an example of such.
>

Yeah!

> Perhape we can incorporate our different experiences to explain (or
suggest)
> how a database can be built/designed to incorporate the needs of the
> application.
>
> How cool would that be. :-)

Ultimately cool.

I don't have much to say that's definitive, but that's probably just as well.

Here are two places to start:

The programming disasters of the 1950s and 1960s got replaced by the design disasters of the 1970s and 1980s.
These in turn got replaced by the analysis disasters of the 1990s and 2000s. Analysis is where we need to focus on improvement. Analysis is slow, costly, incomplete, and inaccurate. And the results are not useful enough to design and programming.

A database is a subsystem of a larger system. What is that system? An application is a subsystem of a larger system. What is that system? How far up this ladder to we have to climb before we are talking about the same system?

I know the above is very vague, and it'll be torn to shreds in the newsgroup. But this is where I'm starting from. Received on Thu Nov 11 2004 - 13:11:31 CET