RE: agility programming and DBA's?

Michael,

This RAD approach is interesting. What has happened is that most systems are so small either in the number of users or the amount of data that proper database design really doesn't matter any more. The hardware is so strong(ie: fast) that a bad database design just does not have the impact that it would have if there were thousands of users or terabytes of data.

I disagree with it, but that is the way of the world -=20

"Lets do it wrong fast so that we can hurry up and fix it right later".

Topm

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Michael McMullen Sent: Thursday, May 26, 2005 10:36 AM
To: oracle-l_at_freelists.org
Subject: Re: agility programming and DBA's?

Why do people think one size fits all. It probably works really well for somethings and not so well for others. The buzzword around here is
"rapid

development" which sounds very much like "agile programming". The developer
works right with the client, gets screens up as quick as possible and they
hash out the rest. Saves alot of money but I'm sure everyone can see the downside. Scope creep gets huge, big denormalized tables etc. But it works
well for small projects. the traditional model to application development
can burn through millions just doing requirements. Our niche is we get the
product out there quickly to the client, but we don't design billing systems, usually all dss stuff.

Mike

--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l