<?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: Tapping with a Sledge Hammer</title>
	<atom:link href="http://www.ldscio.org/2008/04/13/tapping-with-a-sledge-hammer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ldscio.org/2008/04/13/tapping-with-a-sledge-hammer/</link>
	<description>Chief Information Officer for The Church of Jesus Christ of Latter-day Saints</description>
	<lastBuildDate>Wed, 03 Mar 2010 16:47:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nathan Zaugg</title>
		<link>http://www.ldscio.org/2008/04/13/tapping-with-a-sledge-hammer/comment-page-1/#comment-1866</link>
		<dc:creator>Nathan Zaugg</dc:creator>
		<pubDate>Wed, 23 Apr 2008 20:51:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=94#comment-1866</guid>
		<description>That is a great analogy.  Of course now days my son will build a car himself, and we will build a car together.  Why limit yourself to just one.  Of course, your not hard-core pine-wood derby until you&#039;ve nickel-plated your car!  I also enjoy the races where the rules are thrown out and creativity can reigh suprime!
I did notice, however, that there sseems to be a lot of emphisis on code coverage at the Church.  While I am a big fan of unit testing I often try to point out that Code Coverage tells us little more than “are there unit tests” not “are we unit testing”.  The former indicates that the code is indeed being executed.  The latter indicates that the code is being exercised.

Scott Hanselman discribes this in a podcast and slides available here:
http://www.hanselman.com/blog/HanselminutesPodcast103QuetzalBradleyOnTestingAfterUnitTestsAndTheMythOfCodeCoverage.aspx</description>
		<content:encoded><![CDATA[<p>That is a great analogy.  Of course now days my son will build a car himself, and we will build a car together.  Why limit yourself to just one.  Of course, your not hard-core pine-wood derby until you&#8217;ve nickel-plated your car!  I also enjoy the races where the rules are thrown out and creativity can reigh suprime!<br />
I did notice, however, that there sseems to be a lot of emphisis on code coverage at the Church.  While I am a big fan of unit testing I often try to point out that Code Coverage tells us little more than “are there unit tests” not “are we unit testing”.  The former indicates that the code is indeed being executed.  The latter indicates that the code is being exercised.</p>
<p>Scott Hanselman discribes this in a podcast and slides available here:<br />
<a href="http://www.hanselman.com/blog/HanselminutesPodcast103QuetzalBradleyOnTestingAfterUnitTestsAndTheMythOfCodeCoverage.aspx" rel="nofollow">http://www.hanselman.com/blog/HanselminutesPodcast103QuetzalBradleyOnTestingAfterUnitTestsAndTheMythOfCodeCoverage.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Peay</title>
		<link>http://www.ldscio.org/2008/04/13/tapping-with-a-sledge-hammer/comment-page-1/#comment-1848</link>
		<dc:creator>Dan Peay</dc:creator>
		<pubDate>Mon, 14 Apr 2008 21:55:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.ldscio.org/?p=94#comment-1848</guid>
		<description>I love the analogy.  I am developing a market strategy to launch our software into a new market.  My process-oriented, Business Development manager is good about getting the checks and balances of having the right contracts and agreements in place for risk management.    I would rather do business with a handshake rather than spending all the time and effort in having ever page contain a signature line.  I’m trying to find a safe place in between the two.  After thinking about your story, I wonder if some of our processes seem like “Sledge Hammers.”  Or, could lack of a contract become the “Sledge Hammer” that is used on me by a disgruntled partner or customer?   I realize the process that I am talking about is vastly different, but I still really appreciate this article.  “…process shouldn’t be a gate unless it is absolutely necessary.”  Well said!</description>
		<content:encoded><![CDATA[<p>I love the analogy.  I am developing a market strategy to launch our software into a new market.  My process-oriented, Business Development manager is good about getting the checks and balances of having the right contracts and agreements in place for risk management.    I would rather do business with a handshake rather than spending all the time and effort in having ever page contain a signature line.  I’m trying to find a safe place in between the two.  After thinking about your story, I wonder if some of our processes seem like “Sledge Hammers.”  Or, could lack of a contract become the “Sledge Hammer” that is used on me by a disgruntled partner or customer?   I realize the process that I am talking about is vastly different, but I still really appreciate this article.  “…process shouldn’t be a gate unless it is absolutely necessary.”  Well said!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
