A couple of other random thoughts:
I remember Menachim Bazian saying "The sooner you get to the keyboard the longer the app will take."
I think one has to distinguish between an elaborate spec and good architecture. Agile or Extreme Programming doesn't mean ignoring architecture or analysis by any means, it just questions the viability of a fixed spec. Seems to me - at least in my own work - that allowing an app to evolve in short iteration cycles with client feedback means architecture (at least in one's undertstanding of the overall business problem ) is even more important. Kind of like knowing what key you are in in jazz improvisation.
>Hi all -
>
>Of course when I need some articles that discuss the above I can't find them. Anyone have good links to sites that discuss the virtues, cost-savings, lower-bug rate, etc. of not rushing through the analysis and design phases and just "coding right away"? Would love sites that discuss this from both a technical (better class design allows use in a larger number of applications without change) and business (cost-savings, better user-experiences, etc.) perspective.
>
>Thanks!
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
