Was this word invented by google
When something that was working, suddenly doesn't work when demoing to others
41–50 of 54 posts
Re: When something that was working, suddenly doesn't work when demoing to others
#42[deleted]
Re: When something that was working, suddenly doesn't work when demoing to others
#43Earlier 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.
That term definitely applies to any demo that behaves differently than previously observed - subtly implying that the demo setting has something to do with it.
Re: When something that was working, suddenly doesn't work when demoing to others
#44It's fascinating to me how German composite words encapsulate an idea like "[failure attributed to] demonstration effect" in a way that just saying "demonstration effect" in English often fails to accomplish. I also love how German often has useful opposites - schadenfreude vs fremdschamen, for example. On that note, is there an opposite to this, where someone observes that something's not working, they call in the e…
We sometimes use the term Houdini in my field for difficult-to-reproduce problems, but not exactly as an antonym to Vorführeffekt.
German dev here, we frequently filed this just as well under Vorführeffekt, probably even more frequently than the "standard" variant.
Re: When something that was working, suddenly doesn't work when demoing to others
#45In my company we call these "Show & Fail".
They often occur because we'll say "I just want to fix this one thing before we build the demo". We call this type of commit to the source control system a "break-in" instead of a "check-in".
Re: When something that was working, suddenly doesn't work when demoing to others
#46What's the word for this: * My code doesn't work and I can't find the bug even after over an hour * I add a few lines of . Now it works! * Now, just for comparison, I remove all the code I just added (or, at least I think I reverted back to previous state). But now it still works. ???
cache?
Re: When something that was working, suddenly doesn't work when demoing to others
#47What'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" ?
Re: When something that was working, suddenly doesn't work when demoing to others
#48Earlier quoted context omitted.
Is the word only for unpleasant surprises, or for all such situations, even when the surprising outcome is also a good one?
i've never seen it used for pleasant surprises. its basically if you want to show something (even something that does not work, like the engine-not-starting) and the demonstration does not work as expected.
They only have to be "unpleasant" in some aspect, for example because you now annoyed/bothered you team lead.
The unexpected behavior itself can still be desired, with the unpleasantness restricted to the demonstration itself.
Re: When something that was working, suddenly doesn't work when demoing to others
#49Earlier quoted context omitted.
Self-fulfilling prophecy?
I mean attempting to demonstrate something broken, only for it to work properly.
As already said: Vorführeffekt is neutral and could mean both: success and failure. But the opposite of „a performance with an opposite than expected outcome“ is something that comes out exactly as it’s supposed to be without intervention, right? ;)
Re: When something that was working, suddenly doesn't work when demoing to others
#50What'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" ?
That's a temporary system stall when some critical part of the system is overloaded or blocked, usually the disk.
Or an out-of-memory condition, the system recovers when the OOM killer has killed a random process. If you were lucky that process was your game hogging ressources and when it went away the system recovered.
And for impressive German words? "Systemaufstauung mit urplötzlicher Lösung" (system bottleneck with sudden resolving), "Speicherüberlastung" (memory overload) or "Prozessabmurkser" (process terminator).
Note that I invented these words (oder auf gut Deutsch, ich habe mir diese Wörter aus den Fingern gesaugt).