Earlier quoted context omitted.
There's the alternative: * The program works flawlessly * Somebody finds a bug on the code that is executed in a test * The relevant test now fails consistently Both are probably because you changed something on the environment when you looked at the code.
Another common cause is that the code you were looking at wasn't actually the code you were running. Between "I added this line and then I removed this same line, and now it works", the executable might have been recompiled.
When something that was working, suddenly doesn't work when demoing to others
51–54 of 54 posts
Re: When something that was working, suddenly doesn't work when demoing to others
#52Earlier quoted context omitted.
I mean attempting to demonstrate something broken, only for it to work properly.
Wouldn't this term still apply? If the goal of your demonstration is to show failure, and then that succeeds, that makes your demonstration a failure.
Re: When something that was working, suddenly doesn't work when demoing to others
#53Because this happens a lot to me these days, no kidding. The bug happens, some user delights in calling me over, I take a look, they simply can't reproduce it, I walk away - they get the bug again - and, yeah, I kind of have to race ahead of things to understand the nature of the users situation.
Happen to anyone else? I don't think its quite like Vorführeffekt, and is maybe a bit more like Daseinsvermögung oder etwas ..
Re: When something that was working, suddenly doesn't work when demoing to others
#54What's the equivalent word for "Your computer suddenly becomes slow and unresponsive, you try to open Task Manager (or run `top` in a terminal) to see what's bogging down your resources, but the resource monitor itself refuses to respond for a few seconds until the lag vanishes, at which point the utility finally renders and everything under the CPU/Memory utilization appears normal" ?