@nprofile1q... I like comparing reflective thoughts to operating with a debugger: it's much slower than normal operation, particular behavior quirks that happen without it may not happen at all, and even when they do, it's not often obvious which parts of the system cause them. And the debugger's UI you're seeing only presents you with a piece of the full picture, a pretty big one, that. You might need to place additional probes outside to see more.
You'll accept the result if the picture you see matches what you want, but catching some unintended side effects later in parts you weren't looking at at the time is pretty common.
I can't recommend this analogy to *everyone* because not everybody has that kind of debugging experience, but I know plenty of people that do.
And it might be somewhat transferable to diagnostics of other complex systems. I remember watching Louis Rossmann's board repair streams before his RtR crusade, and I remember seeing very similar reasoning methods there.