<?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: Good UI design is humble</title>
	<atom:link href="http://www.inspireux.com/2008/08/06/good-ui-design-is-humble/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.inspireux.com/2008/08/06/good-ui-design-is-humble/</link>
	<description>User Experience quotes and articles to inspire and connect the UX community</description>
	<lastBuildDate>Wed, 08 Feb 2012 10:47:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Frank Paolino</title>
		<link>http://www.inspireux.com/2008/08/06/good-ui-design-is-humble/comment-page-1/#comment-1759</link>
		<dc:creator>Frank Paolino</dc:creator>
		<pubDate>Mon, 24 Nov 2008 23:31:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.inspireux.com/?p=186#comment-1759</guid>
		<description>Wow! I read quite a few of these and this one jumped out at me. I can&#039;t tell you the number of times &quot;bad design&quot; came back as &quot;user error&quot; (or worse). I understand a designer&#039;s frustration, as generally these incidents are small, and the majority of the work is clean and useful. So these problems appear as annoyances to designers. Your approach, or mind set, is one that all developers need to have. They have to jump on these issues instead of talking. &quot;Can I leave this meeting to go work on that now&quot; is better than any excuse.</description>
		<content:encoded><![CDATA[<p>Wow! I read quite a few of these and this one jumped out at me. I can&#8217;t tell you the number of times &#8220;bad design&#8221; came back as &#8220;user error&#8221; (or worse). I understand a designer&#8217;s frustration, as generally these incidents are small, and the majority of the work is clean and useful. So these problems appear as annoyances to designers. Your approach, or mind set, is one that all developers need to have. They have to jump on these issues instead of talking. &#8220;Can I leave this meeting to go work on that now&#8221; is better than any excuse.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

