From: Jeremy McAnally <jeremymcanally@...>
Date: 2008-06-24T22:32:54+09:00
Subject: Re: [ANN] KABLAME! 0.2.1 Released

I'm sure he does.  I'm sure he also realizes that C0 analysis like
rcov doesn't do much good, documentation analysis for dcov isn't a
true tell for how easy the code is to understand, complexity analysis
from flog isn't a good indicator of how well something is solving a
problem, and so on ad nauseum.

Tools are just that: tools.  And they help you solve problems that you
see that you are having.  If he saw a _people_ problem with TDD (as
in, "Oh, there are enough tests!" or "Tests aren't needed!") then
perhaps this tool solved his problem.

Knocking it because it doesn't solve every people or technical problem
related to testing is like knocking Rails because it doesn't write the
web app for you.

--Jeremy

On Tue, Jun 24, 2008 at 3:06 AM, Eleanor McHugh
<eleanor@games-with-brains.com> wrote:
> On 22 Jun 2008, at 17:26, Jacob Dunphy wrote:
>>
>> The only positive effect KABLAME! ever had was turning one of our team
>> members into a serious TDD believer.  When he saw the first print-out
>> and realized he was 10th on the list, he had visual motivation (on top
>> of my hounding and harassment) to start writing tests with every
>> feature he worked on or changed.  He started writing tests everywhere.
>> He started writing them in his personal projects.  The quality of the
>> code reflected the new drive to be a more comprehensive tester.
>
> You are aware that code 'quality' is a far more complex concept than 'has
> lots of tests'?
>
>
> Ellie
>
> Eleanor McHugh
> Games With Brains
> http://slides.games-with-brains.net
> ----
> raise ArgumentError unless @reality.responds_to? :reason
>
>
>
>



-- 
http://jeremymcanally.com/
http://entp.com

Read my books:
Ruby in Practice (http://manning.com/mcanally/)
My free Ruby e-book (http://humblelittlerubybook.com/)

Or, my blogs:
http://mrneighborly.com
http://rubyinpractice.com