<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Selling colleagues on progressive enhancement</title>
	<atom:link href="http://www.pathf.com/blogs/2008/06/selling-colleagues-on-progressive-enhancement/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2008/06/selling-colleagues-on-progressive-enhancement/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<lastBuildDate>Fri, 05 Mar 2010 19:33:43 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Andreas Stephan</title>
		<link>http://www.pathf.com/blogs/2008/06/selling-colleagues-on-progressive-enhancement/comment-page-1/#comment-2196</link>
		<dc:creator>Andreas Stephan</dc:creator>
		<pubDate>Tue, 24 Jun 2008 09:34:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=982#comment-2196</guid>
		<description>Way to go! That&#039;s exactly how I feel it should be done. Not that a RoR programmer needs to know every single browser quirk, neither does a frontend developer have to know how to solve a complicated Active Record issue, but they both should have more than a general understanding of what the other person is doing and should be able to jump in on medium tasks. This leads to better code, more considerations on software design, accessibility and web standards, and also helps a lot if team members leave the team. Im sure your new workflow will be a huge success.</description>
		<content:encoded><![CDATA[<p>Way to go! That&#8217;s exactly how I feel it should be done. Not that a RoR programmer needs to know every single browser quirk, neither does a frontend developer have to know how to solve a complicated Active Record issue, but they both should have more than a general understanding of what the other person is doing and should be able to jump in on medium tasks. This leads to better code, more considerations on software design, accessibility and web standards, and also helps a lot if team members leave the team. Im sure your new workflow will be a huge success.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.270 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-03-19 12:01:33 -->
