Needless to say i’m talking about the oversimplified and misleading version of the Schrödinger’s cat paradigm, where he is both dead and alive until you watch it.
I don’t have a job but i follow theater courses at an academy. And my improvisation is both funny and awful until i show it to others.
Well, I work as a bartender, and here in Finland it’s strictly against the law to serve alcohol to, or even allow a “visibly intoxicated person” to enter the premises (a law which almost every bar breaks at some point, intentionally or no), and I think I’ve witnessed multiple times myself how a customer’s level of intoxication reveals itself only after you have served a drink to them and they’ve payed for it. Could it be called a Schrödrinker’s cat?
The Heisenbug. Once you try to observe this kind of software bug with your technical means, it simply goes away.
Not quite Schrödinger’s cat, but in programming we have Heisenbugs named after Schrödinger’s peer.
It’s when you have a bug/crash that is not reproducible when debugging it. Might be that you’re reading some memory that you’re not supposed to, and the debugger just sets it up differently. Maybe you have a race condition that just never happens with the debugger attached.
Employee salaries in HR; they are both correctly paid(employer perspective often), underpaid (employee perspective often), and overpaid (company and co-worker perspective). Depending on how and how often you open the box, any of these views can be accurate.
The drill bit is good, until you get it to surface.
As a bicyclist, I see that we have Schrödinger’s Cyclist: Too poor to be able to afford a car like “normal” people, but also a rich elitist who can afford to commute by bike.
Also, Schrödinger’s Bike Lanes: A conspiracy by car-hating politicians to punish drivers, but also an amenity that only rich elitists get in their neighborhoods.
For work I use a database written in COBOL. Reports are simultaneously running and frozen until I either get the report results or sufficient time has passed that I’m certain the system has crashed.
Isn’t that the halting problem?
A textbook example, yes. And Today I Learned something!
What thinking about a close one. Some Application and servers are OK and KO as long as you don’t look at it
I guess the best one for me may be elite university students are “just smarter” than others until I have to read their term papers.
For some reason it’s always the non-native English speakers who write well.
Autonomous vehicles are at times both amazingly advanced and bedshittingly idiotic.
I’ve ridden ~25k miles in them for work, and I trust them more than 95% of the drivers on the road. But I’ve also experienced them acting in ways that are still quite far from the way humans would.
Code is both great and terrible until it compiles.
In programming there is also the Heisenbug: as soon as you try to observe the bug, it disappears or changes its behavior.
I fucking hate Heisenbergs!
Hrm, weird reproducible bug. Ok let’s hook up the ol’ debugger and… Where did the bug go? Shiiiiiiit.
My company is basically 30 startups in a trenchcoat. The bulk of our my org’s application was written 5-10 years ago by like 4 dudes, none of whom work at the company anymore. Cowboy coding doesn’t come close. We have so much legacy code and I alternate between “how the fuck does this work” in an impressed way and a horrified way anytime I look at it
Print jobs are both completed successfully and failed until someone checks the queue.
A person that has a lot of certs or a high title is both extremely smart or extremely unintelligent. You don’t know until you start talking with them about things more than surface level.
Projects will either be done next month or take at least a year to complete. Also, if you ask my team to calculate how long a project will take, and then ignore the estimate, the project will take infinite time because you are an insufferable moron.
The contrast is either too little or too much and I won’t know unless I look at the drawing again the next morning
Software both works perfectly (on the developers machine and most deployed instances) and fails dramatically (on some significant subset of deployed instances).
This makes the software both a success (since it works, and can generate revenue) and a failure (since it is unreliable, and may alienate paying customers).
