<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com : Stories kicked by danielstoner</title>
    <description>Stories kicked by danielstoner</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>Thought Driven Development a Methodology of Abile Development</title>
      <description>Warning: This is a rant against TDD extremism! Sensitive TDD people better step out of this dark sleazy communist place right now!
Why do I pick on TDD? Because it makes no sense. The development and design shall be driven by thought not by test. Yes some people are able to "think" better about their problems while using TDD. Kudos to them! But not all people are alike. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2flittletutorials.com%2f2008%2f09%2f29%2fthought-driven-development%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2flittletutorials.com%2f2008%2f09%2f29%2fthought-driven-development%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/architecture/Thought_Driven_Development_a_Methodology_of_Abile_Development</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/architecture/Thought_Driven_Development_a_Methodology_of_Abile_Development</guid>
      <pubDate>Tue, 30 Sep 2008 22:46:03 GMT</pubDate>
    </item>
    <item>
      <title>Bad advice on exceptions from Joel</title>
      <description>Starting from some comments on my exception handling series of articles I run into a couple of blogs pointing to this post on joelonsoftware.com. I think this is the worst advice on exception handling I have ever read, sorry Joel. I know this is an old post, I know Joel is entitled to his own opinion and I know he has the right to write his code as he sees fit. But as an opinion leader he influences others. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2flittletutorials.com%2f2008%2f08%2f23%2fbad-advice-on-exceptions-from-joel%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2flittletutorials.com%2f2008%2f08%2f23%2fbad-advice-on-exceptions-from-joel%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/architecture/Bad_advice_on_exceptions_from_Joel</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/architecture/Bad_advice_on_exceptions_from_Joel</guid>
      <pubDate>Sun, 24 Aug 2008 13:46:02 GMT</pubDate>
    </item>
    <item>
      <title>The Creators of 30 Programming Languages: pages, blogs, interviews</title>
      <description>Behind any programming language there is a creator or sometimes a small team. Each language has a story and a philosophy and each creator had a motivation, a problem to solve. Here is a collection of resources about these people: personal pages, blogs, biographies and interviews. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2flittletutorials.com%2f2008%2f06%2f15%2fcreators-of-programming-languages%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2flittletutorials.com%2f2008%2f06%2f15%2fcreators-of-programming-languages%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/The_Creators_of_30_Programming_Languages_pages_blogs_interviews</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/The_Creators_of_30_Programming_Languages_pages_blogs_interviews</guid>
      <pubDate>Tue, 19 Aug 2008 01:46:02 GMT</pubDate>
    </item>
    <item>
      <title>Code review - The meaningless ritual</title>
      <description>Most of the time code reviews are a meaningless ritual. Everybody pays lip service to the importance of code reviews and a lot of people, especially in the management, are convinced that code reviews very effectively reduce the number of shipped bugs.
