I was thinking about YAGNI yesterday. Normally, I see
most people create a customer class that holds domain
information and another class, say CustomerDb that
persists the information from customer to a database.
This makes sense, becuase if I want to persist to
something different (like a flat file) I can create a
new class to handle it while leaving the domain class
intact.
But two objects that share the same basic fields
(customer) seems to go against YAGNI. Is this how most
people solve the problem or is there a better
solution?
Thanks,
Stede
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - What will yours do?
http://my.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/
