tag:blogger.com,1999:blog-13831777.post7140412297449055001..comments2008-06-25T23:05:31.843-04:00Damon Poolehttp://www.blogger.com/profile/16561311551267979837noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-13831777.post-38046801421524310812008-06-25T23:05:00.000-04:002008-06-25T23:05:00.000-04:00Love the analogy!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13831777.post-60585033875799470102008-01-02T15:18:00.000-05:002008-01-02T15:18:00.000-05:00I think "bug-free software" is an oxymoron for all but the most trivial software implementations.<BR/><BR/>To me, Agile is the embracing of three realizations: First, that any software is only an approximation of the stated requirements, second, that the stated requirements are only an approximation of the actual requirements, and third, that the actual requirements are not static but change over time.<BR/><BR/>"There is no bug" is a good shorthand for the first realization. An agile process lets you more easily respond to the shortcomings (bugs) that will inevitably be found in the implementation of the requirements.<BR/><BR/>The difference between an average developer and an excellent one is their ability to look past quick-fixes to root causes, and past root causes to systemic, architectural flaws.Alannoreply@blogger.com