<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Performance as a Design Consideration</title><link>http://blogs.msdn.com/ericflee/archive/2008/10/27/performance-as-a-design-consideration.aspx</link><description>For many years now I've been frustrated by industry development practices that approach software performance in an ad hoc manner rather than as a design issue. Every time I argue in favor of considering a feature’s potential performance issues up front</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>infoblog &amp;raquo; Performance as a Design Consideration</title><link>http://blogs.msdn.com/ericflee/archive/2008/10/27/performance-as-a-design-consideration.aspx#9019860</link><pubDate>Tue, 28 Oct 2008 11:14:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9019860</guid><dc:creator>infoblog &amp;raquo; Performance as a Design Consideration</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://blog.a-foton.ru/index.php/2008/10/28/performance-as-a-design-consideration/"&gt;http://blog.a-foton.ru/index.php/2008/10/28/performance-as-a-design-consideration/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>