There is a related puzzle which I've also heard called the Two Envelopes Problem. The premise is that you are handed two envelopes. Inside each envelope is a piece of paper with a number written on it. I have written down these numbers by sampling from some probability distribution, but you don't know what it is. All you know is that the two numbers are different. You get to pick one envelope and then look at the pap…
Two envelopes problem
71–80 of 318 posts
Re: Two envelopes problem
#72change your mind as many times as you like, there will only ever be one actual choice
Re: Two envelopes problem
#73I love this problem because it is so simple, and the false line of reasoning is so compelling that it would hardly raise an eyebrow if you saw it in an academic paper and yet the conclusion is so obviously wrong. Decision problems are tricky and in non intuitive ways.
This reminds me of how chess tactics feel so obvious when I’m on a tactics trainer, yet I can’t identify them in games where they actually happen. Or code that “obviously” has a bug only after it caused an issue in production. Would be nice if someone warned me before I do a PR: “ok, fyi there is a subtle but devastating bug in the new_feature.cpp”
Re: Two envelopes problem
#74Re: Two envelopes problem
#75What an interesting trick. A starting point to intuit a resolution: yes you have a 50% chance of doubling and a 50% of halving. But the doubling only happens if you have x dollars, and the halving only happens if you have 2x. So you can see you either gain x or lose x, so your expected return is 0. When the amount you multiply your money by depends on the amount of money you currently have, you have to factor in your…
Re: Two envelopes problem
#76I love this problem because it is so simple, and the false line of reasoning is so compelling that it would hardly raise an eyebrow if you saw it in an academic paper and yet the conclusion is so obviously wrong. Decision problems are tricky and in non intuitive ways.
This reminds me of how chess tactics feel so obvious when I’m on a tactics trainer, yet I can’t identify them in games where they actually happen. Or code that “obviously” has a bug only after it caused an issue in production. Would be nice if someone warned me before I do a PR: “ok, fyi there is a subtle but devastating bug in the new_feature.cpp”
Cognitively, the mind filters out quite a bit of information for performance reasons.
Are we biased in favor of reasoning that "sounds plausible"?
My "hot dice" say "yes".
Re: Two envelopes problem
#77https://www.youtube.com/watch?v=0yjVv_iB1h0 (Interestingly, a lot of those DoND comments have gone. Did they delete them?)
Re: Two envelopes problem
#78Normally we would assume there is someone who owns the envelopes of money. Now their incentive could be to offer to switch only if the envelope you chose contains more money (so they have a chance of keeping more). More like Monty Hall.
Even without that, after switching, should you switch back? The equation given argues you should switch back, so obviously the equation must be wrong.
It is easier to think: if I switch I have a 50% chance of making $X and a 50% chance of losing $X. Switching doesn’t change expected $.
I actually think the later problem in the Wikipedia article is more clever:
Two people, equally rich, meet to compare the contents of their wallets. Each is ignorant of the contents of the two wallets. The game is as follows: whoever has the least money receives the contents of the wallet of the other (in the case where the amounts are equal, nothing happens). One of the two men can reason: "I have the amount A in my wallet. That's the maximum that I could lose. If I win (probability 0.5), the amount that I'll have in my possession at the end of the game will be more than 2A. Therefore the game is favourable to me." The other man can reason in exactly the same way. In fact, by symmetry, the game is fair. Where is the mistake in the reasoning of each man? — "Martin Gardner: Aha! Gotcha"Re: Two envelopes problem
#79That is, the probability is 1/2. That's all that matters to the decision making. Calculating an "expected value" at all is completely useless, whether or not you do it "correctly".
Am I missing something?
Re: Two envelopes problem
#80Earlier quoted context omitted.
Well, the simple way to put is that "A" isn't fixed. The "expected value" argument in steps 6-7 is acting like "A" is a single value when "A" will be larger or smaller depending on what envelope you picked.
Yeah, that's obvious when they say "one envelope contains 2*A and the other A/2". Well no, one doesn't contain one fourth of the other.