<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Avoiding Developer UI</title>
	<link>http://www.timberglund.com/blog/archives/606</link>
	<description>See what large letters I use as I write to you in my own hand.</description>
	<pubDate>Thu, 20 Nov 2008 14:42:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Tim</title>
		<link>http://www.timberglund.com/blog/archives/606#comment-6192</link>
		<pubDate>Thu, 14 Dec 2006 14:13:02 +0000</pubDate>
		<guid>http://www.timberglund.com/blog/archives/606#comment-6192</guid>
					<description>Moosebugs:

Thanks! Glad you liked it. I'm sure adding users to the mix will help, particularly if they are used not just to develop requirements but also to do usability testing. I've read about people doing low-cost usability testing labs with screen recorders and webcams. (That way you can keep technical staff out of the room entirely, and see what a lone user actually does with the software.) I've never done this myself, but I'd like to at some point. I know I've got a product that could benefit from it.

Users are certainly less hamstrung by developer's tunnel vision, but they too often don't really know what they need. Sometimes non-technical people aren't good enough at finding abstractions, whereas developers are a little too good at it. Finding somebody who can hit the sweet spot, whether he come in the guise of &quot;user&quot; or &quot;developer,&quot; is the trick. I sure haven't yet. :)</description>
		<content:encoded><![CDATA[<p>Moosebugs:</p>
<p>Thanks! Glad you liked it. I&#8217;m sure adding users to the mix will help, particularly if they are used not just to develop requirements but also to do usability testing. I&#8217;ve read about people doing low-cost usability testing labs with screen recorders and webcams. (That way you can keep technical staff out of the room entirely, and see what a lone user actually does with the software.) I&#8217;ve never done this myself, but I&#8217;d like to at some point. I know I&#8217;ve got a product that could benefit from it.</p>
<p>Users are certainly less hamstrung by developer&#8217;s tunnel vision, but they too often don&#8217;t really know what they need. Sometimes non-technical people aren&#8217;t good enough at finding abstractions, whereas developers are a little too good at it. Finding somebody who can hit the sweet spot, whether he come in the guise of &#8220;user&#8221; or &#8220;developer,&#8221; is the trick. I sure haven&#8217;t yet. <img src='http://www.timberglund.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Moosebugs</title>
		<link>http://www.timberglund.com/blog/archives/606#comment-6173</link>
		<pubDate>Wed, 13 Dec 2006 14:50:17 +0000</pubDate>
		<guid>http://www.timberglund.com/blog/archives/606#comment-6173</guid>
					<description>Excellent! I just sent this to my development team.  We are still working with complex, specialized, domain-specific engineering analysis software with text file input and output dating from the early 70s.  And it's been maintained by the algorithm developers all along.  When a new feature needs to be added, it's these developers that make the interface.  And so we perpetuate a bad situation and wind up making it worse.

But I'm trying to change that with the next major version change.  And we're trying to get more users on the development team to help with both requirements and testing.</description>
		<content:encoded><![CDATA[<p>Excellent! I just sent this to my development team.  We are still working with complex, specialized, domain-specific engineering analysis software with text file input and output dating from the early 70s.  And it&#8217;s been maintained by the algorithm developers all along.  When a new feature needs to be added, it&#8217;s these developers that make the interface.  And so we perpetuate a bad situation and wind up making it worse.</p>
<p>But I&#8217;m trying to change that with the next major version change.  And we&#8217;re trying to get more users on the development team to help with both requirements and testing.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
