<?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: Feed(igg)back</title>
	<atom:link href="http://ycoolthing.com/archives/122/feediggback/feed" rel="self" type="application/rss+xml" />
	<link>http://ycoolthing.com/archives/122/feediggback</link>
	<description>One Cool Thing from Yahoo! every weekday</description>
	<pubDate>Mon, 06 Oct 2008 22:37:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Y! Cool Thing of the Day &#187; Blog Archive &#187; &#8220;12 Car Mashup off Hwy 101, over.&#8221;</title>
		<link>http://ycoolthing.com/archives/122/feediggback#comment-370</link>
		<dc:creator>Y! Cool Thing of the Day &#187; Blog Archive &#187; &#8220;12 Car Mashup off Hwy 101, over.&#8221;</dc:creator>
		<pubDate>Thu, 19 Oct 2006 03:35:30 +0000</pubDate>
		<guid isPermaLink="false">http://ycoolthing.com/archives/122/feediggback#comment-370</guid>
		<description>[...] Hack Days have become a big deal within the engineer culture at Yahoo!, and no group exemplifies that more than Yahoo! Autos. They&#8217;ve actually worked the concept into their regular work schedule, holding their own Hack Days every 5 or 6 weeks and allocating up to 15% of their time to devote to creating and refining hacks. As a result, you can see a fantastic number of fun ideas coming to life on the Yahoo! Autos site. [...]</description>
		<content:encoded><![CDATA[<p>[...] Hack Days have become a big deal within the engineer culture at Yahoo!, and no group exemplifies that more than Yahoo! Autos. They&#8217;ve actually worked the concept into their regular work schedule, holding their own Hack Days every 5 or 6 weeks and allocating up to 15% of their time to devote to creating and refining hacks. As a result, you can see a fantastic number of fun ideas coming to life on the Yahoo! Autos site. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