The problem is. most developers hate code reviews and avoid them like the plague. If they can't avoid them, then they show up and act their part like in a play at the theater of the absurd. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2flittletutorials.com%2f2008%2f07%2f19%2fcode-review-the-meaningless-ritual%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2flittletutorials.com%2f2008%2f07%2f19%2fcode-review-the-meaningless-ritual%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/Code_review_The_meaningless_ritual</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/Code_review_The_meaningless_ritual</guid>
      <pubDate>Sun, 17 Aug 2008 22:46:02 GMT</pubDate>
    </item>
    <item>
      <title>12 Unit Testing Tips for Software Engineers</title>
      <description>&amp;quot;In this post we look at a dozen unit testing tips that software engineers can apply, regardless of their programming language or environment.&amp;quot; &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.readwriteweb.com%2farchives%2f12_unit_testing_tips_for_software_engineers.php"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.readwriteweb.com%2farchives%2f12_unit_testing_tips_for_software_engineers.php" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/12_Unit_Testing_Tips_for_Software_Engineers</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/12_Unit_Testing_Tips_for_Software_Engineers</guid>
      <pubDate>Fri, 15 Aug 2008 01:01:18 GMT</pubDate>
    </item>
    <item>
      <title>Software development dogmata - good practices gone bad</title>
      <description>Many practices in the software development world are widely accepted at some moment in time as the "true way". The trouble starts when the "true way" is forced down the throats of people who need a "new way". Usually popular practices follow a similar path between the moment somebody discovers/creates them and until they get massively popular. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2flittletutorials.com%2f2008%2f08%2f02%2fsoftware-development-dogmata%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2flittletutorials.com%2f2008%2f08%2f02%2fsoftware-development-dogmata%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/Software_development_dogmata_good_practices_gone_bad</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/Software_development_dogmata_good_practices_gone_bad</guid>
      <pubDate>Thu, 14 Aug 2008 22:46:03 GMT</pubDate>
    </item>
    <item>
      <title>How to run a software development company (INTO THE GROUND)</title>
      <description>The series will cover the things you *shouldn't* do if you hold some sort of managerial stake in a software project.  Sadly these tales will be from my own personal experience working for companies that have drifted into disarray.  These examples will be embellished  somewhat to drive the points home, but by and large, everything you will read in these posts will be true.  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2ftrycatchfail.com%2fblog%2fpost%2f2008%2f08%2f08%2fHow-to-run-a-software-development-company-(INTO-THE-GROUND).aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2ftrycatchfail.com%2fblog%2fpost%2f2008%2f08%2f08%2fHow-to-run-a-software-development-company-(INTO-THE-GROUND).aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/How_to_run_a_software_development_company_INTO_THE_GROUND</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/How_to_run_a_software_development_company_INTO_THE_GROUND</guid>
      <pubDate>Sun, 17 Aug 2008 02:31:02 GMT</pubDate>
    </item>
    <item>
      <title>How bad comments are born in your code</title>
      <description>Many programmers mention their support for "good" comments in the code. A significant percentage of all developers think the quality of the comments is one of the traits that separate good experienced programmers from the rest. But the cruel reality is lots of code out there is not commented at all or, even worse, it is commented but the comments are so bad they make understanding the code harder. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2flittletutorials.com%2f2008%2f07%2f30%2fhow-bad-comments-are-born-in-your-code%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2flittletutorials.com%2f2008%2f07%2f30%2fhow-bad-comments-are-born-in-your-code%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/How_bad_comments_are_born_in_your_code</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/How_bad_comments_are_born_in_your_code</guid>
      <pubDate>Mon, 11 Aug 2008 10:46:02 GMT</pubDate>
    </item>
    <item>
      <title>Top 10 Things New Twitter Users Need To Know</title>
      <description>Those new to Twitter need some guidance. Jeff Blankenburg has come up with a list of things that someone new to Twitter needs to read before even creating their account. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.jeffblankenburg.com%2f2008%2f08%2ftop-10-things-new-twitter-users-need-to.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.jeffblankenburg.com%2f2008%2f08%2ftop-10-things-new-twitter-users-need-to.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/community/Top_10_Things_New_Twitter_Users_Need_To_Know</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/community/Top_10_Things_New_Twitter_Users_Need_To_Know</guid>
      <pubDate>Sun, 10 Aug 2008 07:01:02 GMT</pubDate>
    </item>
    <item>
      <title>No, inheritance is not the way to achieve code reuse!</title>
      <description>I am not sure how so many people go through so many years of school, which is supposed to make us better at thinking, and they fail to differentiate the "why" and the "how". During interviews, when I ask their opinion about the purpose of inheritance in OOP, invariably I get this precooked answer (not so nicely expressed): inheritance is the way to achieve code reuse. No it is not! &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2flittletutorials.com%2f2008%2f06%2f23%2finheritance-not-for-code-reuse%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2flittletutorials.com%2f2008%2f06%2f23%2finheritance-not-for-code-reuse%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/architecture/No_inheritance_is_not_the_way_to_achieve_code_reuse</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/architecture/No_inheritance_is_not_the_way_to_achieve_code_reuse</guid>
      <pubDate>Sat, 09 Aug 2008 04:01:03 GMT</pubDate>
    </item>
    <item>
      <title>The Agile 800 Pounds Gorilla</title>
      <description>I woke up this morning and I was Agile. We are all Agile now. Or we are gonna become Agile. Soon. No doubt about it. It is an order. And orders are not to be discussed, just executed. The Enterprise goes Agile! With the elegance of the huge battleship being pulled across a desert between oceans by slaves, camels and elephants, the Enterprise goes Agile. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2flittletutorials.com%2f2008%2f06%2f24%2fthe-agile-800-pounds-gorilla%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2flittletutorials.com%2f2008%2f06%2f24%2fthe-agile-800-pounds-gorilla%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/The_Agile_800_Pounds_Gorilla</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/The_Agile_800_Pounds_Gorilla</guid>
      <pubDate>Sun, 10 Aug 2008 10:46:02 GMT</pubDate>
    </item>
    <item>
      <title>36 steps to success as technical lead</title>
      <description>The "tech lead" role can be treacherous at times. While the name implies "leadership", most of the times it doesn't come with implied authority like a manager role for example. It often happens that this role is in a no-man's-land where it brings a lot of responsibility but not enough formal authority. In order to successfully help a project from this position one has to navigate through narrow and convoluted straits. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2flittletutorials.com%2f2008%2f07%2f07%2fsuccess-as-technical-lead%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2flittletutorials.com%2f2008%2f07%2f07%2fsuccess-as-technical-lead%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/36_steps_to_success_as_technical_lead</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/36_steps_to_success_as_technical_lead</guid>
      <pubDate>Thu, 07 Aug 2008 00:16:20 GMT</pubDate>
    </item>
    <item>
      <title>13 reasons for UML's descent into darkness</title>
      <description>UML lost the programmers. There is no doubt about it. in my mind. And when a software design technology loses the programmers it fades away no matter what the academia thinks. This happened because UML was pushed in a direction that most code writers don't like: it started to look a lot like bureaucratic paper work. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2flittletutorials.com%2f2008%2f05%2f15%2f13-reasons-for-umls-descent-into-darkness%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2flittletutorials.com%2f2008%2f05%2f15%2f13-reasons-for-umls-descent-into-darkness%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/13_reasons_for_UML_s_descent_into_darkness</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/13_reasons_for_UML_s_descent_into_darkness</guid>
      <pubDate>Mon, 04 Aug 2008 01:01:03 GMT</pubDate>
    </item>
    <item>
      <title>Daily Standup Meetings for Agile Instructional Designers</title>
      <description>In this post, I will introduce the concept of daily standup meetings for instructional designers .  A lot has been written on this topic for agile software development.  But this agile principle can be used in any field like instructional design.  Therefore, this blog will explain the benefits, key questions and structure of a daily standup meeting. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.zachariahyoung.com%2fzy%2fpost%2f2008%2f08%2fDaily-Standup-Meetings-for-Agile-Instructional-Designers.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.zachariahyoung.com%2fzy%2fpost%2f2008%2f08%2fDaily-Standup-Meetings-for-Agile-Instructional-Designers.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/Daily_Standup_Meetings_for_Agile_Instructional_Designers</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/Daily_Standup_Meetings_for_Agile_Instructional_Designers</guid>
      <pubDate>Sun, 03 Aug 2008 04:26:03 GMT</pubDate>
    </item>
    <item>
      <title>55 Free High Quality Icon Sets</title>
      <description>A lot of freebie icons. Another great article from Smashing Magazine &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.smashingmagazine.com%2f2008%2f07%2f02%2f55-free-high-quality-icon-sets%2f"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.smashingmagazine.com%2f2008%2f07%2f02%2f55-free-high-quality-icon-sets%2f" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/tipsandtricks/55_Free_High_Quality_Icon_Sets</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/tipsandtricks/55_Free_High_Quality_Icon_Sets</guid>
      <pubDate>Mon, 07 Jul 2008 16:01:02 GMT</pubDate>
    </item>
  </channel>
</rss>