Who wrote this C.R.A.P.?

Tagged:

All the great Java static analysis tools are fine (PMD, FindBugs, Checkstyle), but what if we were to combine things like cyclomatic complexity with code coverage and svn "blame"? Well, that would be the core of the CRAP metric. Enter crap4j.

This has made the rounds on Artima and the posse, so it may not be new, but it is something you should check out if you haven't yet had a chance.

A good place to start is with the podcast interview of the CRAP creator himself, Ablerto Savoia, on JavaWorld's Java Technology Insider (apologies about linking to JavaWorld up front).