Re: agile programming and agile db design

heylow wrote:
> I am in a place where people peddle agile approach. Four months have
> passed by, with two teams, each comprising 10 developers, working from
> two states. No refactoring has done at db level; nor is it going to
> happen. The shop hired a j2ee caching specialist, and he advised
> pagination and on-the-fly sorting at db-level, and he parrots
> scalability. Another snake oil product!
>
> For a query, we have joined 10 tables to get the required for a
> particular screen. Many other queries need at least 7 tables. When
> people designed tables in previous iterations, they had no clue about
> the requirements for the future requirements.
>
>
> Is this what agile programming and db design is about?

This has nothing to do with Agile. This is people using the good reputation of Agile to cover their ignorance. Agile is about project management and planning. Not about making bad decisions.

What hyou describe is the technology equivalent of draping oneself in the flag and calling upon others to not disagree because to do so would be unpatriotic.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org