<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com : Stories kicked by rich36</title>
    <description>Stories kicked by rich36</description>
    <link>http://www.dotnetkicks.com/</link>
    <language>en-us</language>
    <copyright>Atweb Publishing Ltd.</copyright>
    <docs>http://backend.userland.com/rss</docs>
    <generator>DotNetKicks.com - .NET links, community driven</generator>
    <ttl>30</ttl>
    <item>
      <title>Why Every Good Developer needs to Know how to Mock</title>
      <description>While unit testing is generally considered a good practice ( even among those who don't do unit tests), mocking doesn't seem to carry the same aura. There are a lot of arguments saying why mocking is bad , how it kills testability etc. 

But in my day-to-day job, as well as in my personal projects, I found mocking is definitely indispensable.
 &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fitscommonsensestupid.blogspot.com%2f2008%2f09%2fwhy-every-good-developer-needs-to-know.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fitscommonsensestupid.blogspot.com%2f2008%2f09%2fwhy-every-good-developer-needs-to-know.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Why_Every_Good_Developer_needs_to_Know_how_to_Mock</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Why_Every_Good_Developer_needs_to_Know_how_to_Mock</guid>
      <pubDate>Fri, 19 Sep 2008 05:31:02 GMT</pubDate>
    </item>
  </channel>
</rss>