While I don't completely agree with the parent post, I don't think that your reply does it justice.
If you see something that can't possibly be interacting with your problem...
I think that "can't possibly" is the source of trouble. Today it's practically impossible to say with certainty what is actually impossible. There's so much going on at a lower level that's not visible to us, from network routing completely outside our systems, to the internal workings of many large APIs and frameworks, that there's plenty of room for things to happen in ways that are unlikely to us, but in retrospect after we've researched, do fit together.
I guess I just assumed that everyone researches everything. Doesn't everyone look into how network routing works, or how every large API or framework is implemented, etc? If you're running into a bug, and that bug can possibly be affected by any of those things, then you have to dive all the way to the bottom of the swimming pool to see if there's something amiss.
Yes, we do that. But we also have learned, the hard way, to have some humility with that knowledge. Something may disagree with our mental model, but we're careful not to say something is impossible because our mental model may be wrong. (In fact, it is wrong, since we're dealing with a bug.)
If you see something that can't possibly be interacting with your problem...
I think that "can't possibly" is the source of trouble. Today it's practically impossible to say with certainty what is actually impossible. There's so much going on at a lower level that's not visible to us, from network routing completely outside our systems, to the internal workings of many large APIs and frameworks, that there's plenty of room for things to happen in ways that are unlikely to us, but in retrospect after we've researched, do fit together.