I suppose we could also call the scaffold we use when
constructing a large building as waste, or the safety
harnesses as waste.

One useful distinction I've seen from the Lean folks
is between type 1 and type 2 waste. Type 1 waste
is something we know how to get rid of now without
ill effects, type 2 waste is something we don't know
how to get rid of without ill effects.

Since we don't know how to get rid of it without
ill effects, whether or not it's waste is a matter of
unsupported opinion which is not based on real
world facts.

John Roth


----- Original Message -----
From: "Ron Jeffries" <ronjeffries@...>
To: <testdrivendevelopment@yahoogroups.com>
Sent: Thursday, May 22, 2008 7:18 AM
Subject: Re: [TDD] Re: The first test - Hardest part about TDD?


> Hello, John. On Thursday, May 22, 2008, at 7:55:45 AM, you wrote:
>
>> I suppose one way to understand Olof's remark is that he starts
>> out creating code as part of the TDD process which is eventually
>> removed completely as he refactors. You could view the removed code as
>> 'waste' I guess.
>
> Sure. Just as when I start my bowling game score method as:
>
> return 0;
>
> and later replace the 0 with
>
> return result;
>
> and insert some result-calculating code up above the return
> statement.
>
> The 0 is waste. However, setting out not to waste that zero turns
> out not to work as well.
>
> So the trick, I suppose, is in learning to keep waste at a low level
> but recognizing that it is wasteful to try to keep it at zero.
>
> Ron Jeffries
> www.XProgramming.com
> There is no award for "being XP". There is an award for doing the
> right combination of practices: success.
>
>