As a non physicist, this always seemed to be the most logical explanation of the double slit experiment. The particle by default carries out all possible variations weighted by their likelihood of happening, so you get the wavey pattern like a normal distribution. By measuring it at an earlier point, we restrict ourselves to the outcome of only one of its possible pasts.
Measuring something doesn't change its behavior, just the range of possibilities.
Nobody really doubts that some art fails because its just not good. Differentiating art that is technically superb to art that really resonates is a more interesting conversation.
I do game dev. It's very easy to think "this animation could be better". It's a lot harder to figure out "could this be made more fun". Tactics vs strategy.
My impression is that aside from some crazies who generally get downvoted unilaterally, you rarely see antagonistic opposition to saying Tesla is overvalued. This doesn't hold if you instead make a meta observation that claiming it's overvalued would earn antagonism.
It's not that surprising. The former is voicing an opinion. The latter is effectively just a pre-emptive insult to everyone who disagrees with you.
Similar arguments hold for any popular unpopular opinion.
What do you mean by this? I'm imagining, say, rainfall per day, with a column for date, and a column for rainfall. What's useful about getting the data as it was vs. just having a total dataset with accurate dates.
For something as simple as a sensor reading, you're right, the most natural way to store it is basically an append-only time-series database so it doesn't require much special care.
But say the Rainfall table had a foreign key to a Sensor table that had the coordinates of the sensor. If the physical sensor were moved, the most straightforward data schema would call for the coordinates for the Sensor table to be updated, but then the historic data would have the wrong coordinates if you did a join.
The ideal solution is to design a bitemporal schema so that rows are only ever inserted, not updated, but failing that, regular automatic database snapshots are a good start.
How do you plan to handle players that others don't like? That's a fairly common problem for TTRPGs. You'll see a question every other day on rpg stack exchange about a troublesome player. Off the top of my head
* Players who don't play fairly
* Players who are rude
* Players who break game norms, like always wanting to detract from what the group wants to do ("It's what my character would do in this situation")
* Players who role play too hard in boring ways (e.g. overly philosophical debaters)
* Players who are overtly sexual
* Players who make off color jokes
* Players who aren't engaged enough
* Players who are selfish or antagonistic
* Players who others cannot understand due to language / accents
* Players who are racist/sexist/make unwanted advances irl
Watching someone else's VR view on a TV isn't too bad.