<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com - Stories tagged with Quality</title>
    <description>the latest stories tagged with 'Quality' from DotNetKicks.com</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>Improving code quality - 2 ways to go</title>
      <description>I've been thinking about this for at least a week or two. In fact, it's been since I started (and finished) reading the book "Clean Code" by Robert C. Martin. There is probably only two way to go.

 &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblog.decayingcode.com%2f2009%2f06%2fimproving-code-quality-2-ways-to-go.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblog.decayingcode.com%2f2009%2f06%2fimproving-code-quality-2-ways-to-go.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/altnet/Improving_code_quality_2_ways_to_go</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/altnet/Improving_code_quality_2_ways_to_go</guid>
      <pubDate>Mon, 22 Jun 2009 05:11:29 GMT</pubDate>
    </item>
    <item>
      <title>The Curious Case of Software Quality</title>
      <description>Keyvan writes about the current &amp;quot;principles and qualiy vs common-sense and do the quickest possible solution&amp;quot; and tries to understand why developers tend to prefer the &amp;quot;quick and dirty&amp;quot; vs the &amp;quot;clean and polished&amp;quot; solution. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fnayyeri.net%2fblog%2fthe-curious-case-of-software-quality%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fnayyeri.net%2fblog%2fthe-curious-case-of-software-quality%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/altnet/The_Curious_Case_of_Software_Quality</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/altnet/The_Curious_Case_of_Software_Quality</guid>
      <pubDate>Sun, 15 Feb 2009 03:16:53 GMT</pubDate>
    </item>
    <item>
      <title>What I want With the Web</title>
      <description>Things (very very) important on the web other than AJAX and Web 2.0 &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdreamxtream.wordpress.com%2f2008%2f07%2f08%2fwhat-i-want-with-web%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdreamxtream.wordpress.com%2f2008%2f07%2f08%2fwhat-i-want-with-web%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/What_I_want_With_the_Web</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/What_I_want_With_the_Web</guid>
      <pubDate>Mon, 11 Aug 2008 17:57:52 GMT</pubDate>
    </item>
    <item>
      <title>The devil is in the details (Visual Studio Team System test policy)</title>
      <description>What if you have a Team Project with 2 solutions in 1 team project it? How can I enforce the check-in policy to run tests from solution A only when something in solution A is checked in, tests from solution B with solution B changes, ... &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblog.maartenballiauw.be%2fpost%2f2008%2f06%2fThe-devil-is-in-the-details-Visual-Studio-Team-System-test-policy.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblog.maartenballiauw.be%2fpost%2f2008%2f06%2fThe-devil-is-in-the-details-Visual-Studio-Team-System-test-policy.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/teamsystem/The_devil_is_in_the_details_Visual_Studio_Team_System_test_policy</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/teamsystem/The_devil_is_in_the_details_Visual_Studio_Team_System_test_policy</guid>
      <pubDate>Thu, 12 Jun 2008 13:44:03 GMT</pubDate>
    </item>
    <item>
      <title>An Insurgence of Quality: The Trials of Making High-Quality Software </title>
      <description>  *  Programmers are craftsmen. As craftsmen, they work to a quality line, NOT a deadline. 
  *  Software is not industrial. It is not a product that has a direct correlation between quantity and value. 
  *  Because it is both a craft and a replicatable product, software has both elements of pre-industrial (ie craftsmanship) and post-industrial products. 
  *  Programmers do not respect authority, only ability. 
  *  There is programmer calculus: "We have two different opinions. You have one vote. I, being smarter and more well-informed, have two votes." 
  *  Programmers are quick to adapt when it makes sense.  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2ftimoni.org%2f%3fp%3d30"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2ftimoni.org%2f%3fp%3d30" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/An_Insurgence_of_Quality_The_Trials_of_Making_High_Quality_Software</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/An_Insurgence_of_Quality_The_Trials_of_Making_High_Quality_Software</guid>
      <pubDate>Sat, 07 Jun 2008 03:16:00 GMT</pubDate>
    </item>
    <item>
      <title>Detailed code metrics with NDepend</title>
      <description>A while ago, I blogged about code performance analysis in Visual Studio 2008. Using profiling and hot path tracking, I measured code performance and was able to react to that. Last week, Patrick Smacchia contacted me asking if I wanted to test his project NDepend. He promised me NDepend would provide more insight in my applications. Let's test that!  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblog.maartenballiauw.be%2fpost%2f2008%2f05%2fDetailed-code-metrics-with-NDepend.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblog.maartenballiauw.be%2fpost%2f2008%2f05%2fDetailed-code-metrics-with-NDepend.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/csharp/Detailed_code_metrics_with_NDepend</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/csharp/Detailed_code_metrics_with_NDepend</guid>
      <pubDate>Fri, 30 May 2008 16:01:12 GMT</pubDate>
    </item>
    <item>
      <title>New Team Foundation Server projects on CodePlex!</title>
      <description>There's always time to browse CodePlex! It is actually a good thing to do that from time to time. In the past few days, I spotted two great new projects on Team Foundation Server. Thumbs up for their authors!  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fblog.maartenballiauw.be%2fpost%2f2008%2f04%2fNew-Team-Foundation-Server-projects-on-CodePlex.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fblog.maartenballiauw.be%2fpost%2f2008%2f04%2fNew-Team-Foundation-Server-projects-on-CodePlex.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/teamsystem/New_Team_Foundation_Server_projects_on_CodePlex</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/teamsystem/New_Team_Foundation_Server_projects_on_CodePlex</guid>
      <pubDate>Wed, 30 Apr 2008 16:46:03 GMT</pubDate>
    </item>
    <item>
      <title>NStatic</title>
      <description>NStatic seems to be a really promising code analysis tool that goes way deeper than other tools like FxCop or ReSharper. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fformpage.de%2f2007%2f02%2f08%2fnstatic%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fformpage.de%2f2007%2f02%2f08%2fnstatic%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/architecture/NStatic</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/architecture/NStatic</guid>
      <pubDate>Tue, 13 Feb 2007 13:01:01 GMT</pubDate>
    </item>
    <item>
      <title>6 Software Tips For Hardware Makers</title>
      <description>Scott Rosenberg's recent book, Dreaming In Code suggests that software development dysfunctional. If software written by software companies is so bad, then what about software written by hardware companies? This post provides six simple tips for hardware developers to get back on track and win over customers. It doesn't have to be this bad. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fhaacked.com%2farchive%2f2007%2f01%2f14%2f6_Software_Tips_For_Hardware_Makers.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fhaacked.com%2farchive%2f2007%2f01%2f14%2f6_Software_Tips_For_Hardware_Makers.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/tipsandtricks/6_Software_Tips_For_Hardware_Makers</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/tipsandtricks/6_Software_Tips_For_Hardware_Makers</guid>
      <pubDate>Mon, 15 Jan 2007 18:16:01 GMT</pubDate>
    </item>
  </channel>
</rss>