Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Here's a reply to the article: (I haven't verified for mathematical correctness)
"The "(and only one)" qualification suggested by Ralph Dratman is _not_ required. Indeed, in the first case of the analysis, "older child is a boy born on Tuesday", the possibility that the younger child is also a boy born on Tuesday is explicitly included and counted. The hypothesis for the second case does exclude the possibility of both being boys born on Tuesdays. The two cases are mutually exclusive and exhaustive.
Note that if the puzzle had included the "(and only one)" qualification, then the possibility count would have been 13 (6 for boy and 7 for girl) in both cases, and the probability drops to 12/26."
You still have to make sure that execution of an old version thread, and a new version thread at the same time doesn't break anything though.
Of course coldpatching doesn't have to worry about any of this, so the whole "version" functionality and keeping old code only need apply to the hotpatching, not the coldpatching