<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xml" href="http://www.dzone.com/links/misc/rss.xsl"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dz="http://www.developerzone.com/modules/dz/1.0" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>DZone: queued links: methodology</title>
    <link>http://www.dzone.com/links/queue/tag/methodology.html</link>
    <description>DZone: fresh links for developers</description>
    <language>en-us</language>
    <copyright>Copyright (c) 2006 DZone, Inc.</copyright>
    <pubDate>Sat, 05 Jul 2008 03:28:34 GMT</pubDate>
    <dc:creator>The DZone community</dc:creator>
    <dc:date>2008-07-05T03:28:34Z</dc:date>
    <dc:language>en-us</dc:language>
    <dc:rights>Copyright (c) 2006 DZone, Inc.</dc:rights>
    <dz:selfLink>http://www.dzone.com/links/feed/queue/methodology/rss.xml</dz:selfLink>
    <image>
      <title>DZone: fresh links for developers</title>
      <url>http://www.dzone.com/images/std/dzone.com_258x55.gif</url>
      <link>http://www.dzone.com/links/</link>
    </image>
    <item>
      <title>Domain Driven Design and Development In Practice - Article</title>
      <link>http://www.dzone.com/links/rss/domain_driven_design_and_development_in_practice_2.html</link>
      <description>Domain Driven Design (DDD) is about mapping business domain concepts into software artifacts. Most of the writings and articles on this topic have been based on Eric Evans' book "Domain Driven Design", covering the domain modeling and design aspects mainly from a conceptual and design stand-point. This article looks at the guidelines, best practices frameworks and tools that technical leads and architects can use in the implementation effort.</description>
      <category>frameworks</category>
      <category>java</category>
      <category>methodology</category>
      <category>tools</category>
      <pubDate>Fri, 04 Jul 2008 22:12:48 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/92666.html</guid>
      <dc:creator>srinipenchikala</dc:creator>
      <dc:date>2008-07-04T22:12:48Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/domain_driven_design_and_development_in_practice_2.html'><img src='http://www.dzone.com/links/images/thumbs/120x90/92666.jpg' style='width:120;height:90;margin:6;float:left;vertical-align:top;border:1px solid #ccc;' /></a> Domain Driven Design (DDD) is about mapping business domain concepts into software artifacts. Most of the writings and articles on this topic have been based on Eric Evans' book "Domain Driven Design", covering the domain modeling and design aspects mainly from a conceptual and design stand-point. This article looks at the guidelines, best practices frameworks and tools that technical leads and architects can use in the implementation effort.]]></content:encoded>
      <dz:linkId>92666</dz:linkId>
      <dz:submitDate>2008-07-04T22:12:48Z</dz:submitDate>
      <dz:voteUpCount>2</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>6</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/92666.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>srinipenchikala</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/76906.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Scrum &amp; Football  Analogy</title>
      <link>http://www.dzone.com/links/rss/scrum_football_analogy.html</link>
      <description>A summary of the similarities in Agile methodology SCRUM and the American Football sport and the aspects of Scrum and Football that are very analogous in nature.</description>
      <category>methodology</category>
      <category>trends</category>
      <pubDate>Fri, 04 Jul 2008 22:00:00 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/92665.html</guid>
      <dc:creator>srinipenchikala</dc:creator>
      <dc:date>2008-07-04T22:00:00Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/scrum_football_analogy.html'><img src='http://www.dzone.com/links/images/thumbs/120x90/92665.jpg' style='width:120;height:90;margin:6;float:left;vertical-align:top;border:1px solid #ccc;' /></a> A summary of the similarities in Agile methodology SCRUM and the American Football sport and the aspects of Scrum and Football that are very analogous in nature.]]></content:encoded>
      <dz:linkId>92665</dz:linkId>
      <dz:submitDate>2008-07-04T22:00:00Z</dz:submitDate>
      <dz:voteUpCount>3</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>5</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/92665.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>srinipenchikala</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/76906.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Agile Content is the Goal</title>
      <link>http://www.dzone.com/links/rss/agile_content_is_the_goal.html</link>
      <description>It’s suggested that the web has changed everything.  Whatever requirements there were for delivering desktop applications, the requirements for delivering web applications has changed.   For the web, the thinking goes; delivery of new features to customers is paramount to remain competitive.   Maybe it’s true, but what’s the evidence?  My own experience with popular web sites does not support this conclusion.</description>
      <category>methodology</category>
      <category>reviews</category>
      <pubDate>Fri, 04 Jul 2008 17:20:24 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/92615.html</guid>
      <dc:creator>mswatcher</dc:creator>
      <dc:date>2008-07-04T17:20:24Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/agile_content_is_the_goal.html'><img src='http://www.dzone.com/links/images/thumbs/120x90/92615.jpg' style='width:120;height:90;margin:6;float:left;vertical-align:top;border:1px solid #ccc;' /></a> It’s suggested that the web has changed everything.  Whatever requirements there were for delivering desktop applications, the requirements for delivering web applications has changed.   For the web, the thinking goes; delivery of new features to customers is paramount to remain competitive.   Maybe it’s true, but what’s the evidence?  My own experience with popular web sites does not support this conclusion.]]></content:encoded>
      <dz:linkId>92615</dz:linkId>
      <dz:submitDate>2008-07-04T17:20:24Z</dz:submitDate>
      <dz:voteUpCount>2</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>4</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/92615.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>mswatcher</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/225256.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Test code is "First class code"</title>
      <link>http://www.dzone.com/links/rss/test_code_is_first_class_code.html</link>
      <description>I believe that one of the worst mistake a developer can do when writing Unit Tests is to consider unit test “second class code”, in the end the test code does not goes into production (pay attention to the smell test logic in production) so it does not worth to spend too much time with Test Code.</description>
      <category>methodology</category>
      <category>reviews</category>
      <pubDate>Fri, 04 Jul 2008 17:08:33 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/92610.html</guid>
      <dc:creator>mswatcher</dc:creator>
      <dc:date>2008-07-04T17:08:33Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/test_code_is_first_class_code.html'><img src='http://www.dzone.com/links/images/thumbs/120x90/92610.jpg' style='width:120;height:90;margin:6;float:left;vertical-align:top;border:1px solid #ccc;' /></a> I believe that one of the worst mistake a developer can do when writing Unit Tests is to consider unit test “second class code”, in the end the test code does not goes into production (pay attention to the smell test logic in production) so it does not worth to spend too much time with Test Code.]]></content:encoded>
      <dz:linkId>92610</dz:linkId>
      <dz:submitDate>2008-07-04T17:08:33Z</dz:submitDate>
      <dz:voteUpCount>2</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>2</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/92610.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>mswatcher</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/225256.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>What is “Defensive Programming”?</title>
      <link>http://www.dzone.com/links/rss/what_is_defensive_programming.html</link>
      <description>My post on the Null Object pattern has generated some interesting dialog. One of the trends that I have seen is the idea that defensive programming means your code should fail as early as possible. I couldn’t agree less.</description>
      <category>.net</category>
      <category>methodology</category>
      <pubDate>Fri, 04 Jul 2008 17:04:24 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/92608.html</guid>
      <dc:creator>mswatcher</dc:creator>
      <dc:date>2008-07-04T17:04:24Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/what_is_defensive_programming.html'><img src='http://www.dzone.com/links/images/thumbs/120x90/92608.jpg' style='width:120;height:90;margin:6;float:left;vertical-align:top;border:1px solid #ccc;' /></a> My post on the Null Object pattern has generated some interesting dialog. One of the trends that I have seen is the idea that defensive programming means your code should fail as early as possible. I couldn’t agree less.]]></content:encoded>
      <dz:linkId>92608</dz:linkId>
      <dz:submitDate>2008-07-04T17:04:24Z</dz:submitDate>
      <dz:voteUpCount>1</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>9</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/92608.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>mswatcher</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/225256.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Three Ways to Bind a DropDownList with LINQ and C# ASP .NET</title>
      <link>http://www.dzone.com/links/rss/three_ways_to_bind_a_dropdownlist_with_linq_and_c.html</link>
      <description>With the latest release of C# ASP .NET 3.5, Visual Studio 2008, and LINQ, there is a whole new way of working with the data layer in C# ASP .NET web applications. Prior to LINQ, many developers would either generate or custom-code a data layer based upon the usage of SqlConnection, SqlCommand, and DataReader objects to manipulate data.</description>
      <category>.net</category>
      <category>database</category>
      <category>methodology</category>
      <category>other languages</category>
      <pubDate>Fri, 04 Jul 2008 16:33:07 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/92596.html</guid>
      <dc:creator>mswatcher</dc:creator>
      <dc:date>2008-07-04T16:33:07Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/three_ways_to_bind_a_dropdownlist_with_linq_and_c.html'><img src='http://www.dzone.com/links/images/thumbs/120x90/92596.jpg' style='width:120;height:90;margin:6;float:left;vertical-align:top;border:1px solid #ccc;' /></a> With the latest release of C# ASP .NET 3.5, Visual Studio 2008, and LINQ, there is a whole new way of working with the data layer in C# ASP .NET web applications. Prior to LINQ, many developers would either generate or custom-code a data layer based upon the usage of SqlConnection, SqlCommand, and DataReader objects to manipulate data.]]></content:encoded>
      <dz:linkId>92596</dz:linkId>
      <dz:submitDate>2008-07-04T16:33:07Z</dz:submitDate>
      <dz:voteUpCount>2</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>0</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/92596.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>mswatcher</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/225256.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Are Bad Tests Worse Than No Tests At All?</title>
      <link>http://www.dzone.com/links/rss/are_bad_tests_worse_than_no_tests_at_all.html</link>
      <description>Can you write a test that does more harm than good? In the intro to his upcoming book The Art of Unit Testing, Roy Osherove describes a case where poorly-designed tests actually hurt his team's progress:</description>
      <category>java</category>
      <category>methodology</category>
      <pubDate>Fri, 04 Jul 2008 10:40:21 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/92530.html</guid>
      <dc:creator>jsugrue</dc:creator>
      <dc:date>2008-07-04T10:40:21Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/are_bad_tests_worse_than_no_tests_at_all.html'><img src='http://www.dzone.com/links/images/thumbs/120x90/92530.jpg' style='width:120;height:90;margin:6;float:left;vertical-align:top;border:1px solid #ccc;' /></a> Can you write a test that does more harm than good? In the intro to his upcoming book The Art of Unit Testing, Roy Osherove describes a case where poorly-designed tests actually hurt his team's progress:]]></content:encoded>
      <dz:linkId>92530</dz:linkId>
      <dz:submitDate>2008-07-04T10:40:21Z</dz:submitDate>
      <dz:voteUpCount>4</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>10</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/92530.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>jsugrue</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/185351.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Six valuable Phing build file refactorings</title>
      <link>http://www.dzone.com/links/rss/six_valuable_phing_build_file_refactorings.html</link>
      <description>Some weeks months ago I finally got my hands on the ThoughtWorks Anthology and got immediately hooked on one of the featured essays called 'Refactoring Ant Build Files' contributed by Julian Simpson aka the build doctor. After absorbing and studying the provided catalogue of overall 24 refactorings, I spent some time to transform a few health-promoting ones to the Phing universe. So the following post will outline six five basic, but valuable Phing build file refactorings by showing the smelly example first, followed by the scentless one and a closing refactoring description.</description>
      <category>how-to</category>
      <category>methodology</category>
      <category>php</category>
      <category>tools</category>
      <pubDate>Thu, 03 Jul 2008 23:55:21 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/92434.html</guid>
      <dc:creator>raphael76</dc:creator>
      <dc:date>2008-07-03T23:55:21Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/six_valuable_phing_build_file_refactorings.html'><img src='http://www.dzone.com/links/images/thumbs/120x90/92434.jpg' style='width:120;height:90;margin:6;float:left;vertical-align:top;border:1px solid #ccc;' /></a> Some weeks months ago I finally got my hands on the ThoughtWorks Anthology and got immediately hooked on one of the featured essays called 'Refactoring Ant Build Files' contributed by Julian Simpson aka the build doctor. After absorbing and studying the provided catalogue of overall 24 refactorings, I spent some time to transform a few health-promoting ones to the Phing universe. So the following post will outline six five basic, but valuable Phing build file refactorings by showing the smelly example first, followed by the scentless one and a closing refactoring description.]]></content:encoded>
      <dz:linkId>92434</dz:linkId>
      <dz:submitDate>2008-07-03T23:55:21Z</dz:submitDate>
      <dz:voteUpCount>3</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>10</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/92434.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>raphael76</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/228496.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Scaling Continuous Integration With Multi-Stage Continuous Integration</title>
      <link>http://www.dzone.com/links/rss/scaling_continuous_integration_with_multistage_co.html</link>
      <description>Continuous Integration has a dark side. When it is combined with the practice of mainline development, especially for a large development effort, it can turn into “Continuous Noise.” In this case, you get notified every 10 minutes or so (depending on how much building and testing is going on) that the build and/or test suite is still failing. Multi-Stage CI can help!</description>
      <category>how-to</category>
      <category>methodology</category>
      <pubDate>Thu, 03 Jul 2008 23:52:04 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/92433.html</guid>
      <dc:creator>damonpoole</dc:creator>
      <dc:date>2008-07-03T23:52:04Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/scaling_continuous_integration_with_multistage_co.html'><img src='http://www.dzone.com/links/images/thumbs/120x90/92433.jpg' style='width:120;height:90;margin:6;float:left;vertical-align:top;border:1px solid #ccc;' /></a> Continuous Integration has a dark side. When it is combined with the practice of mainline development, especially for a large development effort, it can turn into “Continuous Noise.” In this case, you get notified every 10 minutes or so (depending on how much building and testing is going on) that the build and/or test suite is still failing. Multi-Stage CI can help!]]></content:encoded>
      <dz:linkId>92433</dz:linkId>
      <dz:submitDate>2008-07-03T23:52:04Z</dz:submitDate>
      <dz:voteUpCount>4</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>10</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/92433.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>damonpoole</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/283687.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>Ideas for testing Zend Framework apps</title>
      <link>http://www.dzone.com/links/rss/ideas_for_testing_zend_framework_apps.html</link>
      <description>Jani Hartikainen provides are some ideas he was thinking of for making testing Zend Framework (and Doctrine) based apps nice and easy.</description>
      <category>frameworks</category>
      <category>methodology</category>
      <category>opinion</category>
      <category>php</category>
      <pubDate>Thu, 03 Jul 2008 21:43:10 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/92423.html</guid>
      <dc:creator>raphael76</dc:creator>
      <dc:date>2008-07-03T21:43:10Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/ideas_for_testing_zend_framework_apps.html'><img src='http://www.dzone.com/links/images/thumbs/120x90/92423.jpg' style='width:120;height:90;margin:6;float:left;vertical-align:top;border:1px solid #ccc;' /></a> Jani Hartikainen provides are some ideas he was thinking of for making testing Zend Framework (and Doctrine) based apps nice and easy.]]></content:encoded>
      <dz:linkId>92423</dz:linkId>
      <dz:submitDate>2008-07-03T21:43:10Z</dz:submitDate>
      <dz:voteUpCount>3</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>13</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/92423.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>raphael76</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/228496.gif</dz:userimage>
      </dz:submitter>
    </item>
    <item>
      <title>LINQ Farm: Lambdas</title>
      <link>http://www.dzone.com/links/rss/linq_farm_lambdas.html</link>
      <description>Lambdas are a simple technology with an intimidating name. They sound like they are going to be difficult to understand, but in practice prove to be relatively trivial. &#xD;
