When combined with domain expertise and a strong intuition for the underlying codebase, it can be a good starting point to gut-solve a buggy piece of code a few times before formally researching the corresponding error message.
When used in this way, it may be a valuable technique that is faster than browsing through the Internet searching a particular error message every time.
Although apparently a solution to the problem, it is a fix by pure chance and anything else that changes the behavior of the threads could cause it to resurface — for example on a computer with a different scheduler.
Code added to any part of the program could easily revert the effect of the "fix".
This article is based in part on the Jargon File, which is in the public domain.