﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Yoni commented on Dont Repeat Yourself: Pragmatic Approaches</title><description>The problem I see with this approach is that you end up with a public property which means that embedding the newly added field has at least one more location which has to be modified - either the UI or business logic external to the entity class.
  
  
Public properties are generally considered evil (see another article by Allen Holub: www.javaworld.com/javaworld/jw-09-2003/jw-0905-toolbox.html) and usually end up causing duplicated code.
</description><link>http://ayende.com/2252/dont-repeat-yourself-pragmatic-approaches#comment1</link><guid>http://ayende.com/2252/dont-repeat-yourself-pragmatic-approaches#comment1</guid><pubDate>Fri, 23 Mar 2007 16:37:32 GMT</pubDate></item></channel></rss>