<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: rspeele</title><link>https://news.ycombinator.com/user?id=rspeele</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 01 May 2026 08:37:10 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=rspeele" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by rspeele in "Who owns the code Claude Code wrote?"]]></title><description><![CDATA[
<p>It is not even about quality. In fact with an LLM following my orders I can create higher quality code than I ever did before. I always was operating within a budget whether it was defined by the # of hours my customers were willing to pay for, or the # of hours I was personally willing to invest in a side project. This budget manifested in the form of cut features, limited test coverage, limited documentation, and so on. So given the same budget or even a slightly reduced budget I can actually make <i>higher quality</i> software with slop superpowers.<p>If I spend 2 hours designing the domain model, 1 hour slopping out a rough implementation, and 5 hours polishing it with a combo of handwritten and vibed refactorings, I will get a better result than if I spent 8 hours writing everything by hand.<p>So my point is not that vibe software is lower quality, as my experience has shown the opposite. It is simply that the spirit of <i>sharing</i> my work was done with the idea that I was sharing it with others who toiled in the same craft, not sharing for consumption by machine. Not that I ever contributed anything very important to the open source world, that anybody depended on. Just personal projects I thought were neat or educational.<p>In hindsight I would probably still have open sourced what I did, because I think it's valuable to have on record that I competently programmed stuff before AI even existed, like pre-atomic steel. But I don't know if I will open source any personal code going forward.<p>====<p>To put it more succinctly: if somebody "ripped off" my open source code in 2018, I wasn't mad about that. Even if they didn't bother to attribute me, well, at least <i>they</i> saw my stuff, had a human brain cell light up appreciating it, and thought it was worth stealing. I'm flattered. But with LLMs my work can be reappropriated without a single human ever directly knowing or caring about it.</p>
]]></description><pubDate>Wed, 29 Apr 2026 03:49:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=47943982</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=47943982</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47943982</guid></item><item><title><![CDATA[New comment by rspeele in "Who owns the code Claude Code wrote?"]]></title><description><![CDATA[
<p>For another human being to look at my open source code, learn from it, get inspired by it, appreciate what I did, and let it influence their own creativity would bring me joy. That's why I open sourced it in the first place.<p>Few people ever actually read open source code, but I'd like to think on the rare occasions they do, they share a connection with the author. I know when I read somebody else's code, for me to understand it I have to be thinking about the problem the same way they were when they wrote it. I feel empathy with them and can sometimes picture the struggle, backtracking, and eureka moments they went through to come up with their solution.<p>Somehow I don't get the same warm fuzzy feelings about a machine powered by investor money ingesting my work automatically, in milliseconds, and coldly compressing it down to a few nudges on a few weights out of trillions of parameters. All so the machine can produce outputs on-demand for lazy users who will never know of me or appreciate my little contribution, and ultimately for the financial benefit of some billionaires who see me as an obsolete waste of space.<p>I guess I'm just irrational that way.</p>
]]></description><pubDate>Tue, 28 Apr 2026 19:03:11 +0000</pubDate><link>https://news.ycombinator.com/item?id=47938991</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=47938991</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47938991</guid></item><item><title><![CDATA[New comment by rspeele in "AI's economics don't make sense"]]></title><description><![CDATA[
<p>If the price of <i>everything</i> would go down it wouldn't be too concerning and everybody would be on board with the "beauty" of it.<p>What seems to actually be happening for white collar workers is that the price they can charge for their labor is dropping, but the price of their expenses (housing, food, gas) continues to rise.</p>
]]></description><pubDate>Tue, 28 Apr 2026 18:24:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=47938386</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=47938386</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47938386</guid></item><item><title><![CDATA[New comment by rspeele in "Gas Town: From Clown Show to v1.0"]]></title><description><![CDATA[
<p>> Ended up building my own thing that is 10x simpler, just a simple main agent you talk to, that can dispatch subagents, they all communicate, wake each other up and keep track of work through a simple CLI. No « refinery » or « wasteland » or « molecule » or « convoys » or « deacons » or …<p>You won't get 10k stars and a blog post out of that. Obviously you need some Stoats who have Conferences with the Stump Lord  to determine whether they are needed at the Silo or the Bilge. They'll then regroup at the appropriate Decision Epicenter and delegate to the Weasels and Chipmunks who actually do the coding (antiquated term) in the Salt Mine.<p>The Stump Lord is an owl.</p>
]]></description><pubDate>Tue, 14 Apr 2026 22:02:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=47772062</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=47772062</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47772062</guid></item><item><title><![CDATA[New comment by rspeele in "AI singer now occupies eleven spots on iTunes singles chart"]]></title><description><![CDATA[
<p>I can’t tell if this is sincere or parody. It is like you set out to write the most HN take on music possible.</p>
]]></description><pubDate>Tue, 07 Apr 2026 06:31:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=47671435</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=47671435</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47671435</guid></item><item><title><![CDATA[New comment by rspeele in "A rogue AI led to a serious security incident at Meta"]]></title><description><![CDATA[
<p>I sure hope you are right.</p>
]]></description><pubDate>Fri, 20 Mar 2026 02:09:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=47449550</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=47449550</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47449550</guid></item><item><title><![CDATA[New comment by rspeele in "A rogue AI led to a serious security incident at Meta"]]></title><description><![CDATA[
<p>I don't think it will be cost effective to build humanoid robots to do most tangible work. Why assemble an expensive masterpiece of servomotors, chips, plastic and steel, when billions of desperate humans are <i>right there</i> and only cost 2.5 meals a day and a small shelter?<p>Of course, <i>intelligence</i> will be a solved problem so "20 years of training" won't be needed. You'll just be the hardware. AI will tell you to pick up that box, place it on that conveyor belt, place the autowelder at that seam and wait for the green light, turn the wrench to install bolt B in part C. If you don't wish to, or no longer can, so be it. Another, hungrier human will replace you. After all more are made every day, and they are capable of doing this type of labor by age 10 or so. And what else would they do with their time, go to school and get a completely useless education?<p>All of this will of course be in service of our technofeudal lords, the owner class. Some robots <i>will</i> be needed for heavy lifting and for the jobs that are too sensitive to trust a human in, like personal security and strikebreaking. Can't risk trusting a serf for those tasks. But for most physical grunt work humans will be cheaper. Shockingly cheap, when they have no other options.<p>Did that make you less depressed?</p>
]]></description><pubDate>Thu, 19 Mar 2026 21:50:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=47446781</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=47446781</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47446781</guid></item><item><title><![CDATA[New comment by rspeele in "Anthropic takes legal action against OpenCode"]]></title><description><![CDATA[
<p>> I miss the days when open source was...<p>Me too. I also miss the days when I was proud of my little open source projects. Now I just regret donating fuel, even a miniscule amount in the grand scheme of things, to the soulless lawnmower that has already chopped down so much of my joy in work and promises to eventually shred the paycheck, too.</p>
]]></description><pubDate>Thu, 19 Mar 2026 20:31:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=47445582</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=47445582</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47445582</guid></item><item><title><![CDATA[New comment by rspeele in "You’re a slow thinker. Now what?"]]></title><description><![CDATA[
<p>Don't watch Big Fish unless you're ready to cry.</p>
]]></description><pubDate>Tue, 16 Sep 2025 03:56:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=45257880</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=45257880</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45257880</guid></item><item><title><![CDATA[New comment by rspeele in "Robust autonomy emerges from self-play"]]></title><description><![CDATA[
<p>"Why would you need to see it? You're the genius who invented the product in question!"<p>> <a href="https://www.youtube.com/watch?v=9LtT0xZ11wM" rel="nofollow">https://www.youtube.com/watch?v=9LtT0xZ11wM</a></p>
]]></description><pubDate>Fri, 07 Feb 2025 19:05:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=42976232</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=42976232</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42976232</guid></item><item><title><![CDATA[New comment by rspeele in "How I failed to make a game: Raycasting on the GBA"]]></title><description><![CDATA[
<p>This reminds me of playing Ecks vs. Sever on the GBA. A raycasted 2.5d doomlike game based on a crappy movie. It was pretty impressive for a GBA game, and it ran well, never stuttering. It had some pretty cool levels, I remember one where you fight through a hotel using IR night vision. It also had a sequel which added a guided missile launcher and some crazy Robocop ED-209 type enemies. As I recall both had multiplayer deathmatch but good luck finding a friend who also had the game and a link cable.<p>One thing I took full advantage of as a kid was that both games had some cheesy behavior with the sniper rifle scope implementation.<p>In the first game, while zoomed in with the scope you could use the D-pad to move your view a few clicks left/right/up/down to refine your aim. However, this was not really <i>turning</i> you, it acted more like you were a ghost side-stepping and poking his head up and down. So, you could crouch behind a box, scope in on the box, then D-pad up to look over it and shoot an enemy mob who still couldn't see your character and wouldn't engage you. Or stand just slightly behind a corner, scope in, and D-pad right to shoot around it.<p>The last level of the first game involves fighting a boss character who has a powerful weapon and a ton of HP, and is surrounded by his infinitely-respawning goons. There's no way kid me would've beaten it without abusing this trick, which reduces the challenge to avoiding his attacks while fighting enough lower-tier enemies to obtain their precious sniper rifle ammo.<p>In the second game, the D-pad moves a crosshair around a fixed viewport rather than shifting the whole viewport around. So the trick doesn't work exactly the same way. If you zoomed in staring at some obstacle right in front of you, you couldn't move the viewport to see around it like you could before.<p>However... when you zoomed in, it worked like you were a ghost <i>moving forward</i> in space, instead of narrowing your FOV from your original vantage point. So you'd instead stand about 10 feet back from a corner, zoom in past the edge, and voila: you were able to see more around the corner just as if you'd walked up next to it. Sure enough, you could slide the crosshair over and snipe the enemies now visible in your viewport despite your player character still being safely 10 feet back around the corner.<p>Good times. They were still great GBA games even with this exploit, it just made the (scarce) sniper rifle ammo even more valuable to the player.</p>
]]></description><pubDate>Thu, 17 Oct 2024 20:49:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=41873631</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=41873631</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41873631</guid></item><item><title><![CDATA[New comment by rspeele in "Half a century of SQL"]]></title><description><![CDATA[
<p>SQL, C, Javascript: the three kings of "good enough".<p>Bad enough that their flaws are evident even to novice practitioners.<p>Good enough, entrenched enough, that they will be around for the next 50 years too.</p>
]]></description><pubDate>Wed, 05 Jun 2024 03:38:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=40581148</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=40581148</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40581148</guid></item><item><title><![CDATA[New comment by rspeele in "Ask HN: Is Stripe the new PayPal, cancelling user accounts without explanation?"]]></title><description><![CDATA[
<p>I empathize with you. I had a (very small) side business where I was making custom wood grip panels for handguns. On the one hand, these are firearm parts but on the other hand, they are also inert, harmless pieces of wood that aren't needed for the firearms to function. I used Stripe to accept payments. When I originally signed up for the Stripe account I specifically asked customer support whether this would be OK. The response I got (in 2019) was:<p>> Stripe does have some strict rules over the types of businesses we can and cannot support. Firearms accessories is an area that we split into two. Businesses selling firearms and parts required for the functioning of the firearm are restricted from using Stripe. Businesses selling firearms accessories and parts not required for the functioning of the firearm can be fully supported.<p>> As your business falls into the second category, I'm pleased to say that you would be able to use Stripe.<p>In 2022 my Stripe account was closed. I entered an "appeal" quoting that original response and asking whether their policy had changed, or their assessment of the products I was selling. The response I got did not answer that and simply said "we are unable to accept payments for weapons, ammunition, and related products, as mentioned on our restricted businesses list."<p>To be honest I was kind of done with it anyway, it had gotten to that "not fun" point where a hobby becomes a chore. And it wasn't an income stream big enough to make any difference in my quality of life. So I didn't bother appealing further or even seeking an alternate payment provider. But I was still annoyed that they didn't tell me what changed between when I got approval and when I got shut down.</p>
]]></description><pubDate>Wed, 29 May 2024 18:19:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=40515043</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=40515043</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40515043</guid></item><item><title><![CDATA[New comment by rspeele in "Did GitHub Copilot increase my productivity?"]]></title><description><![CDATA[
<p>Lazy loading was a mistake in EF. A lot of apps had awful performance due to lazy loading properties in a foreach loop creating N+1 queries to the database. It would be fine in dev with 50-100 rows and a localhost SQL and blow up in prod with 1000s of rows and a separate Azure SQL.<p>Also if you relied on lazy loading properties after the DbContext had been disposed (after the using() block) you were out of luck.<p>With old EF we would turn off lazy loading to make sure devs always got an exception if they hadn’t used .Include() to bring the related entities back in their initial query. Querying the database should always be explicit not lurking behind property getters.<p>Fortunately with EF core MS realized this and it’s off by default. EF with wise use of .Include and no lazy loading is a pretty good ORM!</p>
]]></description><pubDate>Mon, 13 May 2024 13:56:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=40343443</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=40343443</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40343443</guid></item><item><title><![CDATA[New comment by rspeele in "Marilyn vos Savant and the Monty Hall Problem (2015)"]]></title><description><![CDATA[
<p>[footnote] If this part of the explanation is bugging you, consider these related problems:<p>Problem 1. There are two opaque, externally identical bags, each containing 2 marbles. One bag contains 2 black marbles. The other bag contains 1 black marble and 1 white marble.<p>You choose a bag and draw a marble from it, without looking inside. The marble is black. What should you conclude are the odds that the remaining marble in the chosen bag is black?<p>Answer: .elbram kcalb dnoces a dnif ot ylekil sdriht-owt era ew oS .gab etihw-dna-kcalb eht morf si eno ylno dna ,gab kcalb-lla eht morf era elbram kcalb a werd ew hcihw ni soiranecs elbissop eht fo owT<p>Problem 2. There are three opaque, externally identical bags. One bag contains 2 black marbles. The other two bags each contain 1 black marble and 1 white marble.<p>Again you choose a bag and draw a marble from it, without looking inside. The marble is black. What should you conclude are the odds that the remaining marble in your chosen bag is black?<p>Answer: .tnecrep ytfif era elbram kcalb dnoces a gniward fo sddo ruO .gab kcalb-lla eht nesohc gnivah fo sddo ytfif-ytfif ta won era ew oS .sgab etihw-dna-kcalb tnereffid owt eht morf era owt dna ,gab kcalb-lla eht morf era elbram kcalb a werd ew hcihw ni soiranecs elbissop eht fo owT<p>You can connect Problem 2 to our random door opening and a goat being revealed, in the Monty Fall (with an F) problem.</p>
]]></description><pubDate>Tue, 27 Feb 2024 06:46:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=39520871</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=39520871</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39520871</guid></item><item><title><![CDATA[New comment by rspeele in "Marilyn vos Savant and the Monty Hall Problem (2015)"]]></title><description><![CDATA[
<p>Since this bugged me all day, and I suspect you are the kind of person where it bugged you all day, too, here is a better description of the "fall"/"hall" distinction.<p>I think we can agree that these are the six possible, equally likely, configurations of the problem starting from me having chosen door 1. G1 here is "goat 1" and G2 is "goat 2". For each possible prize behind my chosen door, there are two possible configurations of the remaining prizes.<p><pre><code>    My Door | Door 2 | Door 3
    Car     | G1     | G2
    Car     | G2     | G1
    G1      | Car    | G2
    G1      | G2     | Car
    G2      | Car    | G1
    G2      | G1     | Car
</code></pre>
With the "Monty Hall" problem, Monty uses his knowledge to <i>always</i> open a goat door. Thus we see the following revealed options and resulting 2/3s probability of switching succeeding. This is the classic version of the problem.<p><pre><code>    My Door | Door 2 | Door 3 | Monty Reveals | Switch Result
    Car     | G1     | G2     | Either        | Lose
    Car     | G2     | G1     | Either        | Lose
    G1      | Car    | G2     | G2            | Win
    G1      | G2     | Car    | G2            | Win
    G2      | Car    | G1     | G1            | Win
    G2      | G1     | Car    | G1            | Win
</code></pre>
With "Monty Fall", the first thing that happens is a <i>randomly chosen door</i>, that isn't our own, reveals a goat. This is interesting. In the classic problem we were always going to see a goat next, because those are the rules Monty plays by. But in this case, the fact that we <i>randomly found one</i> wasn't guaranteed.<p>Essentially, you are blindfolded and throw a dart at the 2x6 grid of cells under the headers "door 2" and "door 3", and I tell you that the cell you've hit is a goat. What do you know about the <i>row</i> you hit being a switch-or-stay row? Well, half the possible goats you might've hit are in the first 2 scenarios where you should stay, and half the possible goats are in the last 4 scenarios where you should switch. So you're at 50/50. You don't have any new information to switch on.<p><pre><code>    My Door | Door 2 | Door 3
    Car     | G1(a)  | G2(b)
    Car     | G2(c)  | G1(d)
    G1      | Car    | G2(e)
    G1      | G2(f)  | Car
    G2      | Car    | G1(g)
    G2      | G1(h)  | Car
</code></pre>
You are just as likely to be looking at (a), (b), (c), or (d) (so you should stay) as you are to be looking at (e), (f), (g), or (h) (so you should switch). It is 50/50 in this version of the problem.[footnote]<p>This may make it confusing going back to the original. I seem to have shown that both ways make sense but still, how is it different? Imagine it like Monty is doing a random dice roll for which door to open, and he simply juices the outcome by correcting it to the goat door when a car door is selected, since he can't reveal a car and spoil the game. Now we have these equally possible scenarios (a) through (l) for his fair dice roll...<p><pre><code>    My Door | Door 2 | Door 3
    Car     | G1(a)  | G2(b)
    Car     | G2(c)  | G1(d)
    G1      | Car(e) | G2(f)
    G1      | G2(g)  | Car(h)
    G2      | Car(i) | G1(j)
    G2      | G1(k)  | Car(l)
</code></pre>
Which he corrects, avoiding cars, to:<p><pre><code>    My Door | Door 2 | Door 3
    Car     | G1(a)  | G2(b)
    Car     | G2(c)  | G1(d)
    G1      | Car    | G2(f,e)
    G1      | G2(g,h)| Car
    G2      | Car    | G1(i,j)
    G2      | G1(k,l)| Car
</code></pre>
Now we are back to the original game scenario where we see a goat no matter what. And we can see that 8 of the possible ways we might have arrived at seeing this goat come from "switch" rows while 4 come from "stay" rows.</p>
]]></description><pubDate>Tue, 27 Feb 2024 06:17:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=39520716</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=39520716</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39520716</guid></item><item><title><![CDATA[New comment by rspeele in "Marilyn vos Savant and the Monty Hall Problem (2015)"]]></title><description><![CDATA[
<p>They are two different problems. Map out all the scenarios exhaustively and you'll find the difference.<p>In both cases we were originally 1/3 chance of being right. That is not in dispute.<p>In the original (fully defined) "Monty Hall", Monty was going to show us a goat no matter what. It's part of the rules, he <i>has</i> to show a goat. So the fact that we see a goat behind the revealed door is no surprise, and no new information. But <i>which</i> of the two unchosen doors was the goat, is valuable information because in 2/3s of the scenarios Monty's hand was tied and he HAD to show that door to avoid revealing the remaining car.<p>In the "Monty Fall" problem, the fact that <i>we see a goat at all</i> is interesting information. This becomes more likely when we picked the car in the first place, because if we had initially picked the car, and a random other door is opened, it's 100% going to be a goat, whereas if we had picked the goat in the first place, we are only 50% likely to see a goat when a random other door is opened. Let's call the goats Alice and Bob to illustrate this point. We know we DID see a goat, but we don't know which of these equally probable scenarios led to that:<p>1. We picked the car and saw Alice<p>2. We picked the car and saw Bob<p>3. We picked Alice and saw Bob<p>4. We picked Bob and saw Alice<p>Notice how "we picked the car" originally had 1/3 odds but represents half the scenarios that remain possible, because there are <i>two</i> ways to see a goat with that start, while only <i>one</i> way to see a goat with the others.<p>This kind of brings the problem back around to similar territory as Bertrand's Box[0] where <i>the fact that you drew a gold coin</i> is already hinting to you that you're more likely on the "both gold" box than on the "half gold" box.<p>[0]<a href="https://en.wikipedia.org/wiki/Bertrand%27s_box_paradox" rel="nofollow">https://en.wikipedia.org/wiki/Bertrand%27s_box_paradox</a></p>
]]></description><pubDate>Mon, 26 Feb 2024 22:57:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=39517831</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=39517831</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39517831</guid></item><item><title><![CDATA[New comment by rspeele in "Marilyn vos Savant and the Monty Hall Problem (2015)"]]></title><description><![CDATA[
<p>> It doesn't make a difference what causes Monty to reveal a goat.<p>Oh, but it does! See the "Monty Fall" version of the problem, in which Monty accidentally trips and opens a door, which just <i>happens</i> to reveal a goat. In this variant there is no advantage gained by switching, because no more information was revealed about the remaining unopened door.<p>The information gain only happens in the original game because we know that Monty was <i>forced to avoid</i> the winning door in the (66% likely) case where we didn't already pick it.</p>
]]></description><pubDate>Mon, 26 Feb 2024 21:09:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=39516784</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=39516784</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39516784</guid></item><item><title><![CDATA[New comment by rspeele in "Marilyn vos Savant and the Monty Hall Problem (2015)"]]></title><description><![CDATA[
<p>I am curious how you feel about the "Monty Fall"/"Monty Crawl" problems linked elsewhere in the thread.[0]<p>For my part I am somewhat sympathetic to jncfhnb's point. The exact phrasing that Vos Savant was asked did not specify the rules that the host <i>was required</i> to open a door, nor that it <i>always</i> must be a goat door. It simply says that the host has knowledge of what's behind the doors, and <i>in this particular iteration of the game</i>, he showed you a goat and asked you about switching.<p>That does not exclude a scenario where the host is a manipulative fellow, who chose to show you the goat only because he <i>knows</i> you are about to win, trying to convince you to lose. A contestant on the real show would surely worry about this possibility.<p>Of course, the people who wrote to disagree with Vos Savant almost never said "the problem is not fully stated", they said "it's 50/50 you fool", which isn't right. Additionally, since it wouldn't be a math problem at all if we let the host have agency, it is reasonable to assume the unspoken rule that he does not, leading to Marilyn's correct 2/3rds answer.<p>[0]<a href="https://web.archive.org/web/20230706235720/https://probability.ca/jeff/writing/montyfall.pdf" rel="nofollow">https://web.archive.org/web/20230706235720/https://probabili...</a></p>
]]></description><pubDate>Mon, 26 Feb 2024 20:43:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=39516552</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=39516552</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39516552</guid></item><item><title><![CDATA[New comment by rspeele in "Marilyn vos Savant and the Monty Hall Problem (2015)"]]></title><description><![CDATA[
<p>One way to think about is, suppose you switch -- why not switch <i>back</i>?<p>In the random-open case, you really know nothing new about either of the closed doors. If you can talk yourself into switching, you could make an equally good argument for switching back.<p>In the Monty-knows-and-always-shows-goat case, you have gained information about one of the closed doors. You haven't gained any information about your initial pick door. But the other remaining door, you know there's a 2/3rds chance that Monty was <i>forced</i> to avoid it so as not to reveal the car. Only in the 1/3rd case where you were already on the car does Monty have freedom to open either door willy nilly.</p>
]]></description><pubDate>Mon, 26 Feb 2024 18:59:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=39515448</link><dc:creator>rspeele</dc:creator><comments>https://news.ycombinator.com/item?id=39515448</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39515448</guid></item></channel></rss>