<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com : Stories kicked by philosophil</title>
    <description>Stories kicked by philosophil</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>Guidelines on Code reviews</title>
      <description>Guidelines to conduct a good code review. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fphilosophil.spaces.live.com%2fblog%2fcns!7E55D8EFA2AEE5D6!159.entry"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fphilosophil.spaces.live.com%2fblog%2fcns!7E55D8EFA2AEE5D6!159.entry" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/csharp/Guidelines_on_Code_reviews</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/csharp/Guidelines_on_Code_reviews</guid>
      <pubDate>Mon, 14 Jul 2008 20:45:26 GMT</pubDate>
    </item>
    <item>
      <title>Guidelines for effective TFS comments.</title>
      <description>Guidelines for writing effective TFS comments. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fphilosophil.spaces.live.com%2fblog%2fcns!7E55D8EFA2AEE5D6!158.entry"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fphilosophil.spaces.live.com%2fblog%2fcns!7E55D8EFA2AEE5D6!158.entry" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/teamsystem/Guidelines_for_effective_TFS_comments</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/teamsystem/Guidelines_for_effective_TFS_comments</guid>
      <pubDate>Mon, 14 Jul 2008 19:30:12 GMT</pubDate>
    </item>
    <item>
      <title>Unit test guidelines Part 1 to 5</title>
      <description>A multi-part article on how to properly write unit tests. It discusses when unit tests should be used in the application life cycle, what it looks like, what are the different ways to approach unit testing (black box, white box, behavior drivent testing, interaction based testing, etc.) , how to mock,  what not to test and finally a list of guidelines which summarize what to do and what not to do. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fphilosophil.spaces.live.com%2fblog%2fcns!7E55D8EFA2AEE5D6!150.entry"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fphilosophil.spaces.live.com%2fblog%2fcns!7E55D8EFA2AEE5D6!150.entry" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Unit_test_guidelines_Part_1_to_5</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Unit_test_guidelines_Part_1_to_5</guid>
      <pubDate>Mon, 26 May 2008 18:38:06 GMT</pubDate>
    </item>
  </channel>
</rss>