<?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"
	>
<channel>
	<title>Comments on: Speed control designed to help the user</title>
	<atom:link href="http://architectures.danlockton.co.uk/2006/09/28/speed-control-designed-to-help-the-user/feed/" rel="self" type="application/rss+xml" />
	<link>http://architectures.danlockton.co.uk/2006/09/28/speed-control-designed-to-help-the-user/</link>
	<description>How do people use products, systems and environments?  How can designers influence interaction?  How can we design for sustainable behaviour?</description>
	<pubDate>Sat, 22 Nov 2008 22:05:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>By: Sebastien Bailard</title>
		<link>http://architectures.danlockton.co.uk/2006/09/28/speed-control-designed-to-help-the-user/#comment-9834</link>
		<dc:creator>Sebastien Bailard</dc:creator>
		<pubDate>Sat, 30 Sep 2006 03:19:31 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=125#comment-9834</guid>
		<description>I'm glad you guys mention the fact QWERTY was faster than the alternative: a jammed keyboard.

Another thing to consider is:
Why do we have keys staggered from row to row?  'E' is up and to the left from 'D', when it might be more useful to have it be directly above.
Here's a good review of one with a more rational layout:
http://www.dansdata.com/edkb.htm

There's a good write-up of Dvorak here:
http://en.wikipedia.org/wiki/Dvorak_Simplified_Keyboard

Anecdotally, Dvorak is supposed to help prevent/help with RSI, which is why I'm interested in it.  (I haven't finished learning it.)

Apparently, world record speed typists favor Dvorak as well.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad you guys mention the fact QWERTY was faster than the alternative: a jammed keyboard.</p>
<p>Another thing to consider is:<br />
Why do we have keys staggered from row to row?  &#8216;E&#8217; is up and to the left from &#8216;D&#8217;, when it might be more useful to have it be directly above.<br />
Here&#8217;s a good review of one with a more rational layout:<br />
<a href="http://www.dansdata.com/edkb.htm" rel="nofollow">http://www.dansdata.com/edkb.htm</a></p>
<p>There&#8217;s a good write-up of Dvorak here:<br />
<a href="http://en.wikipedia.org/wiki/Dvorak_Simplified_Keyboard" rel="nofollow">http://en.wikipedia.org/wiki/Dvorak_Simplified_Keyboard</a></p>
<p>Anecdotally, Dvorak is supposed to help prevent/help with RSI, which is why I&#8217;m interested in it.  (I haven&#8217;t finished learning it.)</p>
<p>Apparently, world record speed typists favor Dvorak as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://architectures.danlockton.co.uk/2006/09/28/speed-control-designed-to-help-the-user/#comment-9821</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Fri, 29 Sep 2006 20:09:28 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=125#comment-9821</guid>
		<description>Well, OK, you have a point in that it allowed the typists to type more quickly, since if the keys jammed the speed would fall to zero. 

But imagine if a jam-less keyboard could have been built before the QWERTY system had become established, then ABCDEF... would surely have been more efficient than QWERTY... - at least for novice users. Assuming they knew their alphabet, there would have been less need to hunt-and-peck, and thus a higher speed could have been achieved. Hence, &lt;em&gt;in comparison to this&lt;/em&gt;, QWERTY slowed down users, though, as you say, in a world of jamming keys, this allowed a more efficient machine, which was indeed faster than one which jammed often.</description>
		<content:encoded><![CDATA[<p>Well, OK, you have a point in that it allowed the typists to type more quickly, since if the keys jammed the speed would fall to zero. </p>
<p>But imagine if a jam-less keyboard could have been built before the QWERTY system had become established, then ABCDEF&#8230; would surely have been more efficient than QWERTY&#8230; - at least for novice users. Assuming they knew their alphabet, there would have been less need to hunt-and-peck, and thus a higher speed could have been achieved. Hence, <em>in comparison to this</em>, QWERTY slowed down users, though, as you say, in a world of jamming keys, this allowed a more efficient machine, which was indeed faster than one which jammed often.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://architectures.danlockton.co.uk/2006/09/28/speed-control-designed-to-help-the-user/#comment-9811</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Fri, 29 Sep 2006 14:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://architectures.danlockton.co.uk/?p=125#comment-9811</guid>
		<description>Even a cursory amount of research indicates that the QWERTY layout was not intended to &lt;em&gt;slow&lt;/em&gt; typists, but to allow them to type &lt;em&gt;faster&lt;/em&gt;. The layout reduced the possibility of jams, which made the machine &lt;em&gt;more&lt;/em&gt; efficient, not less.

That reason has indeed been obsoleted, but it was never to slow down users.

As you say, it's debatable whether QWERTY is a market failure; compared to DVORAK (allegedly designed for speed), the only unbiased test on record showed that there was no advantage to DVORAK.</description>
		<content:encoded><![CDATA[<p>Even a cursory amount of research indicates that the QWERTY layout was not intended to <em>slow</em> typists, but to allow them to type <em>faster</em>. The layout reduced the possibility of jams, which made the machine <em>more</em> efficient, not less.</p>
<p>That reason has indeed been obsoleted, but it was never to slow down users.</p>
<p>As you say, it&#8217;s debatable whether QWERTY is a market failure; compared to DVORAK (allegedly designed for speed), the only unbiased test on record showed that there was no advantage to DVORAK.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
