<?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: Software design: Simple is beautiful</title>
	<atom:link href="http://compsci.ca/blog/software-design-simple-is-beautiful/feed/" rel="self" type="application/rss+xml" />
	<link>http://compsci.ca/blog/software-design-simple-is-beautiful/</link>
	<description>Programming, Education, Computer Science</description>
	<lastBuildDate>Thu, 24 Feb 2011 18:08:53 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adam</title>
		<link>http://compsci.ca/blog/software-design-simple-is-beautiful/comment-page-1/#comment-8568</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Sun, 25 Mar 2007 05:07:56 +0000</pubDate>
		<guid isPermaLink="false">http://compsci.ca/blog/software-design-simple-is-beautiful/#comment-8568</guid>
		<description>Haha, I guess that&#039;s what happens when I don&#039;t RTFA (or video)
-1 Redundant</description>
		<content:encoded><![CDATA[<p>Haha, I guess that&#8217;s what happens when I don&#8217;t RTFA (or video)<br />
-1 Redundant</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://compsci.ca/blog/software-design-simple-is-beautiful/comment-page-1/#comment-8567</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Sun, 25 Mar 2007 05:04:28 +0000</pubDate>
		<guid isPermaLink="false">http://compsci.ca/blog/software-design-simple-is-beautiful/#comment-8567</guid>
		<description>@Adam, Clayton - in the video David addressed the problem as the &lt;em&gt;&quot;SUV syndrome&quot;&lt;/em&gt; - people having a need to surround themselves with features they don&#039;t need, but might use in the distant future (probably no sooner than the next version of the software will come out).

I think the important point here is to make sure that your core features work darn well, before developing a truck-full of &quot;extras&quot; to sell the above mentioned core features.</description>
		<content:encoded><![CDATA[<p>@Adam, Clayton &#8211; in the video David addressed the problem as the <em>&#8220;SUV syndrome&#8221;</em> &#8211; people having a need to surround themselves with features they don&#8217;t need, but might use in the distant future (probably no sooner than the next version of the software will come out).</p>
<p>I think the important point here is to make sure that your core features work darn well, before developing a truck-full of &#8220;extras&#8221; to sell the above mentioned core features.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://compsci.ca/blog/software-design-simple-is-beautiful/comment-page-1/#comment-8487</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Sat, 24 Mar 2007 16:05:16 +0000</pubDate>
		<guid isPermaLink="false">http://compsci.ca/blog/software-design-simple-is-beautiful/#comment-8487</guid>
		<description>@Clayton, You add those features to give those 99% of users a feeling that they are purchasing a better product than what they had before. And to give 1% of users the chance to make older versions of Office obsolete.
I was, however, talking general terms. I don&#039;t think Office should be a prime example, simply because the vast majority of people only use it for word processing, and those &quot;features&quot; are just excuses to sell a new version.</description>
		<content:encoded><![CDATA[<p>@Clayton, You add those features to give those 99% of users a feeling that they are purchasing a better product than what they had before. And to give 1% of users the chance to make older versions of Office obsolete.<br />
I was, however, talking general terms. I don&#8217;t think Office should be a prime example, simply because the vast majority of people only use it for word processing, and those &#8220;features&#8221; are just excuses to sell a new version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clayton</title>
		<link>http://compsci.ca/blog/software-design-simple-is-beautiful/comment-page-1/#comment-8476</link>
		<dc:creator>Clayton</dc:creator>
		<pubDate>Sat, 24 Mar 2007 14:27:26 +0000</pubDate>
		<guid isPermaLink="false">http://compsci.ca/blog/software-design-simple-is-beautiful/#comment-8476</guid>
		<description>@Adam, 99% of the users out there only bought Microsoft Office to do simple word processing. They don&#039;t give a damn about any of the other crap that&#039;s in there. So why add it in?</description>
		<content:encoded><![CDATA[<p>@Adam, 99% of the users out there only bought Microsoft Office to do simple word processing. They don&#8217;t give a damn about any of the other crap that&#8217;s in there. So why add it in?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://compsci.ca/blog/software-design-simple-is-beautiful/comment-page-1/#comment-8381</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Sat, 24 Mar 2007 04:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://compsci.ca/blog/software-design-simple-is-beautiful/#comment-8381</guid>
		<description>I don&#039;t think you are forced to leave features out to make the user interface better. I think you can simply allow the basic user access to basic features, while allowing those in-the-know access to all the features of the program. 
I think that&#039;s why the &quot;Settings&#039; dialog boxes frequently have multiple tabs in them, simply because of the number of features. And really, that&#039;s the way to go. Hide features that the user doesn&#039;t normally access, but still could come in handy.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think you are forced to leave features out to make the user interface better. I think you can simply allow the basic user access to basic features, while allowing those in-the-know access to all the features of the program.<br />
I think that&#8217;s why the &#8220;Settings&#8217; dialog boxes frequently have multiple tabs in them, simply because of the number of features. And really, that&#8217;s the way to go. Hide features that the user doesn&#8217;t normally access, but still could come in handy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clayton</title>
		<link>http://compsci.ca/blog/software-design-simple-is-beautiful/comment-page-1/#comment-8276</link>
		<dc:creator>Clayton</dc:creator>
		<pubDate>Sat, 24 Mar 2007 00:04:55 +0000</pubDate>
		<guid isPermaLink="false">http://compsci.ca/blog/software-design-simple-is-beautiful/#comment-8276</guid>
		<description>I agree one hundred percent. I don&#039;t like trying to use software that is overly complicated or messy. Just to test how much worse Office got in the 2003 edition (which I have) I did the same thing you did, and mine turned out even worse. Clean, Simple, Functional. These are the things I look for when I look at software.</description>
		<content:encoded><![CDATA[<p>I agree one hundred percent. I don&#8217;t like trying to use software that is overly complicated or messy. Just to test how much worse Office got in the 2003 edition (which I have) I did the same thing you did, and mine turned out even worse. Clean, Simple, Functional. These are the things I look for when I look at software.</p>
]]></content:encoded>
	</item>
</channel>
</rss>


