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?
Not related to the Schrödinger question, but my advice for solving that problem would be to have some little robots trundling about with boxing gloves on. They can randomly harry each your walk-ins with a sudden flurry of blows. By seeing how these people handle the unexpected robotic assault, you should better be able to assess their level of inebriation.
In computer programm single threaded programs are pretty predictable (apart from human errors). As soon as you have multi threading that goes out the window. Modern CPUs in most devices you use have what’s called a scheduler that schedules when to let different things actually use the CPU so you can actually do multiple things at once. It’s a super important concept for what we want to do with devices. But because of that you have no guarantee about when (or if) other threads of your own code will execute. Apart from truly insane edge cases, single threaded programs act pretty deterministically. Multi threaded ones do not. It’s very similar to the “it’s alive and dead until you check” idea because you just don’t know. So much so that there are data types we use called things like Maybe where the result is either a success or a failure and you write code for both.
Also much like the cat in a box thing, programmers don’t really view it as magic, it’s just sort of a side effect of the uncertainty.
Is it actually non-deterministic or just too many variables and too much sensitivity to initial conditions influencing the scheduler’s decisions for the programmer to reasonably be able to predict?
It is deterministic, it is just determined elsewhere.
If thread 1 is working on a task and needs the output of thread 2, it doesn’t know what the output is. Of you move the tasks from thread 2 back into thread 1, then you have eliminated the point of multi threading.
Without getting philosophical, I’m going to say human behavior is non-deterministic. Because a human is using a computer you cannot reason about what may be running when. That’s why I say it’s non-deterministic. You can make an argument that a non real time computer not connected to the Internet could be considered fully deterministic, but it’s really just a distraction. That’s why I tried to make it clear I wasn’t talking about “magical ‘truly’ random” things.
I’m not trying to get overly technical or philosophical lol. For example, PRNGs are deterministic, but it’s sufficiently random that we treat it as random without worrying about whether it’s “actually random.” (But yes, there can be bugs where they actually are behaving too predictably and they actually aren’t random. This is why I’m trying to keep the topic simple without getting lost in the details.)
When you account for not knowing what else is going on the system I’d say it’s actually non deterministic. But not in a magical “truly random” sort of way, just that other things you don’t personally have control over are going on. If this topic interests you then you may want to look into real time computing which is an area where you do have deterministic systems where you can more accurately guarantee how long something will take. This is important in dangerous activities. Think things like nuclear reactors where a process taking too long might mean not alerting another part of a system that something bad has happened. Like the part of the system that tells you if something is too hot not responding so you keep adding fuel. Compare this to your phone. If your phone is slow then, well, it’s just annoying really.
As an animator, the client simultaneously knows everything about what makes a good animation, colour theory etc. and is utterly incapable of doing it themselves or providing any specific feedback beyond “I don’t like this” or “make it feel more pink but don’t actually make it pink.”
This state persists until you introduce an invoice for all the extra work it’ll take to redo all the stuff they agreed to two weeks ago, and then the waveform collapses and suddenly everything you sent them in the first place is fine.
I tried to get chatgpt to draw me a “coffee shop that feels pink without actually using the color pink”.
It failed (used the color pink):
Then I made the same request with the color green. It failed again, but I like this “non-green but actually green” coffee shop.
I also like the ridiculous position of those two chairs.
As a Set Dresser/On set dresser - any set build before a director sees it/ wideshot films it.
How it generally works is we get a bunch of stuff and… Something. This something can be as exact as a blueprint (techpack) that clearly marks where furniture is supposed to go or as vague as a one sentence long description of what the set is supposed to be. We are usually given a bunch of options for virtually everything that is used. Then we make up the set.
Then the waveform goes nuts. The Heirachy goes Set Decorator, Production Designer, and then Producer. They will randomly visit or call in sometimes separately and whatever plans that existed immediately cease to matter. The set may completely change a random number of times back and forth as anyone above us in the hierarchy demands unless it countermands a specific demand made by someone above the demander in the hierarchy.
That is until shoot day. Once the Director has the floor all of that prep goes immediately out the window and the director may change whatever they please about the set and while there’s usually too much time constraints to change everything it could mean getting rid of anything. The waveform only collapses to depict a singular reality once the wideshot is in the bag which means there is now a continuity that must (okay “must” is a strong word) be obeyed.
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.
