News for hackers. Stuff that matters.
Re:Show HN: Understanding the Monty Hall paradox through code by andischo on Sunday March 29, 2020 @06:17AM (#22717754)
The easiest explanation I've ever heard and which immediately made me understand it was the following:

Instead of 3 doors, imagine there are 100. 99 of which have a goat and only one of which has a price behind it. Now blindly choose a door and the host opens 98 of the other doors which have a goat behind it. Would you switch your door now, given the choice?

It's easy to see that your probability of choosing a "wrong" door when you had 100 doors to choose from was much higher than choosing the right door when you only have two doors to choose from.

This method of thinking, i.e. increasing or decreasing the problem space by some orders of magintude has helped me a lot in thinking about problems and their solutions in general.

Re:Show HN: Understanding the Monty Hall paradox through code by BrandoElFollito on Saturday April 11, 2020 @12:09PM (#22842379)
This does not (at least to me) explain why a switch is interesting.

The probabilities are different but this does not make my first choice "worse"

Re:Show HN: Understanding the Monty Hall paradox through code by svantana on Sunday March 29, 2020 @11:07AM (#22719582)
I also do this, among other things to find subtle bugs in code and math. For every unbounded variable, what happens if it is 10^100, or 10^-100? It's a good habit that also makes you view division and logarithms with great suspicion :)
Re:Show HN: Understanding the Monty Hall paradox through code by ken on Sunday March 29, 2020 @12:48PM (#22720423)
One of my first computer science teachers pronounced "/" (in C) as "divide and throw away the remainder", which sounds awkward at first but turns out to be quite helpful. It's one of those operators which, unfortunately, looks just like one from math class but acts very differently, even in common cases.
Re:Show HN: Understanding the Monty Hall paradox through code by l0b0 on Sunday March 29, 2020 @06:41PM (#22723452)
Good idea, but it's not intuitive why the original problem is equivalent to the host revealing N-2 (98) goats rather than, say, (N-2)/2 (49) or 1.
Re:Show HN: Understanding the Monty Hall paradox through code by abiogenesis on Sunday March 29, 2020 @08:49PM (#22724211)
Interesting. I was explained this question the exact same way (100 doors) some years ago and it was instantly intuitive to me. Maybe it's how every brain works differently.
Re:Show HN: Understanding the Monty Hall paradox through code by l0b0 on Tuesday March 31, 2020 @05:28AM (#22736054)
I understand that it makes sense intuitively, but how do you justify it to yourself mathematically? As far as I can tell there is nothing in the original formulation that explains why it would scale that way.
Re:Show HN: Understanding the Monty Hall paradox through code by overcast on Sunday March 29, 2020 @10:14AM (#22719143)
Sure but making it 99/100 just increased your odds significantly from 2/3.
Re:Show HN: Understanding the Monty Hall paradox through code by millstone on Sunday March 29, 2020 @06:29AM (#22717800)
I'm the host, and I also happen to be blind. I chose 98 doors and none of them have the car - terrible luck on my part! But probably this lends some credence to your initial guess?
Re:Show HN: Understanding the Monty Hall paradox through code by Retric on Sunday March 29, 2020 @10:15AM (#22719152)
This is correct, but based on specific assumptions. If the host flipped a coin and selected a door and 1/Nth of the time it had the car then you switching would not change your odds.

Similarly, an adversarial host who sometimes opens a door and sometimes just shows you your choice can similarly mess with the odds.

It’s really due to the host both being forced to show a door and knowing which door to choose that you gain from leveraging that knowledge.

Re:Show HN: Understanding the Monty Hall paradox through code by roenxi on Sunday March 29, 2020 @07:03AM (#22717974)
No, if the host is acting randomly no information was revealed. It is equally likely that the car is behind your door or the other door.

The player are indifferent to switching under your scenario. Why not, I suppose?

Re:Show HN: Understanding the Monty Hall paradox through code by andischo on Sunday March 29, 2020 @06:45AM (#22717877)
That is also a very interesting way to think about it, if I understood you correctly. Seeing the host as another player, any "bad luck" he has, should translate into myself having a higher chance of success if used correctly.
Re:Show HN: Understanding the Monty Hall paradox through code by hanoz on Sunday March 29, 2020 @07:42AM (#22718185)
With the host as another blind player, his opening of 98 goat doors only increases the probability you were right from 0.01 to 0.5, so still makes no difference for you to change. But of course the original version of the problem is predicated on the host knowing where the car is and only revealing goats.