<?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: The Power of No</title>
	<atom:link href="http://www.gettheeye.com/no/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gettheeye.com/no/</link>
	<description>A series of articles about making software feel good.</description>
	<lastBuildDate>Thu, 22 Jul 2010 14:12:00 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike</title>
		<link>http://www.gettheeye.com/no/#comment-343</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 22 Jul 2010 14:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gettheeye.com/?p=1095#comment-343</guid>
		<description>Nicely written, and good points. 

It&#039;s often challenging to stop, because you just know there&#039;s so much more that would be &quot;useful.&quot; But too many choices can slow things down. Customizable toolbars is a good metaphor, I think. You can easily add or drop the tools you need. In this case, you build the tools and let the user decide.

Wrote a fairly large help system a few years ago, which became a .chm and was favorably received. That taught me a lot about keeping things simple, and providing the user with the option to link to specific, more granular information if they needed it.

Mike</description>
		<content:encoded><![CDATA[<p>Nicely written, and good points. </p>
<p>It&#8217;s often challenging to stop, because you just know there&#8217;s so much more that would be &#8220;useful.&#8221; But too many choices can slow things down. Customizable toolbars is a good metaphor, I think. You can easily add or drop the tools you need. In this case, you build the tools and let the user decide.</p>
<p>Wrote a fairly large help system a few years ago, which became a .chm and was favorably received. That taught me a lot about keeping things simple, and providing the user with the option to link to specific, more granular information if they needed it.</p>
<p>Mike</p>
]]></content:encoded>
	</item>
</channel>
</rss>
