<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<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: We Need That Tomorrow</title>
	<link>http://www.rubberbandwound.com/2007/03/30/we-need-that-tomorrow/</link>
	<description>Christopher Warren on Ruby on Rails, Programming, Photography, and Life</description>
	<pubDate>Fri, 30 Jul 2010 18:36:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: brandonschauer</title>
		<link>http://www.rubberbandwound.com/2007/03/30/we-need-that-tomorrow/#comment-136</link>
		<dc:creator>brandonschauer</dc:creator>
		<pubDate>Fri, 30 Mar 2007 16:29:53 +0000</pubDate>
		<guid>http://www.rubberbandwound.com/2007/03/30/we-need-that-tomorrow/#comment-136</guid>
		<description>Interesting to hear that this topic got so stuck in your head. And you're right that the gut reaction to not even listen to the request gets more intense the closer you get to project completion.

Your post brought another thought to mind about the truly unreasonable request, e.g., "... and my daughter said we have to have a weather widget!" These certainly do happen, and sometimes there's no "best solution" for them. I think that's why I really like to develop design criteria that evolve throughout a project. Just simple statements about what you &lt;i&gt;are&lt;/i&gt; doing so you can also be clear about what you &lt;i&gt;aren't&lt;/i&gt; doing. Flickr is nice enough to &lt;a href="http://flickr.com/about/" rel="nofollow"&gt;post some of their design criteria&lt;/a&gt; right on the site. Simple statements like these can help deflect the truly dumb ideas.</description>
		<content:encoded><![CDATA[<p>Interesting to hear that this topic got so stuck in your head. And you&#8217;re right that the gut reaction to not even listen to the request gets more intense the closer you get to project completion.</p>
<p>Your post brought another thought to mind about the truly unreasonable request, e.g., &#8220;&#8230; and my daughter said we have to have a weather widget!&#8221; These certainly do happen, and sometimes there&#8217;s no &#8220;best solution&#8221; for them. I think that&#8217;s why I really like to develop design criteria that evolve throughout a project. Just simple statements about what you <i>are</i> doing so you can also be clear about what you <i>aren&#8217;t</i> doing. Flickr is nice enough to <a href="http://flickr.com/about/" rel="nofollow">post some of their design criteria</a> right on the site. Simple statements like these can help deflect the truly dumb ideas.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
