<?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: Ask Aza: Mistake Proofing</title>
	<atom:link href="http://www.azarask.in/blog/post/ask-aza-mistake-proofing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.azarask.in/blog/post/ask-aza-mistake-proofing/</link>
	<description>-- aza &#124; ɐzɐ --</description>
	<lastBuildDate>Tue, 07 Feb 2012 20:21:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: شات كتابي</title>
		<link>http://www.azarask.in/blog/post/ask-aza-mistake-proofing/comment-page-1/#comment-12958</link>
		<dc:creator>شات كتابي</dc:creator>
		<pubDate>Thu, 20 Jan 2011 13:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=123#comment-12958</guid>
		<description>thnks 
gooooood</description>
		<content:encoded><![CDATA[<p>thnks<br />
gooooood</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Yip</title>
		<link>http://www.azarask.in/blog/post/ask-aza-mistake-proofing/comment-page-1/#comment-2905</link>
		<dc:creator>Jason Yip</dc:creator>
		<pubDate>Tue, 25 Nov 2008 06:20:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=123#comment-2905</guid>
		<description>6 levels of mistake proofing:

1. Eliminate the step
2. Replace with something more reliable
3. Prevent by design
4. Facilitate to make steps easier
5. Detect errors quickly
6. Mitigate to minimise effects</description>
		<content:encoded><![CDATA[<p>6 levels of mistake proofing:</p>
<p>1. Eliminate the step<br />
2. Replace with something more reliable<br />
3. Prevent by design<br />
4. Facilitate to make steps easier<br />
5. Detect errors quickly<br />
6. Mitigate to minimise effects</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Warden</title>
		<link>http://www.azarask.in/blog/post/ask-aza-mistake-proofing/comment-page-1/#comment-2904</link>
		<dc:creator>Kevin Warden</dc:creator>
		<pubDate>Tue, 25 Nov 2008 03:10:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=123#comment-2904</guid>
		<description>Although I like, and agree with your point, there has to be some sort of bypass to allow for someone to purposely use something incorrectly. Closed source software forces you to use things for the developer&#039;s intended purpose. Think Internet Explorer. Now think Firefox. If I want to use a browser for something other than the developer&#039;s intended purpose of web-browsing (testing a site, improving a built-in feature, etc.), then I have to use Firefox as IE won&#039;t let me purposely break something.</description>
		<content:encoded><![CDATA[<p>Although I like, and agree with your point, there has to be some sort of bypass to allow for someone to purposely use something incorrectly. Closed source software forces you to use things for the developer&#8217;s intended purpose. Think Internet Explorer. Now think Firefox. If I want to use a browser for something other than the developer&#8217;s intended purpose of web-browsing (testing a site, improving a built-in feature, etc.), then I have to use Firefox as IE won&#8217;t let me purposely break something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave</title>
		<link>http://www.azarask.in/blog/post/ask-aza-mistake-proofing/comment-page-1/#comment-2897</link>
		<dc:creator>dave</dc:creator>
		<pubDate>Mon, 24 Nov 2008 17:04:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=123#comment-2897</guid>
		<description>I wonder what you&#039;re opinion is on how this is reflected in the KDE vs Gnome wars. The KDE side are trying to empower a commited and vigilant prosumer who is fully engaged with their task while Gnome is trying guide users towards the best path without overwhelming them with choice and helping them avoid shooting themselves in the foot.

Or less charitably, the KDE interface looks like the car that Homer Simpson designed with every single gadget and option crammed in willy-nilly, ready to explode at the press of the wrong button. And Gnome is a bunch of fascists who have nothing but contempt for their imbicile users and will slowly remove every single feature until there is nothing left for them to get wrong.

Is there an objectively measurable third-way?</description>
		<content:encoded><![CDATA[<p>I wonder what you&#8217;re opinion is on how this is reflected in the KDE vs Gnome wars. The KDE side are trying to empower a commited and vigilant prosumer who is fully engaged with their task while Gnome is trying guide users towards the best path without overwhelming them with choice and helping them avoid shooting themselves in the foot.</p>
<p>Or less charitably, the KDE interface looks like the car that Homer Simpson designed with every single gadget and option crammed in willy-nilly, ready to explode at the press of the wrong button. And Gnome is a bunch of fascists who have nothing but contempt for their imbicile users and will slowly remove every single feature until there is nothing left for them to get wrong.</p>
<p>Is there an objectively measurable third-way?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Humphrey</title>
		<link>http://www.azarask.in/blog/post/ask-aza-mistake-proofing/comment-page-1/#comment-2895</link>
		<dc:creator>David Humphrey</dc:creator>
		<pubDate>Mon, 24 Nov 2008 15:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=123#comment-2895</guid>
		<description>I can&#039;t find the exact study now, but this is pretty close:

http://www.npr.org/templates/story/story.php?storyId=91945517

The idea was to look at how applying aviation&#039;s use of checklists, and call-response from pilot to co-pilot, could be used to deal with human error.  The particular study I&#039;m thinking of related to a hospital trying it and reducing patient sickness due to error with a particular procedure to 0%.  It was a shocking and amazing outcome.

Reading your post brought this back to mind.  I wonder if the call-response model has any place in our apps?  We don&#039;t want to have all our actions mirrored back to us; but at the same time, when we make (what could be) a mistake, knowing that the undo is available would be good.  I&#039;m not sure the practical ramifications of mapping this onto software, but it&#039;s interesting.</description>
		<content:encoded><![CDATA[<p>I can&#8217;t find the exact study now, but this is pretty close:</p>
<p><a href="http://www.npr.org/templates/story/story.php?storyId=91945517" rel="nofollow">http://www.npr.org/templates/story/story.php?storyId=91945517</a></p>
<p>The idea was to look at how applying aviation&#8217;s use of checklists, and call-response from pilot to co-pilot, could be used to deal with human error.  The particular study I&#8217;m thinking of related to a hospital trying it and reducing patient sickness due to error with a particular procedure to 0%.  It was a shocking and amazing outcome.</p>
<p>Reading your post brought this back to mind.  I wonder if the call-response model has any place in our apps?  We don&#8217;t want to have all our actions mirrored back to us; but at the same time, when we make (what could be) a mistake, knowing that the undo is available would be good.  I&#8217;m not sure the practical ramifications of mapping this onto software, but it&#8217;s interesting.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

