<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Commentaires sur : Hobo : plugin Rails pour prototyper encore plus vite&#8230;</title>
	<atom:link href="http://www.balencourt.com/blog/2007/01/02/hobo-plugin-rails-pour-prototyper-encore-plus-vite/feed" rel="self" type="application/rss+xml" />
	<link>http://www.balencourt.com/blog/2007/01/02/hobo-plugin-rails-pour-prototyper-encore-plus-vite</link>
	<description>teenager then manager</description>
	<pubDate>Thu, 24 Jul 2008 09:38:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>Par : Denis</title>
		<link>http://www.balencourt.com/blog/2007/01/02/hobo-plugin-rails-pour-prototyper-encore-plus-vite#comment-527</link>
		<dc:creator>Denis</dc:creator>
		<pubDate>Fri, 05 Jan 2007 12:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.balencourt.com/blog/?p=281#comment-527</guid>
		<description>&lt;p class="denis"&gt;&lt;br/&gt;&lt;br/&gt;Hi Tom,&lt;br/&gt;&lt;br/&gt; Thanks for your comment. Indeed I can imagine that Hobo speeds up your development and i fully understand that hobo is not only a prototyping tool and that it can be used in production (by the way I'm very curious to see the  &lt;a href="http://hobocentral.net/blog/2007/01/05/putting-hobo-through-its-paces/"&gt;commercial websites you are referring to&lt;/a&gt;  when they will be ready and have some feedback about your "live" experience with Hobo). But we had a discussion about the fact that most of the time the customers can not imagine that even if a work seems finished, it's not always the case and that there is a "risk of misunderstanding" that has to be addressed by the professional developers.&lt;br/&gt;&lt;br/&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p class="denis">
<p>Hi Tom,</p>
<p> Thanks for your comment. Indeed I can imagine that Hobo speeds up your development and i fully understand that hobo is not only a prototyping tool and that it can be used in production (by the way I&#8217;m very curious to see the  <a href="http://hobocentral.net/blog/2007/01/05/putting-hobo-through-its-paces/">commercial websites you are referring to</a>  when they will be ready and have some feedback about your &#8220;live&#8221; experience with Hobo). But we had a discussion about the fact that most of the time the customers can not imagine that even if a work seems finished, it&#8217;s not always the case and that there is a &#8220;risk of misunderstanding&#8221; that has to be addressed by the professional developers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Par : Tom Locke</title>
		<link>http://www.balencourt.com/blog/2007/01/02/hobo-plugin-rails-pour-prototyper-encore-plus-vite#comment-528</link>
		<dc:creator>Tom Locke</dc:creator>
		<pubDate>Fri, 05 Jan 2007 09:29:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.balencourt.com/blog/?p=281#comment-528</guid>
		<description>&lt;p&gt;Hi - sorry to post in English. From the Google translation I think you made the point about prototypes only being 80% of the work of building the real application, and how customers can get the wrong idea.&lt;br /&gt; &lt;br /&gt; I just thought I'd mention that Hobo is not just a prototyping tool. It can be used for that, but I'm also using it with several 'real' web applications for paying customers. Hobo is giving me a dramatic speed-up in building the finished product.&lt;br /&gt; &lt;br /&gt; Thanks for your post on Hobo!&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi - sorry to post in English. From the Google translation I think you made the point about prototypes only being 80% of the work of building the real application, and how customers can get the wrong idea.</p>
<p> I just thought I&#8217;d mention that Hobo is not just a prototyping tool. It can be used for that, but I&#8217;m also using it with several &#8216;real&#8217; web applications for paying customers. Hobo is giving me a dramatic speed-up in building the finished product.</p>
<p> Thanks for your post on Hobo!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Par : SynchrO'live</title>
		<link>http://www.balencourt.com/blog/2007/01/02/hobo-plugin-rails-pour-prototyper-encore-plus-vite#comment-529</link>
		<dc:creator>SynchrO'live</dc:creator>
		<pubDate>Thu, 04 Jan 2007 22:39:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.balencourt.com/blog/?p=281#comment-529</guid>
		<description>&lt;!-- TB --&gt; &lt;p&gt;&lt;strong&gt;Un plug-in pour Ruby on rails&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;Denis nous fait part part d'un plug-in,&#160;pour Ruby on rails, Hobo, offrant une capacité de prototypage innégalée.  Lire Hobo, plug-in Rails pour prototyper encore plus vite...&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p><!-- TB -->
<p><strong>Un plug-in pour Ruby on rails</strong></p>
<p>Denis nous fait part part d&#8217;un plug-in,&nbsp;pour Ruby on rails, Hobo, offrant une capacité de prototypage innégalée.  Lire Hobo, plug-in Rails pour prototyper encore plus vite&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Par : Francois</title>
		<link>http://www.balencourt.com/blog/2007/01/02/hobo-plugin-rails-pour-prototyper-encore-plus-vite#comment-484</link>
		<dc:creator>Francois</dc:creator>
		<pubDate>Tue, 02 Jan 2007 14:36:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.balencourt.com/blog/?p=281#comment-484</guid>
		<description>&lt;p&gt;:) Comme tu le dis pour les développeurs pro, 80 à 90% du travail est invisible à l'écran. Notion qui est toujours difficile à faire passer auprès d'un client. Puisque la méthodologie de prototypage s'améliore d'un coté (avec un plugin comme celui-ci), il n'y aurait aucune raison pour ne pas trouver un argumentaire qui soit intelligible par un client. &lt;br /&gt; &lt;br /&gt; Une méthodologie plus propre mettra le client en confiance ... et donc rendra plus crédible une argumentation sur le temps nécéssaire pour assurer un développement professionnel.&lt;br /&gt; &lt;/p&gt;</description>
		<content:encoded><![CDATA[<p> <img src='http://www.balencourt.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> Comme tu le dis pour les développeurs pro, 80 à 90% du travail est invisible à l&#8217;écran. Notion qui est toujours difficile à faire passer auprès d&#8217;un client. Puisque la méthodologie de prototypage s&#8217;améliore d&#8217;un coté (avec un plugin comme celui-ci), il n&#8217;y aurait aucune raison pour ne pas trouver un argumentaire qui soit intelligible par un client. </p>
<p> Une méthodologie plus propre mettra le client en confiance &#8230; et donc rendra plus crédible une argumentation sur le temps nécéssaire pour assurer un développement professionnel.
 </p>
]]></content:encoded>
	</item>
</channel>
</rss>
