<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: RailsConf Day 2</title>
	<link>http://ntschutta.com/jat/2006/06/24/railsconf-day-2/</link>
	<description>Just A Thought...on Ajax, usability, software development and anything else that catches my fancy.</description>
	<pubDate>Fri, 05 Dec 2008 11:38:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: ntschutta.com &#187; Blog Archive &#187; Quick and Clean</title>
		<link>http://ntschutta.com/jat/2006/06/24/railsconf-day-2/#comment-4732</link>
		<dc:creator>ntschutta.com &#187; Blog Archive &#187; Quick and Clean</dc:creator>
		<pubDate>Wed, 12 Jul 2006 01:16:59 +0000</pubDate>
		<guid>http://ntschutta.com/jat/2006/06/24/railsconf-day-2/#comment-4732</guid>
		<description>[...] Alas the next day brings yet another crisis and your best laid plans are cast asunder. Day after day, we are often asked to put in quick and dirty fixes. Can it be any different? I mean we can&#8217;t possibly do quick and clean could we? Well, Obie Fernandez thinks there&#8217;s a way: Ruby and its close personal friend Rails. In a recent post about enterprise adoption (essentially expanding on his talk at RailsConf) Obie offers some great advice on how to pitch Rails to the enterprise. He hits it on the head when he says: The biggest challenge, in my opinion, is that lots of teams doing J2EE have people are used to thinking that quick == dirty. Martin&#8217;s keynote had tons of good information for anyone wanting to evangelize Ruby as enabling quick and clean solutions, and well-written Rails applications are all about quick and clean. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Alas the next day brings yet another crisis and your best laid plans are cast asunder. Day after day, we are often asked to put in quick and dirty fixes. Can it be any different? I mean we can&#8217;t possibly do quick and clean could we? Well, Obie Fernandez thinks there&#8217;s a way: Ruby and its close personal friend Rails. In a recent post about enterprise adoption (essentially expanding on his talk at RailsConf) Obie offers some great advice on how to pitch Rails to the enterprise. He hits it on the head when he says: The biggest challenge, in my opinion, is that lots of teams doing J2EE have people are used to thinking that quick == dirty. Martin&#8217;s keynote had tons of good information for anyone wanting to evangelize Ruby as enabling quick and clean solutions, and well-written Rails applications are all about quick and clean. [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
