Kay Pentecost wrote: > As a result, when I worked in an application I > inherited a lot of code that > was never used... and when all I had to update was a > single field, I was > still updating the entire record. > > I know it's breaking YAGNI, and I know you probably > wouldn't do this on an > XP project... but what do people on this list think > about that way of > working? > > If you went into a company where the code was like, > what would you do?
I have seen that done very well, and almost XP-like. However, between the bad way to do it and the good way can be a very, very deep crevasse. If you expect to cross, you must go down a very long way, and then you have a very hard climb ahead of you. Update the entire record to update the field, Kay! (BTW YAGNI refers to source's cognitive burden, not its efficiency. But it helps.) ===== Phlip http://industrialxp.org/community/bin/view/Main/TestFirstUserInterfaces __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com 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/
