<?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"
	>
<channel>
	<title>Comments on: A Simple Measurement</title>
	<atom:link href="http://cwd.dhemery.com/2003/12/a_simple_measurement/feed/" rel="self" type="application/rss+xml" />
	<link>http://cwd.dhemery.com/2003/12/a_simple_measurement/</link>
	<description>Dale Emery on Leadership</description>
	<pubDate>Tue, 06 Jan 2009 23:15:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Brad Appleton</title>
		<link>http://cwd.dhemery.com/2003/12/a_simple_measurement/#comment-105</link>
		<dc:creator>Brad Appleton</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cwd.dhemery.com/2003/12/02/a_simple_measurement/#comment-105</guid>
		<description>I cant help but think of Integral Calculus. Where the most accurate result (for computing the area or volume or surface area of all sort of interesting shapes/solids) if really an approximation that starts with something simple like your string example, and then makes the increments (e.g. number and lengths of string used to sum up the approximate total) smaller and smaller, and takes the mathematical limit as the delta (increment) approaches zero in size to get the most accurate result.

So something like area under a curve is approximated by taking perfect rectangles that fill in the curve (more or less) and uses those rectangles (whose area is EASY to compute - simply height*width) as a first approximation, and then keeps using more and more rectangles of smaller and smaller width to progressively approach a more accurate value.

Maybe there should be some more calculus in project planning books :-)</description>
		<content:encoded><![CDATA[<p>I cant help but think of Integral Calculus. Where the most accurate result (for computing the area or volume or surface area of all sort of interesting shapes/solids) if really an approximation that starts with something simple like your string example, and then makes the increments (e.g. number and lengths of string used to sum up the approximate total) smaller and smaller, and takes the mathematical limit as the delta (increment) approaches zero in size to get the most accurate result.</p>
<p>So something like area under a curve is approximated by taking perfect rectangles that fill in the curve (more or less) and uses those rectangles (whose area is EASY to compute - simply height*width) as a first approximation, and then keeps using more and more rectangles of smaller and smaller width to progressively approach a more accurate value.</p>
<p>Maybe there should be some more calculus in project planning books <img src='http://cwd.dhemery.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly Anderson</title>
		<link>http://cwd.dhemery.com/2003/12/a_simple_measurement/#comment-106</link>
		<dc:creator>Kelly Anderson</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cwd.dhemery.com/2003/12/02/a_simple_measurement/#comment-106</guid>
		<description>According to the Heisenberg uncertainty principle, whatever you seek to measure changes what you are measuring. When you measure people's performance by a metric, you change their performance as they optimize for that metric. Inevitably, you decrease overall efficiency by increasing efficiency measured by one metric.

There's a good paper on this topic (and many others) in "The Best Software Writing I: Selected and Introduced by Joel Spolsky" (Paperback)
by Joel Spolsky ISBN: 1590595009

-Kelly</description>
		<content:encoded><![CDATA[<p>According to the Heisenberg uncertainty principle, whatever you seek to measure changes what you are measuring. When you measure people&#8217;s performance by a metric, you change their performance as they optimize for that metric. Inevitably, you decrease overall efficiency by increasing efficiency measured by one metric.</p>
<p>There&#8217;s a good paper on this topic (and many others) in &#8220;The Best Software Writing I: Selected and Introduced by Joel Spolsky&#8221; (Paperback)<br />
by Joel Spolsky ISBN: 1590595009</p>
<p>-Kelly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly Anderson</title>
		<link>http://cwd.dhemery.com/2003/12/a_simple_measurement/#comment-107</link>
		<dc:creator>Kelly Anderson</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cwd.dhemery.com/2003/12/02/a_simple_measurement/#comment-107</guid>
		<description>Ah, and don't forget this gem:
http://en.wikipedia.org/wiki/Uncertainty_principle</description>
		<content:encoded><![CDATA[<p>Ah, and don&#8217;t forget this gem:<br />
<a href="http://en.wikipedia.org/wiki/Uncertainty_principle" rel="nofollow">http://en.wikipedia.org/wiki/Uncertainty_principle</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
