tag:blogger.com,1999:blog-3198935374994345981.post369043139366741317..comments2009-04-01T09:29:22.509+02:00Torkel Ödegaardnoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-3198935374994345981.post-59167682361568213542009-04-01T09:29:00.000+02:002009-04-01T09:29:00.000+02:00Absolutely right!<BR/>IMHO, Readability is more important than perpormence. Because, if your code is readable. you can easily refactor your code for performanceOğuz Kurumlunoreply@blogger.comtag:blogger.com,1999:blog-3198935374994345981.post-79864316286821556352009-03-31T21:58:00.000+02:002009-03-31T21:58:00.000+02:00Don't forget unnecessary inheritance and interface implementation.<BR/><BR/>I once worked on a huge project that had an interface for almost every since POCO and Service (Services, Repositories etc.) <BR/><BR/>Debugging was HELL. Y ou classes like this:<BR/><BR/>abstract class AggregateDomainObject : DomainObject<BR/>abstract class ProductBase : AggregateDomainObject, IProduct<BR/>abstract class Product : ProductBase<BR/>abstract class ExpiringProduct : Product<BR/>class EventProduct : ExpiringProduct <BR/><BR/>Needless to say that the interface "IProduct", the class "ProductBase" etc. were totally useless and just helped to bloat the whole app. (This is just one of the over 50 scenarios.)Tawani Anyangwehttp://www.blogger.com/profile/07048402899899544722noreply@blogger.comtag:blogger.com,1999:blog-3198935374994345981.post-33686506396232938322009-03-31T08:33:00.000+02:002009-03-31T08:33:00.000+02:00Couldn't agree more man...Anonymousnoreply@blogger.com