<?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: SA Tenets &#8211; First, Do No Harm</title>
	<atom:link href="http://www.opssa.net/2009/04/sa-tenets-first-do-no-harm/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.opssa.net/2009/04/sa-tenets-first-do-no-harm/</link>
	<description>OpsSA.net - SA wisdom and philosophy</description>
	<lastBuildDate>Sat, 02 Jan 2010 16:43:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: cerberus</title>
		<link>http://www.opssa.net/2009/04/sa-tenets-first-do-no-harm/comment-page-1/#comment-797</link>
		<dc:creator>cerberus</dc:creator>
		<pubDate>Mon, 27 Apr 2009 15:32:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.opssa.net/?p=263#comment-797</guid>
		<description>Good kickoff.  

Two things come to mind when it comes to do no harm:

1) Document the fix!  This is, IMO, more important that the original documentation that should accompany the environment in the steady state.  A fix @ 3am that isn&#039;t written down, is very quickly forgotten, and may make the existing documentation wrong.  Of course, if it&#039;s a simple host reboot, this may not apply.

2) Harm has been done.  Own up to it!  We all make mistakes (being human..ain&#039;t it great?).  If the pooch is horked and you did it, own up to it, tell folks what happened, that you did it and are working on a fix, or explain what the fix is that has just been applied.  If you are afraid to make a mistake, you are in the wrong profession.

Making the same mistake over and over again is a different problem for a different post.</description>
		<content:encoded><![CDATA[<p>Good kickoff.  </p>
<p>Two things come to mind when it comes to do no harm:</p>
<p>1) Document the fix!  This is, IMO, more important that the original documentation that should accompany the environment in the steady state.  A fix @ 3am that isn&#8217;t written down, is very quickly forgotten, and may make the existing documentation wrong.  Of course, if it&#8217;s a simple host reboot, this may not apply.</p>
<p>2) Harm has been done.  Own up to it!  We all make mistakes (being human..ain&#8217;t it great?).  If the pooch is horked and you did it, own up to it, tell folks what happened, that you did it and are working on a fix, or explain what the fix is that has just been applied.  If you are afraid to make a mistake, you are in the wrong profession.</p>
<p>Making the same mistake over and over again is a different problem for a different post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chet</title>
		<link>http://www.opssa.net/2009/04/sa-tenets-first-do-no-harm/comment-page-1/#comment-793</link>
		<dc:creator>chet</dc:creator>
		<pubDate>Thu, 23 Apr 2009 03:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.opssa.net/?p=263#comment-793</guid>
		<description>and this goes along with &quot;document everything&quot;.. because when stuff is broken and you&#039;re in a panic to fix it, being able to go over previously confirmed/established steps will help to make sure you don&#039;t make a whoopsies :D

then again, not everything can be documented, like in your case of dd-itis, so yeah, hehe</description>
		<content:encoded><![CDATA[<p>and this goes along with &#8220;document everything&#8221;.. because when stuff is broken and you&#8217;re in a panic to fix it, being able to go over previously confirmed/established steps will help to make sure you don&#8217;t make a whoopsies :D</p>
<p>then again, not everything can be documented, like in your case of dd-itis, so yeah, hehe</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.172 seconds -->
