<?xml version="1.0" encoding="UTF-8"?>







<rss version="2.0">
<channel>
  <title>Just My Thoughts</title>
  <link>http://radio.javaranch.com/ilja/</link>
  <description>Ilja on Software Development and more...</description>
  <language>en</language>
  <copyright>Ilja Preuss</copyright>
  <lastBuildDate>Sun, 09 Mar 2008 18:54:15 GMT</lastBuildDate>
  <generator>Pebble</generator>
  <docs>http://backend.userland.com/rss</docs>
  <image>
    <url>http://pebble.sourceforge.net/common/images/powered-by-pebble.gif</url>
    <title>Just My Thoughts</title>
    <link>http://radio.javaranch.com/ilja/</link>
  </image>
  
  <item>
    <title>A Lightweight Appreciative Retrospection</title>
    <link>http://radio.javaranch.com/ilja/2008/03/09/1205088855539.html</link>
    
      
      
        <description>
          In December last year, our team had to meet a challenging business goal, and to meet it we changed quite a lot of our process. As the end of the year came close, we felt the desire to have some kind of reflection. We didn&#039;t feel the need for a fully fledged retrospective, though - instead, we wanted something lightweight and fun - and preferably something appreciative. I decided to try a variation of the Like To Like exercise as the main part. Here is how it went.&lt;/p&gt;
          &lt;p&gt;&lt;a href="http://radio.javaranch.com/ilja/2008/03/09/1205088855539.html"&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <comments>http://radio.javaranch.com/ilja/2008/03/09/1205088855539.html#comments</comments>
    <guid isPermaLink="true">http://radio.javaranch.com/ilja/2008/03/09/1205088855539.html</guid>
    <pubDate>Sun, 09 Mar 2008 18:54:15 GMT</pubDate>
  </item>
  
  <item>
    <title>You *Are* Gonna Need A Good Design</title>
    <link>http://radio.javaranch.com/ilja/2008/02/27/1204145190205.html</link>
    
      
        <description>
          &lt;p&gt;
&#034;You ain&#039;t gonna need it!&#034; (short YAGNI) is one of the most popular, and probably also most misunderstood and misused mantras of Extreme Programming. Again and again I see it used as an excuse to not improve a design &#034;because it already works&#034;.
&lt;/p&gt;

&lt;p&gt;I guess the following has already been stated in hundreds of places on the web and elsewhere, in some form or another - on the other hand I also think it can&#039;t be said too often:&lt;/p&gt;

&lt;P&gt;&lt;B&gt;YAGNI applies to functionality, not design.&lt;/B&gt; All Agile approaches I know of are quite adamant about the fact that &lt;B&gt;you need a clean, well decoupled, cohesive, duplication-free, expressive and extensively tested design&lt;/b&gt; from the beginning. One that is optimized for the currently implemented (and needed) functionality.&lt;/p&gt;
        </description>
      
      
    
    
    
    <comments>http://radio.javaranch.com/ilja/2008/02/27/1204145190205.html#comments</comments>
    <guid isPermaLink="true">http://radio.javaranch.com/ilja/2008/02/27/1204145190205.html</guid>
    <pubDate>Wed, 27 Feb 2008 20:46:30 GMT</pubDate>
  </item>
  
  </channel>
</rss>
