>> 3. Describe the problem to someone unfamiliar with it.
>> 
>> A lot of the time, the third party doesn't even have to say anything - 
>> just the act of describing the situation reveals some high-level error.
>
>This is a very powerful technique which I use a lot - 
>I call it "cardboard cutout debugging", 

Sounds like a pretty good name for it ...

>because as you say, they can just sit there and say 
>nothing, it's the act of rephrasing the problem so 
>someone else can understand it that "explains" it to 
>yourself and makes you think of it from another angle.

Yeah, done it many times myself too.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist