<?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: I Had Downtime Today.  Here&#039;s What I&#039;m Doing About It.</title>
	<atom:link href="http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=i-had-downtime-today-heres-what-im-doing-about-it</link>
	<description>Patrick McKenzie (patio11) blogs on software development, marketing, and general business topics</description>
	<lastBuildDate>Sat, 11 Feb 2012 17:02:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Building Highly Reliable Websites For Small Companies: MicroISV on a Shoestring</title>
		<link>http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/#comment-2415</link>
		<dc:creator>Building Highly Reliable Websites For Small Companies: MicroISV on a Shoestring</dc:creator>
		<pubDate>Tue, 20 Apr 2010 13:54:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=861#comment-2415</guid>
		<description>[...] Minimizing operator error is critically important, because you are the least reliable component of your system.  Because you rely on software to do most of the actual work, when you touch the system you&#8217;re almost by definition performing something novel that isn&#8217;t automated.  Novel operations are moving parts and vastly more likely to fail than known-good operations that your system crunches millions of times per day.  Additionally, even if what you want to do is absolutely flawlessly planned out, you&#8217;ll often not execute flawlessly on the plan.  This was one of the root causes of my worst downtime&#160;ever. [...]</description>
		<content:encoded><![CDATA[<p>[...] Minimizing operator error is critically important, because you are the least reliable component of your system.  Because you rely on software to do most of the actual work, when you touch the system you&#8217;re almost by definition performing something novel that isn&#8217;t automated.  Novel operations are moving parts and vastly more likely to fail than known-good operations that your system crunches millions of times per day.  Additionally, even if what you want to do is absolutely flawlessly planned out, you&#8217;ll often not execute flawlessly on the plan.  This was one of the root causes of my worst downtime&nbsp;ever. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Running A Software Business On 5 Hours A Week: MicroISV on a Shoestring</title>
		<link>http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/#comment-2414</link>
		<dc:creator>Running A Software Business On 5 Hours A Week: MicroISV on a Shoestring</dc:creator>
		<pubDate>Sun, 21 Mar 2010 15:35:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=861#comment-2414</guid>
		<description>[...] your testing and QA procedures to avoid it.  When they fail&#8201;&#8212;&#8201;and they will fail&#8201;&#8212;&#8201;fix the process which permitted the failure to happen, in addition to just [...]</description>
		<content:encoded><![CDATA[<p>[...] your testing and QA procedures to avoid it.  When they fail&thinsp;&#8212;&thinsp;and they will fail&thinsp;&#8212;&thinsp;fix the process which permitted the failure to happen, in addition to just [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: High Scalability のホット･リンク集 ： Cassandra@Twitter インタビューもあるよ！ [ #cloud #cloudcomputing #nosql ] &#171; Agile Cat &#8212; Azure &#38; Hadoop &#8212; Talking Book</title>
		<link>http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/#comment-2413</link>
		<dc:creator>High Scalability のホット･リンク集 ： Cassandra@Twitter インタビューもあるよ！ [ #cloud #cloudcomputing #nosql ] &#171; Agile Cat &#8212; Azure &#38; Hadoop &#8212; Talking Book</dc:creator>
		<pubDate>Thu, 25 Feb 2010 22:39:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=861#comment-2413</guid>
		<description>[...] I Had Downtime Today. Here’s What I’m Doing About It by Patrick McKenzie. Awesome deep dive into went wrong with Bingo Card Creator. Sh*t happens. How do you design a process to help prevent it from happening and how do you deal with problems with integrity when they do? [...]</description>
		<content:encoded><![CDATA[<p>[...] I Had Downtime Today. Here’s What I’m Doing About It by Patrick McKenzie. Awesome deep dive into went wrong with Bingo Card Creator. Sh*t happens. How do you design a process to help prevent it from happening and how do you deal with problems with integrity when they do? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/#comment-2412</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Tue, 23 Feb 2010 13:31:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=861#comment-2412</guid>
		<description>&gt;&gt;
Are you using any tracking tool to keep tabs on bugs/features/to-dos/inquiries?
&gt;&gt;

I use the old Mk. 1 pen and paper to keep track of anything that needs to stay in my brain longer than a day and shorter than a week.  For example, &quot;What I am going to implement this Saturday.&quot;  Email inquiries I answer immediately the next time I check email and star in Gmail if they require follow-up.  Everything else gets either blogged, remembered, or forgotten.</description>
		<content:encoded><![CDATA[<p>&gt;&gt;<br />
Are you using any tracking tool to keep tabs on bugs/features/to-dos/inquiries?<br />
&gt;&gt;</p>
<p>I use the old Mk. 1 pen and paper to keep track of anything that needs to stay in my brain longer than a day and shorter than a week.  For example, &#8220;What I am going to implement this Saturday.&#8221;  Email inquiries I answer immediately the next time I check email and star in Gmail if they require follow-up.  Everything else gets either blogged, remembered, or forgotten.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/#comment-2411</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 22 Feb 2010 15:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=861#comment-2411</guid>
		<description>So having not heard of the five why&#039;s had to quick do a look up and of course went to the ubiquity site wikipidia.  So for someone as skilled at root cause analysis as you I could see the 5 whys being sufficient but had to pull the critique because it just seeems like a very loose framework that may create a culture of root cause analysis but not complete the steps.  So from the wiki:

While the 5 Whys is a powerful tool for engineers or technically savvy individuals to help get to the true causes of problems, it has been criticized by Teruyuki Minoura, former managing director of global purchasing for Toyota, as being too basic a tool to analyze root causes to the depth that is needed to ensure that the causes are fixed. Reasons for this criticism include:

Tendency for investigators to stop at symptoms rather than going on to lower level root causes.
Inability to go beyond the investigator&#039;s current knowledge - can&#039;t find causes that they don&#039;t already know
Lack of support to help the investigator to ask the right &quot;why&quot; questions.
Results aren&#039;t repeatable - different people using 5 Whys come up with different causes for the same problem.
The tendency to isolate a single root cause, whereas each question could elicit many different root causes</description>
		<content:encoded><![CDATA[<p>So having not heard of the five why&#8217;s had to quick do a look up and of course went to the ubiquity site wikipidia.  So for someone as skilled at root cause analysis as you I could see the 5 whys being sufficient but had to pull the critique because it just seeems like a very loose framework that may create a culture of root cause analysis but not complete the steps.  So from the wiki:</p>
<p>While the 5 Whys is a powerful tool for engineers or technically savvy individuals to help get to the true causes of problems, it has been criticized by Teruyuki Minoura, former managing director of global purchasing for Toyota, as being too basic a tool to analyze root causes to the depth that is needed to ensure that the causes are fixed. Reasons for this criticism include:</p>
<p>Tendency for investigators to stop at symptoms rather than going on to lower level root causes.<br />
Inability to go beyond the investigator&#8217;s current knowledge &#8211; can&#8217;t find causes that they don&#8217;t already know<br />
Lack of support to help the investigator to ask the right &#8220;why&#8221; questions.<br />
Results aren&#8217;t repeatable &#8211; different people using 5 Whys come up with different causes for the same problem.<br />
The tendency to isolate a single root cause, whereas each question could elicit many different root causes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: My daily readings 02/22/2010 &#171; Strange Kite</title>
		<link>http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/#comment-2410</link>
		<dc:creator>My daily readings 02/22/2010 &#171; Strange Kite</dc:creator>
		<pubDate>Mon, 22 Feb 2010 11:30:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=861#comment-2410</guid>
		<description>[...] I Had Downtime Today. Here’s What I’m Doing About It.: MicroISV on a Shoestring [...]</description>
		<content:encoded><![CDATA[<p>[...] I Had Downtime Today. Here’s What I’m Doing About It.: MicroISV on a Shoestring [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Torben</title>
		<link>http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/#comment-2409</link>
		<dc:creator>Torben</dc:creator>
		<pubDate>Mon, 22 Feb 2010 10:38:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=861#comment-2409</guid>
		<description>You don&#039;t often talk about bug *tracking* but often of the *squashing* itself. Are you using any tracking tool to keep tabs on bugs/features/to-dos/inquiries? I&#039;ve seen that FogBugz comes with a free account for 1-2 people; just right for a mISV. I&#039;d like to hear your thoughts about this, or about similar tools?</description>
		<content:encoded><![CDATA[<p>You don&#8217;t often talk about bug *tracking* but often of the *squashing* itself. Are you using any tracking tool to keep tabs on bugs/features/to-dos/inquiries? I&#8217;ve seen that FogBugz comes with a free account for 1-2 people; just right for a mISV. I&#8217;d like to hear your thoughts about this, or about similar tools?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Stamatiou</title>
		<link>http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/#comment-2408</link>
		<dc:creator>Paul Stamatiou</dc:creator>
		<pubDate>Mon, 22 Feb 2010 06:44:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=861#comment-2408</guid>
		<description>I have thought about creating a &quot;drop a message directly to your dashboard&quot; feature for Skribit for quite some time - or at least beefing up flash[] stuff. I think this post has convinced me to put that on my to do list. Thanks!

Been following your blog/HN stuff for what seems like forever.

Best,
Paul</description>
		<content:encoded><![CDATA[<p>I have thought about creating a &#8220;drop a message directly to your dashboard&#8221; feature for Skribit for quite some time &#8211; or at least beefing up flash[] stuff. I think this post has convinced me to put that on my to do list. Thanks!</p>
<p>Been following your blog/HN stuff for what seems like forever.</p>
<p>Best,<br />
Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Giles Bowkett</title>
		<link>http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/#comment-2407</link>
		<dc:creator>Giles Bowkett</dc:creator>
		<pubDate>Mon, 22 Feb 2010 02:02:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=861#comment-2407</guid>
		<description>Seriously, that&#039;s what you have to do for the test server? I want to work in Japan.</description>
		<content:encoded><![CDATA[<p>Seriously, that&#8217;s what you have to do for the test server? I want to work in Japan.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Listen to I Had Downtime Today. Here’s What I’m Doing About It. - MicroISV on a Shoestring - Hear a Blog</title>
		<link>http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/#comment-2406</link>
		<dc:creator>Listen to I Had Downtime Today. Here’s What I’m Doing About It. - MicroISV on a Shoestring - Hear a Blog</dc:creator>
		<pubDate>Sun, 21 Feb 2010 23:36:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=861#comment-2406</guid>
		<description>[...] http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/" rel="nofollow">http://www.kalzumeus.com/2010/02/21/i-had-downtime-today-heres-what-im-doing-about-it/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

