http://www.codingthearchitecture.com/2006/02/09/speculative_design.html From Agile Answers comes the following paragraph (emphasis added), which is pretty timely given the conversations I've had recently. Do the simplest thing for the task at hand Originally a pushback against speculative development (particularly in ... en Simon Brown Thu, 09 Feb 2006 20:21:28 GMT Pebble (http://pebble.sourceforge.net) http://backend.userland.com/rss http://www.codingthearchitecture.com/2006/02/09/speculative_design.html#comment1139516488452 I think this points to the larger folly of thinking that you can design a large, complex system up front. Any system that is complicated enough to require you to think about its design ahead of time is complicated enought that you'll probably get portions of the design wrong. Brooks had this idea in a rule that said, "Plan to throw one away, you will anyhow". I find that my third pass at a new problem is the first one that shows true insight. If you don't allow time for design to evolve, it will just fail instead. Rob http://www.codingthearchitecture.com/2006/02/09/speculative_design.html#comments http://www.codingthearchitecture.com/2006/02/09/speculative_design.html#comment1139516488452 Thu, 09 Feb 2006 20:21:28 GMT