<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com : Stories kicked by changer</title>
    <description>Stories kicked by changer</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>Microsoft Volta - oh my oh my</title>
      <description>Microsoft uses the &amp;quot;live labs&amp;quot; to release all sorts of test balloons. Sometimes we get really nifty stuff like Photosynth or SeaDragon. Unfortunately, sometimes we get not so bright ideas like Volta. here is why.. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2007%2f12%2f06%2fMicrosoftVoltaOhMyOhMy.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2007%2f12%2f06%2fMicrosoftVoltaOhMyOhMy.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/architecture/Microsoft_Volta_oh_my_oh_my</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/architecture/Microsoft_Volta_oh_my_oh_my</guid>
      <pubDate>Fri, 21 Dec 2007 04:31:04 GMT</pubDate>
    </item>
    <item>
      <title>Information Radiators: Make life visible</title>
      <description>A couple of people have asked me how we track our work for our iterations. We basically use a somewhat simple information radiator.

Information radiators serve to quickly give everyone on the project team a quick indication on what needs to be done, what is being worked on, and what has been done.

Information radiators can be as a simple as a few cards on a cork board to huge 54" plasma displays. It's up your team to determine what works best.  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.lostechies.com%2fblogs%2fjoe_ocampo%2farchive%2f2007%2f12%2f08%2finformation-radiators-make-life-visible.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.lostechies.com%2fblogs%2fjoe_ocampo%2farchive%2f2007%2f12%2f08%2finformation-radiators-make-life-visible.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/community/Information_Radiators_Make_life_visible</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/community/Information_Radiators_Make_life_visible</guid>
      <pubDate>Sat, 08 Dec 2007 22:42:07 GMT</pubDate>
    </item>
    <item>
      <title>The .NET/Java architect training program</title>
      <description>A side effect of my decision not to become an independent consultant at this time means that I have to shelve some of the projects I was considering. One of these projects was to create a training program for software architects. Since It seems I am not going to promote it, I thought I'd share what I think a training program for .NET/Java architects should look like in the hope that someone would find it useful and do promote it (or parts of it)
 &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2007%2f09%2f29%2fTheNETJavaArchitectTrainingProgram.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2007%2f09%2f29%2fTheNETJavaArchitectTrainingProgram.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/architecture/The_NET_Java_architect_training_program</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/architecture/The_NET_Java_architect_training_program</guid>
      <pubDate>Sat, 29 Sep 2007 00:16:58 GMT</pubDate>
    </item>
    <item>
      <title>Ancient Scrolls of Wisdom</title>
      <description>What we can learn from software engineering books that are more than a decade old (like mythical man-month, peopleware etc.) &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2007%2f09%2f14%2fAncientScrollsOfWisdom.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2007%2f09%2f14%2fAncientScrollsOfWisdom.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/Ancient_Scrolls_of_Wisdom</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/Ancient_Scrolls_of_Wisdom</guid>
      <pubDate>Wed, 19 Sep 2007 15:26:53 GMT</pubDate>
    </item>
    <item>
      <title>WAKA - A little REST and Relaxation in November?</title>
      <description>If there's one reason to go to ApacheCon 07 in Atlanta, then it's probably Roy T. Fielding's &amp;quot;a little REST and Relaxation&amp;quot;
While there isn't a whole lot of information available  on WAKA  (that replacement for HTTP Roy mentions in the end of the abstract). Belwo are a few links I managed to find..

 &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2007%2f09%2f15%2fWAKAALittleRESTAndRelaxationInNovember.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2007%2f09%2f15%2fWAKAALittleRESTAndRelaxationInNovember.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/architecture/WAKA_A_little_REST_and_Relaxation_in_November</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/architecture/WAKA_A_little_REST_and_Relaxation_in_November</guid>
      <pubDate>Mon, 17 Sep 2007 13:51:56 GMT</pubDate>
    </item>
    <item>
      <title>FTP Must Die</title>
      <description>&amp;quot;FTP is an outdated, insecure, slow, unfriendly pig of a protocol. It's got no business being on the Internet in the 21st century.&amp;quot; &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwooledge.org%2fmywiki%2fFtpMustDie"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwooledge.org%2fmywiki%2fFtpMustDie" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/FTP_Must_Die</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/FTP_Must_Die</guid>
      <pubDate>Mon, 17 Sep 2007 16:00:54 GMT</pubDate>
    </item>
    <item>
      <title>REST and the magic of scalability idempotence and whatnot</title>
      <description>From time to time I read about the magic that is RESTful services and how they solve everything and anything like scalability, idempotency, simplicity etc.

I think such claims  are plainly wrong and misleading. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2007%2f09%2f12%2fRESTAndTheMagicOfScalabilityIdempotenceAndWhatnot.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2007%2f09%2f12%2fRESTAndTheMagicOfScalabilityIdempotenceAndWhatnot.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/webservices/REST_and_the_magic_of_scalability_idempotence_and_whatnot</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/webservices/REST_and_the_magic_of_scalability_idempotence_and_whatnot</guid>
      <pubDate>Fri, 14 Sep 2007 11:41:27 GMT</pubDate>
    </item>
    <item>
      <title>The Ruby Connector : Free .NET to Ruby Control</title>
      <description>The Ruby Connector is a drag-and-drop control which enables .NET programs to communicate with Ruby programs. Using the Ruby Connector, you can: 
- Create visual front-ends to Ruby programs using the Visual Studio form designer. 
- Interact with the Ruby interpreter in your own applications in much the same way as you can interact with the Ruby Console in Ruby In Steel. 
- Start or stop the Ruby interpreter at will and pass expressions from your .NET program to be evaluated by Ruby. 
- Create 'hybrid' applications in which a .NET program runs simultaneously with a Ruby program and data is exchanged from one to the other &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.sapphiresteel.com%2fSapphireSteel-Downloads"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.sapphiresteel.com%2fSapphireSteel-Downloads" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/winforms/The_Ruby_Connector_Free_NET_to_Ruby_Control</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/winforms/The_Ruby_Connector_Free_NET_to_Ruby_Control</guid>
      <pubDate>Thu, 13 Sep 2007 09:25:35 GMT</pubDate>
    </item>
  </channel>
</rss>