<?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: Sketching complexity with Groovy</title>
	<atom:link href="http://thediscoblog.com/2007/03/30/sketching-complexity-with-groovy/feed/" rel="self" type="application/rss+xml" />
	<link>http://thediscoblog.com/2007/03/30/sketching-complexity-with-groovy/</link>
	<description>Can you dig it man?</description>
	<pubDate>Tue, 07 Oct 2008 14:25:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Andy</title>
		<link>http://thediscoblog.com/2007/03/30/sketching-complexity-with-groovy/#comment-7846</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Mon, 02 Apr 2007 15:22:01 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/03/30/sketching-complexity-with-groovy/#comment-7846</guid>
		<description>Philip-- thanks for the pointer to Hackystat! This looks interesting indeed. The statement "if variations in the level of code complexity are correlated with daily build failure" is quite interesting as in a former life, we built a similar engine that reported on which lines of code changed if there was a test failure for a test that previously worked.

I look forward to checking out Hackystat-- keep up the great work!</description>
		<content:encoded><![CDATA[<p>Philip&#8211; thanks for the pointer to Hackystat! This looks interesting indeed. The statement &#8220;if variations in the level of code complexity are correlated with daily build failure&#8221; is quite interesting as in a former life, we built a similar engine that reported on which lines of code changed if there was a test failure for a test that previously worked.</p>
<p>I look forward to checking out Hackystat&#8211; keep up the great work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: disco &#187; Sketching complexity with Groovy</title>
		<link>http://thediscoblog.com/2007/03/30/sketching-complexity-with-groovy/#comment-7768</link>
		<dc:creator>disco &#187; Sketching complexity with Groovy</dc:creator>
		<pubDate>Sat, 31 Mar 2007 20:29:45 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/03/30/sketching-complexity-with-groovy/#comment-7768</guid>
		<description>[...] Hon Daddy Dad wrote an interesting post today onHere&#8217;s a quick excerptThis disco tool analyzes a code base and reports everything relating to code length, including class sizes, method sizes, and the number of methods found in a class. Whatâ€™s more, JavaNCSS reports method complexities, Cyclomatic style. &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Hon Daddy Dad wrote an interesting post today onHere&#8217;s a quick excerptThis disco tool analyzes a code base and reports everything relating to code length, including class sizes, method sizes, and the number of methods found in a class. Whatâ€™s more, JavaNCSS reports method complexities, Cyclomatic style. &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Johnson</title>
		<link>http://thediscoblog.com/2007/03/30/sketching-complexity-with-groovy/#comment-7758</link>
		<dc:creator>Philip Johnson</dc:creator>
		<pubDate>Sat, 31 Mar 2007 17:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/03/30/sketching-complexity-with-groovy/#comment-7758</guid>
		<description>You might be interested in the open source &lt;a href="http://www.hackystat.org" rel="nofollow"&gt;Hackystat Project&lt;/a&gt; which explores how to more easily collect and integrate together software measures.  In Hackystat, software "sensors" are attached to various software development tools and sent to a centralized server.  Developers can run analyses that illuminate relationships between both process and product-oriented metrics.  This makes it easy to investigate, for example, if  variations in the level of code complexity are correlated with daily build failure.  

There is a link on the home page to the Version 8 planning document, which might be of interest as this major release should make it much easier for developers such as yourself to "knock out" new kinds of reports using languages like Groovy.  If that's your bag, of course.</description>
		<content:encoded><![CDATA[<p>You might be interested in the open source <a href="http://www.hackystat.org" rel="nofollow">Hackystat Project</a> which explores how to more easily collect and integrate together software measures.  In Hackystat, software &#8220;sensors&#8221; are attached to various software development tools and sent to a centralized server.  Developers can run analyses that illuminate relationships between both process and product-oriented metrics.  This makes it easy to investigate, for example, if  variations in the level of code complexity are correlated with daily build failure.  </p>
<p>There is a link on the home page to the Version 8 planning document, which might be of interest as this major release should make it much easier for developers such as yourself to &#8220;knock out&#8221; new kinds of reports using languages like Groovy.  If that&#8217;s your bag, of course.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bar Restaurant &#187; Sketching complexity with Groovy</title>
		<link>http://thediscoblog.com/2007/03/30/sketching-complexity-with-groovy/#comment-7710</link>
		<dc:creator>Bar Restaurant &#187; Sketching complexity with Groovy</dc:creator>
		<pubDate>Sat, 31 Mar 2007 01:41:04 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/03/30/sketching-complexity-with-groovy/#comment-7710</guid>
		<description>[...] Original post by Andy and a wordpress plugin by Elliott    &#160; [...]</description>
		<content:encoded><![CDATA[<p>[...] Original post by Andy and a wordpress plugin by Elliott    &nbsp; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
