Comments on: The Double Dawg Dare

By: Refactoring: DoubleDawg Gets A Present! | Situated Geekery

Refactoring: DoubleDawg Gets A Present! | Situated Geekery — Wed, 27 Jan 2010 04:01:36 +0000

[...] this latest in the DoubleDawg series, we are almost ready to do something [...]

By: Jeff Grigg

Jeff Grigg — Mon, 11 Jan 2010 23:07:52 +0000

I teach the value of integration testing over unit/micro testing. While higher level tests are harder and more costly to write, I find that they enable refactoring. And I find that unit/micro tests often discourage refactoring because the tests are so closely tied to the implementation: There are valid refactorings that break the tests – denying you the benefit of having tests to protect you from errors in refactoring.

By: DoubleDawg 3: Follow The Data | Situated Geekery

DoubleDawg 3: Follow The Data | Situated Geekery — Wed, 26 Aug 2009 20:57:24 +0000

[...] back yesterday, and GeePaw’s love for his flock required him to immediately advance the DoubleDawgDare [...]

By: Marty Andrews

Marty Andrews — Wed, 03 Jun 2009 09:49:02 +0000

This is one I couldn’t resist. I wrote Complexian, so I’m seeking out bad code with it all the time. I test it by running it against open source projects to see what I can find. Here’s two candidates for you. The numbers listed are the NPath complexity of the methods at that location.

From the Java source code itself:
jdk-1_5_0-src-scsl/j2se/src/share/classes/com/sun/org/apache/xerces/internal/impl/xpath/XPath.java:1322: Complexity is 7693507144912343066

From struts:
struts-2.1.6/src/core/src/main/java/org/apache/struts2/components/UIBean.java:616: Complexity is 8134399640484

By: GeePawHill

GeePawHill — Wed, 03 Jun 2009 01:08:46 +0000

I will definitely be sharing both the source (in steps) and the mildly expurgated screencasts that go with them.

By: Nick Pellow

Nick Pellow — Wed, 03 Jun 2009 01:02:34 +0000

I Double Dog Dare ya!
FastPageParser from Sitemesh
http://clover.atlassian.com/browse/sitemesh/proj-risks.html
Or for something a bit smaller – what about XWork’s SpringProxyableObjectFactory, or PropertiesReader: http://clover.atlassian.com/browse/xwork/proj-risks.html

By: Brian Marick

Brian Marick — Tue, 02 Jun 2009 16:59:35 +0000

It’d be nice if you could do this on github or someplace like that, so that the entire world might look at the differences between commits. I imagine something like a time-lapse movie, perhaps with running commentary recorded as you’re doing the refactoring.

By: Steve Quinlan

Steve Quinlan — Tue, 02 Jun 2009 11:51:42 +0000

class HelloWorldApp {
public static void main(String[] args) {
System.out.println(“Hello World!”);
}
}

It’s on now, Mike

By: Andy Palmer

Andy Palmer — Tue, 02 Jun 2009 09:49:37 +0000

This is really useful advice, thank you for making it explicit.

This is going straight into my toolbox

I am looking forward to seeing your account of the challenge

By: Kristof Neirynck

Kristof Neirynck — Tue, 02 Jun 2009 09:34:10 +0000

the correct link for “microtest” is:
http://anarchycreek.com/2009/05/20/theyre-called-microtests/