<?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: There Are No Standards</title>
	<atom:link href="http://www.allaboutbalance.com/there-are-no-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allaboutbalance.com/there-are-no-standards/</link>
	<description>On Usability, Agility and Technology</description>
	<lastBuildDate>Thu, 15 Jul 2010 15:23:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Svend Tofte</title>
		<link>http://www.allaboutbalance.com/there-are-no-standards/comment-page-1/#comment-167</link>
		<dc:creator>Svend Tofte</dc:creator>
		<pubDate>Mon, 21 Jul 2008 22:31:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.allaboutbalance.com/index.php/there-are-no-standards/#comment-167</guid>
		<description>I think alot of these issues stems from the training programmers go through. We (*cough*) tend to focus on the main case. We make sure outlier cases do not crash the applications, but should such cases appear, we don&#039;t really bother to &quot;nice&quot; it up. 

Probably the most trivial example if some search result listing, since the &quot;results&quot; is a fixed string.

&quot;1 results&quot; (note the plural)
&quot;1 result(s)&quot; (looks even worse to me)
&quot;2 result&quot; (again pretty bad)

Instead of spending 10 minutes covering the different cases, a programmer is just going to think &quot;most searches are not going to be 1 result searches, so using the string &#039;results&#039; will work well&quot;

Same reasoning and sloppy Q&amp;A allows blemishes such as the ones you list to slip through. It&#039;s easy to imagine the sort dropdown as being a constant on pages. It &quot;looks&quot; handy, but it can only sort on properties ALL products share (such as &quot;brand&quot;, etc), and thus becomes useless when you wish to sort on something even a tiny bit more specific, because binding the sort dialog to these specific sub-category properties is obviously going to be more complex.

Usually a good combination of programmer inattention, and budget ensures that usability people will never run out of things to write about :)</description>
		<content:encoded><![CDATA[<p>I think alot of these issues stems from the training programmers go through. We (*cough*) tend to focus on the main case. We make sure outlier cases do not crash the applications, but should such cases appear, we don&#8217;t really bother to &#8220;nice&#8221; it up. </p>
<p>Probably the most trivial example if some search result listing, since the &#8220;results&#8221; is a fixed string.</p>
<p>&#8220;1 results&#8221; (note the plural)<br />
&#8220;1 result(s)&#8221; (looks even worse to me)<br />
&#8220;2 result&#8221; (again pretty bad)</p>
<p>Instead of spending 10 minutes covering the different cases, a programmer is just going to think &#8220;most searches are not going to be 1 result searches, so using the string &#8216;results&#8217; will work well&#8221;</p>
<p>Same reasoning and sloppy Q&amp;A allows blemishes such as the ones you list to slip through. It&#8217;s easy to imagine the sort dropdown as being a constant on pages. It &#8220;looks&#8221; handy, but it can only sort on properties ALL products share (such as &#8220;brand&#8221;, etc), and thus becomes useless when you wish to sort on something even a tiny bit more specific, because binding the sort dialog to these specific sub-category properties is obviously going to be more complex.</p>
<p>Usually a good combination of programmer inattention, and budget ensures that usability people will never run out of things to write about :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
