William K. Volkman wrote:
> Additionally that is a programmer centric view, something that would
> only be applicable to small projects. Once you get 10s of developers
> involved chaos ensues until a DBA is appointed to analyze, normalize,
> and document the data requirements. Even in small systems the idea
> that the code has the definition breaks down quickly. I.E. Deploying
> program "A" which is up and running, now you want to add program "B"
> which needs a couple more fields. If you don't have the time to go
> back and update/change "A" (including testing and perhaps release
> management) and "A" tries to enforce the structure of the tables, "B"
> will fail (and then you refactor, moving the definition back out of
> the code ;-).
1. I never plan on working on a team with a ton of developers. I enjoy
working on small teams because, in my experience, the end result is
of a much higher quality, and at an earlier date. Large teams get
bogged down is a mess of requirements, architecture discussions,
and meetings.
2. I don't buy the "large systems" argument at all. I suspect any
problems here come from assuming that a "large" system requires a
"large" team, leading to the problems I discuss in #1.
Anyway, I was (mostly) kidding about the DRY argument anyway. A better
point to make is probably that DRY is overrated in the first place ;)
--
Jonathan LaCour
http://cleverdevil.org
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
