1,372 karma · joined June 3, 2007
psyonic (at) gmail (dot) com
https://www.elastic.co/blog/elasticsearch-2.0.0.beta1-coming...
"not many but more than one."
This python gist appears to simulate the situation correctly, and shows that it becomes 50/50.
https://gist.github.com/ecdavis/da8f67258860e9f35620
That said, I'm not sure I completely agree with this solution just throwing out cases where he opens the winning door, without replacement. I feel like at this point we're calculating a different problem where we haven't precisely defined what it is we're measuring, so you could tweak things to get either answer.
This isn't quite right. Obviously if there's a chance Monty might open the car, it screws up the gameshow, but it doesn't actually change the odds in the situation that he opened a door with a goat.
The knowledge in Monte's head doesn't change the odds.
To simulate this properly, you'll need to change the problem statement somewhat... you'll either have to throw out cases where he opened the door with the car, or state the problem such that we're only look at cases where he randomly opened a door with the goat. But you'll still get 2/3.
Assuming nothing happens to him, he's just broadcasted what happens to those who come after him.
Also, my girlfriend teaches at Zipfian Academy (http://www.zipfianacademy.com/), a data science bootcamp, and so far they legitimately have a 100% placement rate. I'm sure they won't keep that up forever, but they do a great job preparing their students. Theirs is a little different, however, as they expect some prior programming and a fair amount of math, so it's fairly difficult to get into.
When I was younger, I used to visit slashdot and skip directly to the comments without bothering with the articles. The meta-discussions were generally the most interesting part. Not all sites are youtube.
Used quite pleasantly by Rapture JSON: http://rapture.io/jsonSupport
They look the same as normal logging function calls, but entirely avoid the issue of "logging guards."
I'll point you at a good link, but basically if you have a lot of calls to logger.debug, logger.trace, etc, and they involve a lot of string conversions, you pay the penalty for those string conversions all the time even when you're logging at warn or higher. This leads many java developers to do the following:
if (LOGGER.isDebugEnabled()) { LOGGER.debug("last node was: " + node); }
... which makes logging significantly heavier visually.
With a macro you are essentially adding syntax, so you can bake the guards into your log statements.
Logging guards: http://www.kdgregory.com/index.php?page=java.logging
This is an iPhone (non-jailbroken.) Are you saying the official CoinBase app had a trojan? Or Authy, the most widely used 2FA app?
If you're actually curious what I think they should do, we could talk about it, but I don't think you care beyond blaming the victim.
What I don't understand is why you assume I MUST have done something wrong. Do you really think it's impossible that this was a weakness on their end?
If 110 million credit cards can be stolen from Target, maybe it's possible API keys can be stolen from CoinBase?