<?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 Invisible Interface</title>
	<atom:link href="http://www.noodlesoft.com/blog/2008/09/29/the-invisible-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.noodlesoft.com/blog/2008/09/29/the-invisible-interface/</link>
	<description>On Mac OS X programming</description>
	<lastBuildDate>Fri, 16 Jul 2010 19:41:33 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mr_noodle</title>
		<link>http://www.noodlesoft.com/blog/2008/09/29/the-invisible-interface/comment-page-1/#comment-27382</link>
		<dc:creator>mr_noodle</dc:creator>
		<pubDate>Fri, 03 Oct 2008 22:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.noodlesoft.com/blog/?p=134#comment-27382</guid>
		<description>Hi Suresh,

You raise an interesting point but my experience indicates that things tends to go the other way. Donald Knuth&#039;s quote about premature optimization is appropriate here. Interfaces create legacies. Most of the time, you can improve performance without breaking everything that uses the product. Change the interface, and you risk making users re-learn the new interface or re-tool things that use it (such as a programming API). I think it&#039;s more important to get the interface right earlier on than the efficiency.

In a future article, I&#039;ll talk more about this but there&#039;s a lot that can be done to improve performance without changing the interface. The user mostly cares about what is being done, not how your program or device does it. Those are the engineer&#039;s problems and the better interface is the one that can hide all the little bumps and ugly bits in the implementation. It&#039;s extra work but I think the mindset shouldn&#039;t be that it&#039;s a problem so much as a challenge.</description>
		<content:encoded><![CDATA[<p>Hi Suresh,</p>
<p>You raise an interesting point but my experience indicates that things tends to go the other way. Donald Knuth&#8217;s quote about premature optimization is appropriate here. Interfaces create legacies. Most of the time, you can improve performance without breaking everything that uses the product. Change the interface, and you risk making users re-learn the new interface or re-tool things that use it (such as a programming API). I think it&#8217;s more important to get the interface right earlier on than the efficiency.</p>
<p>In a future article, I&#8217;ll talk more about this but there&#8217;s a lot that can be done to improve performance without changing the interface. The user mostly cares about what is being done, not how your program or device does it. Those are the engineer&#8217;s problems and the better interface is the one that can hide all the little bumps and ugly bits in the implementation. It&#8217;s extra work but I think the mindset shouldn&#8217;t be that it&#8217;s a problem so much as a challenge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Suresh</title>
		<link>http://www.noodlesoft.com/blog/2008/09/29/the-invisible-interface/comment-page-1/#comment-27347</link>
		<dc:creator>Suresh</dc:creator>
		<pubDate>Fri, 03 Oct 2008 12:43:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.noodlesoft.com/blog/?p=134#comment-27347</guid>
		<description>Good post.My thought on this problem is like this. 
When we solve a problem through technology, do we probably not care a lot about the efficiency in the beginning, and make it a little too easy for the end user? Because, at a later point in time, we are forced to solve that problem of inefficiency, and by then we are used to very simplistic interfaces, that anything we have to do in extra, is considered a problem.
My 2 cents.</description>
		<content:encoded><![CDATA[<p>Good post.My thought on this problem is like this.<br />
When we solve a problem through technology, do we probably not care a lot about the efficiency in the beginning, and make it a little too easy for the end user? Because, at a later point in time, we are forced to solve that problem of inefficiency, and by then we are used to very simplistic interfaces, that anything we have to do in extra, is considered a problem.<br />
My 2 cents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mr_noodle</title>
		<link>http://www.noodlesoft.com/blog/2008/09/29/the-invisible-interface/comment-page-1/#comment-27281</link>
		<dc:creator>mr_noodle</dc:creator>
		<pubDate>Thu, 02 Oct 2008 18:10:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.noodlesoft.com/blog/?p=134#comment-27281</guid>
		<description>Thanks for that info. I&#039;ve seen the two button toilets in Spain and the UK. I don&#039;t remember whether or not they were in France and I have yet to go to Germany. It looks like I&#039;m going to have to make a more extensive tour of Europe&#039;s toilets.

Interesting about all the variations over there. So, if you don&#039;t stop the water, does it run indefinitely? Also, is it obvious which toilet is which when you encounter one or do you have to fiddle with it to figure it out?</description>
		<content:encoded><![CDATA[<p>Thanks for that info. I&#8217;ve seen the two button toilets in Spain and the UK. I don&#8217;t remember whether or not they were in France and I have yet to go to Germany. It looks like I&#8217;m going to have to make a more extensive tour of Europe&#8217;s toilets.</p>
<p>Interesting about all the variations over there. So, if you don&#8217;t stop the water, does it run indefinitely? Also, is it obvious which toilet is which when you encounter one or do you have to fiddle with it to figure it out?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Berle</title>
		<link>http://www.noodlesoft.com/blog/2008/09/29/the-invisible-interface/comment-page-1/#comment-27246</link>
		<dc:creator>Berle</dc:creator>
		<pubDate>Thu, 02 Oct 2008 06:56:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.noodlesoft.com/blog/?p=134#comment-27246</guid>
		<description>Most toilets in Germany have two buttons. One for flushing and a second one for stopping. Some have one button and stop flushing when you press that second time, but those tend to work more unreliable. Another variant: One button that&#039;s a kind of a toggle switch that you flip to one direction to flush. It toggles back once it&#039;s done, but you can flip back sooner to stop flushing.

Seems there&#039;s a market over here for water-saving toilets. The toilet vendors are creative. 

By the way... I have never seen the variant you are describing, but hey...</description>
		<content:encoded><![CDATA[<p>Most toilets in Germany have two buttons. One for flushing and a second one for stopping. Some have one button and stop flushing when you press that second time, but those tend to work more unreliable. Another variant: One button that&#8217;s a kind of a toggle switch that you flip to one direction to flush. It toggles back once it&#8217;s done, but you can flip back sooner to stop flushing.</p>
<p>Seems there&#8217;s a market over here for water-saving toilets. The toilet vendors are creative. </p>
<p>By the way&#8230; I have never seen the variant you are describing, but hey&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mr_noodle</title>
		<link>http://www.noodlesoft.com/blog/2008/09/29/the-invisible-interface/comment-page-1/#comment-27201</link>
		<dc:creator>mr_noodle</dc:creator>
		<pubDate>Wed, 01 Oct 2008 17:50:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.noodlesoft.com/blog/?p=134#comment-27201</guid>
		<description>Well, if that&#039;s what people want, then I&#039;ll have to consider it. Personally, I&#039;m just content being able to work the words &quot;bare asses&quot; in a blog post.</description>
		<content:encoded><![CDATA[<p>Well, if that&#8217;s what people want, then I&#8217;ll have to consider it. Personally, I&#8217;m just content being able to work the words &#8220;bare asses&#8221; in a blog post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Robinson</title>
		<link>http://www.noodlesoft.com/blog/2008/09/29/the-invisible-interface/comment-page-1/#comment-27169</link>
		<dc:creator>Paul Robinson</dc:creator>
		<pubDate>Wed, 01 Oct 2008 10:42:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.noodlesoft.com/blog/?p=134#comment-27169</guid>
		<description>Great post!  

I think, for consistency, at least one toilet reference should appear in each piece in the series.....</description>
		<content:encoded><![CDATA[<p>Great post!  </p>
<p>I think, for consistency, at least one toilet reference should appear in each piece in the series&#8230;..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
