<?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: Metrics Must be Interpreted In Context</title>
	<atom:link href="http://www.juliasshaw.com/blog/2007/02/26/metrics-must-be-interpreted-in-context/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.juliasshaw.com/blog/2007/02/26/metrics-must-be-interpreted-in-context/</link>
	<description>Irrational Rocks</description>
	<lastBuildDate>Mon, 06 Sep 2010 13:28:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Julias Shaw &#8250; Teaser: Creating Ad Hoc Reports in Panopticode 0.2</title>
		<link>http://www.juliasshaw.com/blog/2007/02/26/metrics-must-be-interpreted-in-context/#comment-2</link>
		<dc:creator>Julias Shaw &#8250; Teaser: Creating Ad Hoc Reports in Panopticode 0.2</dc:creator>
		<pubDate>Sat, 30 May 2009 16:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.juliasshaw.com/blog/?p=48#comment-2</guid>
		<description>[...] In Metrics Must be Interpreted In Context I described one of my preferences when creating rules around metrics. Namely, that one should not look at metrics independently, but within the context of other metrics. I described a rule that said unit test line coverage must be greater then 80% for all code with a cyclomatic complexity over 1. While you could enforce this rule in Panopticode 0.1 by creating a custom report, this is not ideal. Who wants to write Java code every time you make a new rule? This will get much easier in Panopticode 0.2. [...]</description>
		<content:encoded><![CDATA[<p>[...] In Metrics Must be Interpreted In Context I described one of my preferences when creating rules around metrics. Namely, that one should not look at metrics independently, but within the context of other metrics. I described a rule that said unit test line coverage must be greater then 80% for all code with a cyclomatic complexity over 1. While you could enforce this rule in Panopticode 0.1 by creating a custom report, this is not ideal. Who wants to write Java code every time you make a new rule? This will get much easier in Panopticode 0.2. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

