<?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>Comments on: RailsConf Keynote: Martin Fowler</title>
	<atom:link href="http://metaatem.net/2006/06/23/railsconf-keynote-martin-fowler/feed" rel="self" type="application/rss+xml" />
	<link>http://metaatem.net/2006/06/23/railsconf-keynote-martin-fowler</link>
	<description>its a mirror - get it? Erik Kastner's blog.</description>
	<pubDate>Tue, 06 Jan 2009 08:57:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: ntschutta.com &#187; Blog Archive &#187; Quick and Clean</title>
		<link>http://metaatem.net/2006/06/23/railsconf-keynote-martin-fowler#comment-1766</link>
		<dc:creator>ntschutta.com &#187; Blog Archive &#187; Quick and Clean</dc:creator>
		<pubDate>Wed, 12 Jul 2006 01:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://metaatem.net/2006/06/23/railsconf-keynote-martin-fowler#comment-1766</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>[...] 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. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The most important things I learned about Rails development from RailsConf and RailsDay at Meta &#124; ateM</title>
		<link>http://metaatem.net/2006/06/23/railsconf-keynote-martin-fowler#comment-1675</link>
		<dc:creator>The most important things I learned about Rails development from RailsConf and RailsDay at Meta &#124; ateM</dc:creator>
		<pubDate>Wed, 28 Jun 2006 14:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://metaatem.net/2006/06/23/railsconf-keynote-martin-fowler#comment-1675</guid>
		<description>[...] #. Let Rails do it&#8217;s thing and get out your way. This one was more from Martin Fowler&#8217;s keynote then anything. What Rails gives you is the ability to not worry so much about the &#8220;plumbing&#8221; of your app, and focus on what makes your problem domain interesting and unique. [...]</description>
		<content:encoded><![CDATA[<p>[...] #. Let Rails do it&#8217;s thing and get out your way. This one was more from Martin Fowler&#8217;s keynote then anything. What Rails gives you is the ability to not worry so much about the &#8220;plumbing&#8221; of your app, and focus on what makes your problem domain interesting and unique. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
