On 05/29/13 10:40 AM, Ted Roche wrote:
As a general rule, adding empty classes, containers, pages and methods "just in case" you're going to need it in the future is an anti-pattern of premature optimization. When you finally do need it, it inevitably needs to be in a different structure than what you predicted anyway. Better to do a clean refactor when its needed that to add a lot of overhead you may never need.
Amen, brother! Dan _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
