Chris if you read the more recent messages I wrote you'll see that I'm not evangelizing poor architectural design or poor implementation. My experience in the industry showed me that project management methodology and architectural design/implementation go hand in hand. I strongly believe in the following: take the same team of people, give them the same project, but manage them once with waterfall and at the other time with agile, and they'll come up with different architectural designs. This is because the assumptions, the perceived needs etc etc are different in these two cases. And please allow me to strongly disagree with you and say that developing software (for consumer electronics, I DON'T mean avionics) and building houses/cars is an analogy as poor as in can get.
On May 28, 7:36 am, "Christopher Van Kirk" <[email protected]> wrote: > I think you're confusing a project management methodology with an > architecture. Design is an architectural concern, and has nothing > intrinsically to do with delivery dates or management philosophies. The > analogies were to point out the flaw in your logic. The house, car and work > animals require a strong foundation to perform their function, and the same > is true of software. > > Inspired flexible design is a critical ingredient to making a project > management approach like 'Agile' work. Get it wrong and you'll get lost in > refactoring hell. > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
