<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Voice Code</title>
	<link>http://uiscape.com/2007/05/02/voice-code/</link>
	<description>Research notes on interaction design</description>
	<pubDate>Mon, 06 Oct 2008 22:46:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1</generator>

	<item>
		<title>By: pauldwaite</title>
		<link>http://uiscape.com/2007/05/02/voice-code/#comment-38</link>
		<author>pauldwaite</author>
		<pubDate>Mon, 07 May 2007 10:31:45 +0000</pubDate>
		<guid>http://uiscape.com/2007/05/02/voice-code/#comment-38</guid>
					<description>Is there any chance this would be faster than typing? If not, I'd suggest it's got zero chance of any significant use.</description>
		<content:encoded><![CDATA[<p>Is there any chance this would be faster than typing? If not, I&#8217;d suggest it&#8217;s got zero chance of any significant use.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Amar</title>
		<link>http://uiscape.com/2007/05/02/voice-code/#comment-39</link>
		<author>Amar</author>
		<pubDate>Mon, 07 May 2007 13:38:57 +0000</pubDate>
		<guid>http://uiscape.com/2007/05/02/voice-code/#comment-39</guid>
					<description>I think their main target audience seem to be programmers who suffer from RSI. I can also see this getting used by people with physical disabilities who cannot use a mouse or keyboard. There's &lt;a href="http://dx.doi.org/10.1145/1168987.1169022" title="Hubbell, Langan &#038; Hain (2006). A voice-activated syntax-directed editor for manually disabled programmers" rel="nofollow"&gt;another system&lt;/a&gt; that targets these users specifically.
Still, it would indeed be interesting to know whether it's fast enough to tempt even "manual" programmers. Unfortunately, their paper doesn't talk about this.</description>
		<content:encoded><![CDATA[<p>I think their main target audience seem to be programmers who suffer from RSI. I can also see this getting used by people with physical disabilities who cannot use a mouse or keyboard. There&#8217;s <a href="http://dx.doi.org/10.1145/1168987.1169022" title="Hubbell, Langan &#038; Hain (2006). A voice-activated syntax-directed editor for manually disabled programmers" rel="nofollow">another system</a> that targets these users specifically.<br />
Still, it would indeed be interesting to know whether it&#8217;s fast enough to tempt even &#8220;manual&#8221; programmers. Unfortunately, their paper doesn&#8217;t talk about this.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Sven Ryen</title>
		<link>http://uiscape.com/2007/05/02/voice-code/#comment-40</link>
		<author>Sven Ryen</author>
		<pubDate>Wed, 09 May 2007 20:34:31 +0000</pubDate>
		<guid>http://uiscape.com/2007/05/02/voice-code/#comment-40</guid>
					<description>On Phones runnnig Nokia S40 Series 3rd Edition, the voice recognition is quite good.  The correct name is usually picked, unless you have many similar names in your address book, like "Paul Johnsen" and "Paul Johnsted".
In that case, the programmers have been careful enough to introduce a small delay in which the user can select the correct contact from the phone menu - if he happens to be looking at his screen. 
it's to my knowledge not possible to "cancel" an outgoing call by voice commands. The headset will duly repeat the phrase the phone believes to have picked up, and then - if it has picked the wrong contact - you'll have to immediately grab for your phone to hang up the call before the wrong person answers.</description>
		<content:encoded><![CDATA[<p>On Phones runnnig Nokia S40 Series 3rd Edition, the voice recognition is quite good.  The correct name is usually picked, unless you have many similar names in your address book, like &#8220;Paul Johnsen&#8221; and &#8220;Paul Johnsted&#8221;.<br />
In that case, the programmers have been careful enough to introduce a small delay in which the user can select the correct contact from the phone menu - if he happens to be looking at his screen.<br />
it&#8217;s to my knowledge not possible to &#8220;cancel&#8221; an outgoing call by voice commands. The headset will duly repeat the phrase the phone believes to have picked up, and then - if it has picked the wrong contact - you&#8217;ll have to immediately grab for your phone to hang up the call before the wrong person answers.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Alexander</title>
		<link>http://uiscape.com/2007/05/02/voice-code/#comment-42</link>
		<author>Alexander</author>
		<pubDate>Wed, 09 May 2007 22:06:53 +0000</pubDate>
		<guid>http://uiscape.com/2007/05/02/voice-code/#comment-42</guid>
					<description>Paul: I don't have any hard data at hand (although I guess they do exist) about programmer productivity, but from my personal experience writing software, I doubt that the #1 goal is the speed of data entry. Modern IDEs (such as Eclipse) have already reduced the need for a lot of typing by providing code templates and context-sensitive completions, features also present in VoiceCode. I don't think that triggering these features by voice is going to be much slower than triggering them with a couple of keystrokes.

Sven: Good observation, as I said, there always needs to be a quick way of correcting mistakes made by voice recognition. Although I suspect that if you're talking to the phone through a headset, all headsets should have a button that allows you to end the call.</description>
		<content:encoded><![CDATA[<p>Paul: I don&#8217;t have any hard data at hand (although I guess they do exist) about programmer productivity, but from my personal experience writing software, I doubt that the #1 goal is the speed of data entry. Modern IDEs (such as Eclipse) have already reduced the need for a lot of typing by providing code templates and context-sensitive completions, features also present in VoiceCode. I don&#8217;t think that triggering these features by voice is going to be much slower than triggering them with a couple of keystrokes.</p>
<p>Sven: Good observation, as I said, there always needs to be a quick way of correcting mistakes made by voice recognition. Although I suspect that if you&#8217;re talking to the phone through a headset, all headsets should have a button that allows you to end the call.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: VoiceCode: Advances in Voice Recognition Software at The Ergonomenon</title>
		<link>http://uiscape.com/2007/05/02/voice-code/#comment-49</link>
		<author>VoiceCode: Advances in Voice Recognition Software at The Ergonomenon</author>
		<pubDate>Sat, 19 May 2007 00:38:01 +0000</pubDate>
		<guid>http://uiscape.com/2007/05/02/voice-code/#comment-49</guid>
					<description>[...] UIScape: Researchers from the National Research Council of Canada have created VoiceCode, an application [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] UIScape: Researchers from the National Research Council of Canada have created VoiceCode, an application [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
