Posted by Jerry Stuckle on 05/17/06 01:07

Bent Stigsen wrote:
> Kenneth Downs wrote:
>
>
>>Jerry Stuckle wrote:
>>
>>
>>>Kenneth Downs wrote:
>>>
>>>>Bent Stigsen wrote:
>>>>
>>>>
>>>>
>>>>>Can't help wonder why you would you say something like that. Are you
>>>>>trying to make him feel insulted, or just joking because you don't
>>>>>believe putting a little effort in the database-design process is worth
>>>>>it or possible in the way Jerry presents it.
>>>>
>>>>
>>>>None of the above. I'm laughing at Jerry's close-mindendess.
>>>>
>>>>It appears that Jerry doesn't know how much he doesn't know, and if that
>>>>is true then he would not feel insulted by anything I say.
>>>>
>>>>As for being more direct, I made my points in the earlier posts.
>>>>Planning is good, I do it every day, we should always learn to do it
>>>>better, but a
>>>>wise man learns to expect the unexpected. The only system that doesn't
>>>>change is a dead system.
>>>>
>>>>Cheers,
>>>
>>>No, the system which doesn't change is a well-planned system.
>>>
>>
>>Brent: QED.
>
>
> Well then, feel free to laugh at me too. :)
>
> I generally agree, allthough to a statement like the above, I would add a
> disclaimer regarding its validity, with conditions like natural disasters,
> year 10000+ bug, and other dealbreakers which could be expected. But I can
> safely say I will fall short when it comes to the unexpected.
>
> /Bent

That's true - but I could also claim it shows a weakness in the design.

An ideal design would never have to be changed. It would be complete and
flexible enough for anything the customer would (reasonably) want to do. Note
that I'm not saying a "perfect design" which does everything. But one which
would meet that customer's needs for years to come.

But of course we can't always create that idea design. But the better our
understanding of the customers business and needs, the closer we can come to it.
Which means the less chance things need to be changed in the future.

Some people think changing a database is a minor issue. In some cases it is -
but it can also be a huge issue. For instance - the infamous Y2K bug was
basically a database design problem. And look what it cost companies just to
change a column from 2 digits to 4.


--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[Back to original message]