<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>The Napkin ~ A Blog By Highgroove Studios comments on 4 Reasons to Prototype Rapidly</title>
    <link>http://napkin.highgroove.com/</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>The Napkin ~ A Blog By Highgroove Studios comments</description>
    <item>
      <title>"4 Reasons to Prototype Rapidly": comment by Geoffrey Grosenbach</title>
      <description>&lt;p&gt;I&amp;#8217;ve found this to be true for other things, too.&lt;/p&gt;


	&lt;p&gt;It&amp;#8217;s easier to edit a video if material has been recorded and can be seen live.&lt;/p&gt;


	&lt;p&gt;It&amp;#8217;s easier to refine a business if it&amp;#8217;s already operating.&lt;/p&gt;


	&lt;p&gt;And #3 sounds like the scientific method to me! Make a hypothesis, try it out, and adjust accordingly.&lt;/p&gt;</description>
      <pubDate>Thu, 26 Feb 2009 13:06:16 EST</pubDate>
      <guid>http://napkin.highgroove.com/articles/2009/02/26/4-reasons-to-prototype-rapidly#comment-1031</guid>
      <link>http://napkin.highgroove.com/articles/2009/02/26/4-reasons-to-prototype-rapidly#comment-1031</link>
    </item>
    <item>
      <title>"4 Reasons to Prototype Rapidly": comment by jasnow@hotmail.com</title>
      <description>&lt;p&gt;Similar to:
http://www.paulgraham.com/13sentences.html&lt;/p&gt;</description>
      <pubDate>Thu, 26 Feb 2009 12:22:59 EST</pubDate>
      <guid>http://napkin.highgroove.com/articles/2009/02/26/4-reasons-to-prototype-rapidly#comment-1030</guid>
      <link>http://napkin.highgroove.com/articles/2009/02/26/4-reasons-to-prototype-rapidly#comment-1030</link>
    </item>
    <item>
      <title>"4 Reasons to Prototype Rapidly" by cbq</title>
      <description>&lt;p&gt;Here are 4 reasons for prototyping applications first.  By prototyping, I mean an emphasis on building working applications rapidly:&lt;/p&gt;


	&lt;p&gt;1. It is much easier to edit an existing application that to try to dream one up with nothing visual and interactive to work with.&lt;/p&gt;


	&lt;p&gt;2. Too much planning leads to over-complication.  Sometimes you can be too smart for you own good.  &amp;#8220;What if the user wants to do X or Y.&amp;#8221;  Don&amp;#8217;t guess, find out.&lt;/p&gt;


	&lt;p&gt;3. A working application that can be tweaked beats a theoretical application that is perfect (and either sucks when it&amp;#8217;s &amp;#8220;done&amp;#8221; or never sees the light of day)&lt;/p&gt;


	&lt;p&gt;4. A Prototype forces you to focus on the core functionality, that makes or breaks your idea. Trust us, the logo is not your killer feature.&lt;/p&gt;


	&lt;p&gt;Credit is due to our good friend &lt;a href="http://www.mikelandman.com/"&gt;Mike Landman&lt;/a&gt; of &lt;a href="http://www.rippleit.com/"&gt;Ripple&lt;/a&gt; for Reasons #1 and #3.&lt;/p&gt;

</description>
      <pubDate>Thu, 26 Feb 2009 08:33:00 EST</pubDate>
      <guid>&lt;a href="/articles/2009/02/26/4-reasons-to-prototype-rapidly"&gt;4 Reasons to Prototype Rapidly&lt;/a&gt;</guid>
      <link>&lt;a href="/articles/2009/02/26/4-reasons-to-prototype-rapidly"&gt;4 Reasons to Prototype Rapidly&lt;/a&gt;</link>
    </item>
  </channel>
</rss>