LINQ has an almost inordinate need for its users to declare a large number of small, simple delegates. The architects of C# decided that forcing the users of LINQ to declare delegates using standard C# 2.0 delegate syntax was an overly verbose option. They wanted to find a shorter, more concise way to accomplish the same task.</description>
      <category>.net</category>
      <category>database</category>
      <category>methodology</category>
      <pubDate>Thu, 03 Jul 2008 05:35:02 GMT</pubDate>
      <guid isPermaLink="false">http://www.dzone.com/links/92215.html</guid>
      <dc:creator>mswatcher</dc:creator>
      <dc:date>2008-07-03T05:35:02Z</dc:date>
      <content:encoded><![CDATA[<a href='http://www.dzone.com/links/rss/linq_farm_lambdas.html'><img src='http://www.dzone.com/links/images/thumbs/120x90/92215.jpg' style='width:120;height:90;margin:6;float:left;vertical-align:top;border:1px solid #ccc;' /></a> Lambdas are a simple technology with an intimidating name. They sound like they are going to be difficult to understand, but in practice prove to be relatively trivial. 
LINQ has an almost inordinate need for its users to declare a large number of small, simple delegates. The architects of C# decided that forcing the users of LINQ to declare delegates using standard C# 2.0 delegate syntax was an overly verbose option. They wanted to find a shorter, more concise way to accomplish the same task.]]></content:encoded>
      <dz:linkId>92215</dz:linkId>
      <dz:submitDate>2008-07-03T05:35:02Z</dz:submitDate>
      <dz:voteUpCount>2</dz:voteUpCount>
      <dz:voteDownCount>0</dz:voteDownCount>
      <dz:clickCount>11</dz:clickCount>
      <dz:commentCount>0</dz:commentCount>
      <dz:thumbnail>http://www.dzone.com/links/images/thumbs/120x90/92215.jpg</dz:thumbnail>
      <dz:submitter>
        <dz:username>mswatcher</dz:username>
        <dz:userimage>http://www.dzone.com/links/images/avatars/225256.gif</dz:userimage>
      </dz:submitter>
    </item>
  </channel>
</rss>

