Fascinating. And happened very close to where I am sitting as I write this.

This sort of error corresponds to a classic computer programming debugging error - you decide incorrectly what the cause of a problem is, and then "fix" it, without actually verifying the true cause.

Sometimes the fix "helps", but of course it won't actually fix anything permanently.

I have gotten good at avoiding that sort of error. Of course, I have the advantages of all the time I need, and the chance to have made lots of errors in the past and learned from them without splattering myself all over a field...

(Yes, that's what the simulator's for, you're right...)