Russell: I zeroed in on just one part of this exchange:
Russell Gold wrote: >>Refactoring without a clear >>architectural goal is just polishing a turd. > Or am I simply > wrong in assuming that we can refactor to a good architecture without > extensive documentation and review? It is certainly possible to refactor towards a good architecture without extensive documentation. I'm not sure what "review" means here, so I can't comment on that. Two ingredients are necessary (but, I'm sure, not sufficient): 1. Communication among the people refactoring the code (in general), and 2. Agreement among those refactoring the code on an overall high-level design goal (in particular) Refactoring without a purpose /can/ be successful, but usually only by accident. (That said, refactoring blindly is a good way to develop refactoring skill; it just might not result in a better design.) -- J. B. (Joe) Rainsberger Diaspar Software Services http://www.diasparsoftware.com :: +1 416 791-8603 Predictable, repeatable, quality delivery To Post a message, send it to: [EMAIL PROTECTED] To Unsubscribe, send a blank message to: [EMAIL PROTECTED] ad-free courtesy of objectmentor.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/extremeprogramming/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
