> Reminds me of a strategy for solving difficult debugging problems, i
> used to teach to developers. We called it "teach a monkey", meaning,
> explain it to an outside person, a spouse or kid might do, because their
> attention and willingness to understand forces YOU to slow down and more
> often than not, this leads to the discovery of the mistake in thinking,
> that lead to the bug. :-)
https://en.wikipedia.org/wiki/Rubber_duck_debugging
Stefan