This podcast doesn’t stink, man
I recently had a copasetic conversation with Alberto Savoia regarding the hip CRAP metric– my parents would be appalled with our language (I think the word in question is used at least 135 times); however, we had a good time discussing the efficacy of the metric, its future, and of course, its malodorously applied name.
In short, the CRAP metric effectively marries code coverage with cyclomatic complexity and an effort to delineate risk associated with change. Have a listen (courtesy of JavaWorld) and stay tuned for more podcasts, baby!
Thursday 25 Oct 2007 | Andy | Code Metrics, Developer Testing
Huh! Another good usage of a meaningful and phonetically pleasant acronym. My motorcycle buddies down at NESBA (http://www.nesba.org) use the term to describe control riders guiding fast ninjas through snail traffic. They call it Control Rider Assisted Pass (CRAP). And now a second CRAP in my life - is this luck or what?
PS: Your blog thinks I am SPAM - (SEARCHING for PEOPLE with ACRONYMS in MIND)
http://z.about.com/d/politicalhumor/1/0/Q/j/1/warming_war.jpg
[…] JRuby gabfest In keeping with my copasetic conversations with hip people, I recently had the opportunity to chat with my friend Neal Ford regarding JRuby. As anyone who’s met Neal knows, this cat worships Ruby– what’s more, Neal is a super smart dude that lives and breathes Java as well. Accordingly, Neal offers some interesting thoughts on JRuby (and of course, Ruby) such as meta-programming, JRuby’s future, associated tools, and even Groovy. […]
[…] metrics and trended– for instance, complexity alone is somewhat interesting, but pairing complexity with code coverage paints a much more detailed metric that bears understanding. High complexity with low coverage is […]