5 whys is my go-to debugging strategy for truly mysterious software and systems bugs.<p>The rubber hits the road at the point where you have an answer like &quot;one of A, B, or C occurred&quot; and you don&#x27;t know which because none of them are ever supposed to happen :) you know you&#x27;re within a clue-bat-swing-radius of the problem then.