Hi, Phlip!
--- In [EMAIL PROTECTED], Phlip <[EMAIL PROTECTED]>
wrote:
> 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.
The uh... for want of a better word... framework or generating a
class as a "Data Gateway" or the updating part?
If you meant the framework/generator can you expand on how it was
done well in an XP-way?
> However, between the bad way to do it and the good way
> can be a very, very deep crevasse.
Please expand on this???
Kay
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/
