> If the specs are fluid, all design confidence flies out the window and the resulting system is over-engineered to cover eventualities. IMO that achieves the

> If the specs are fluid, all design confidence flies out the window and the resulting system is over-engineered to cover eventualities. IMO that achieves the worst of both worlds. If the specs are fluid you have to be able to iterate quickly, dive in, modify code and deploy. Any time code gets over-engineered to elegantly handle future changes it just slows down those changes. You need to accept or even embrace that the requirements will change, not to try and preempt the changes. For 90% of the corporate web apps I've seen a simple CGI site would have been the correct solution, able to change quickly with no layers upon layers of dependencies.