RE: [AM] Unfounded assertion
Jason Gorman <[email protected]>
| Newsgroups | gmane.comp.programming.modeling.agile |
|---|---|
| Message-ID | <[email protected]> |
Is refactoring "problem domain stuff"? I thought it was about improving the technical design without changing what the system does. Surely refactoring is "solution domain"? Jason Gorman http://www.objectmonkey.com -----Original Message----- From: Adrian Howard [mailto:[email protected]] Sent: 02 February 2004 15:10 To: [email protected] Subject: Re: [AM] Unfounded assertion On Monday, February 2, 2004, at 11:00 am, Hubert Matthews wrote: > Adrian Howard wrote: > >> The better code review sessions I've been involved were more about >> building the right system than they were about preventing mistakes. >> More "We can refactor that out into a new class" >> than "That will die horribly on edge case foo". > > This seems contradictory to me. The first sentence implies an > emphasis on the problem domain, but the second one seems to value > technical matters rather than problem domain. Can I ask you to > clarify, please? Sorry, my poor communication skills again :-) I was trying to say that better code review sessions often focus more on problem domain stuff (refactoring, etc.) than bugs. Good code reviews as much, if not more, about building the right system than they are about spotting and preventing errors. Clarified? Adrian For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com --^---------------------------------------------------------------- This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h Or send an email to: [email protected] TOPICA - Start your own email discussion group. FREE! http://www.topica.com/partner/tag02/create/index2.html --^----------------------------------------------------------------