<?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 Inspections</title><link>http://blogs.msdn.com/jmeier/archive/2007/07/08/performance-inspections.aspx</link><description>In this post, I'll focus on design, code, and deployment inspections for performance. Inspections are a white-box technique to proactively check against specific criteria. You can integrate inspections at key stages in your life cycle, such as design,</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Security Inspections</title><link>http://blogs.msdn.com/jmeier/archive/2007/07/08/performance-inspections.aspx#3896473</link><pubDate>Mon, 16 Jul 2007 18:24:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3896473</guid><dc:creator>J.D. Meier's Blog</dc:creator><description>&lt;p&gt;Inspections are among my favorite tools for improving security. I like them because they’re so effective&lt;/p&gt;
</description></item></channel></rss>