> Tears apart your weak reasoning until only truth remains

I've done that to myself quite some times when writing a very detailed report on an issue. Back in the day of stackoverflow (godbless and godspeed, glad Joel made it out and sorry for the investors) you had to be detailed to maximize on your initial viewers.

I think the idea is the same with the rubber duck debugging method although I've never tried it myself.