<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Quick-Fixes help generate switch blocks</title>
	<atom:link href="http://blogs.jetbrains.com/dotnet/2006/06/quick-fixes-help-generate-switch-blocks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.jetbrains.com/dotnet/2006/06/quick-fixes-help-generate-switch-blocks/</link>
	<description>ReSharper for productivity, dotTrace for performance</description>
	<pubDate>Mon, 22 Mar 2010 04:35:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Development on a Shoestring</title>
		<link>http://blogs.jetbrains.com/dotnet/2006/06/quick-fixes-help-generate-switch-blocks/#comment-50</link>
		<dc:creator>Development on a Shoestring</dc:creator>
		<pubDate>Thu, 06 Jul 2006 12:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/dotnet/2006/06/generating-switch-labels-with-quick-fixes/#comment-50</guid>
		<description>&lt;strong&gt;.NET Development tools&lt;/strong&gt;



Ian Olsen&#8217;s ReSharper vs. CodeRush post (and it&#8217;s subsequent follow-up).  He makes some very useful points about the two programs.  After my ReSharper demo licence expired recently I really empathise with this point:
I really miss ReSharp...</description>
		<content:encoded><![CDATA[<p><strong>.NET Development tools</strong></p>
<p>Ian Olsen&#8217;s ReSharper vs. CodeRush post (and it&#8217;s subsequent follow-up).  He makes some very useful points about the two programs.  After my ReSharper demo licence expired recently I really empathise with this point:<br />
I really miss ReSharp&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Obfuscator</title>
		<link>http://blogs.jetbrains.com/dotnet/2006/06/quick-fixes-help-generate-switch-blocks/#comment-22</link>
		<dc:creator>Obfuscator</dc:creator>
		<pubDate>Fri, 16 Jun 2006 08:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/dotnet/2006/06/generating-switch-labels-with-quick-fixes/#comment-22</guid>
		<description>Hi Shea,
I can relate to that and, actually, a number of our own developers would agree with you a 100%. This goes hand in hand with the idea of "developing with pleasure" which we've always advocated and promoted.</description>
		<content:encoded><![CDATA[<p>Hi Shea,<br />
I can relate to that and, actually, a number of our own developers would agree with you a 100%. This goes hand in hand with the idea of &#8220;developing with pleasure&#8221; which we&#8217;ve always advocated and promoted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shea</title>
		<link>http://blogs.jetbrains.com/dotnet/2006/06/quick-fixes-help-generate-switch-blocks/#comment-21</link>
		<dc:creator>Shea</dc:creator>
		<pubDate>Wed, 14 Jun 2006 15:04:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/dotnet/2006/06/generating-switch-labels-with-quick-fixes/#comment-21</guid>
		<description>While ReSharper drastically improves programmer productivity (I used the rate of 15% to convince my non-technical manager...), I find I most profit from the ability to catch common programmer errors (e.g., Array.Cop doesn't exist) before the compilation cycle. I feel like less of a failure when my syntactical errors are caught by ReSharper than by the compiler. The compiler is alot meaner than ReSharper in the sense that when you make a mistake in the sense that all implications of that mistake are brought to your attention (it's like if you lose a bunch of money in the stock market and you're forced to immdiately see yourself on the bus instead of the BMW, AND your wife leaving you). Whereas ReSharper only lets you know of the problem locally, not globally. Much more pleasant.</description>
		<content:encoded><![CDATA[<p>While ReSharper drastically improves programmer productivity (I used the rate of 15% to convince my non-technical manager&#8230;), I find I most profit from the ability to catch common programmer errors (e.g., Array.Cop doesn&#8217;t exist) before the compilation cycle. I feel like less of a failure when my syntactical errors are caught by ReSharper than by the compiler. The compiler is alot meaner than ReSharper in the sense that when you make a mistake in the sense that all implications of that mistake are brought to your attention (it&#8217;s like if you lose a bunch of money in the stock market and you&#8217;re forced to immdiately see yourself on the bus instead of the BMW, AND your wife leaving you). Whereas ReSharper only lets you know of the problem locally, not globally. Much more pleasant.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
