3 ms·
Hey! They didn't even mention Long Bets! That's the site that registered the bet and is holding the money. http://longbets.org/ http://longbets.org/ Which I a
by wpietri 14y ago
Hey! They didn't even mention Long Bets! That's the site that registered the bet and is holding the money.
http://longbets.org/ http://longbets.org/
Which I am going to pimp shamelessly here, as I wrote the code for it a decade ago. We have bets that go out many years. There's one that won't be decided until 2150. There's even one about how the universe will end.
If you would like to make a similar long-term bet, either use the site or let me know; I'm glad to facilitate. As long as the bet is more than 2 years out and the stakes are more than $200 each, you're golden.
We'd love to see the site used more to call out people making bold/crazy predictions. E.g., is somebody saying that NoSQL databases will rule the earth in 10 years? Do you think they're wrong? Tell them to put up or shut up! We'll put you both on record.
- impendia 14y agoMy favorite: "Large Hadron Collider will destroy Earth."
- arbuge 14y agoI'd be willing to bet everything I have it won't. In fact I'd offer the same for any "XXX will destroy Earth" bet. Let me know if you're interested :-)
- RyanMcGreal 14y agoSo did Stigler win this one? http://longbets.org/291/ http://longbets.org/291/
- wpietri 14y agoThanks for the prod. They are now adjudicating all the outstanding best. Stigler did indeed win that one!
- gwern 14y agoOne problem you guys have is that you aren't updating anything. I've been copying over predictions to predictionbook.com for the last 2 or 3 years now, and a number of predictions have expired - with no official judgment or anything.
- wpietri 14y agoThanks for the feedback! The predictions intentionally haven't been updated. With bets the adversarial bet definition process produced clear, ajudicatable criteria. Predictions, though, were intended to be looser. We just wanted to record them, and didn't want to be in charge of deciding them. If I had it to do over again, I'd be tempted to solve the problem in a crowdsourced way, where people get to opine on the outcome of the prediction endlessly. I'll check out PredictionBook; it looks interesting. And if you want to discuss this stuff with me or the Long Now staff, feel free to get in touch.
- jaggederest 14y agoHow's the code maintenance on that? Just imagining what 'long now' code looks like!
- wpietri 14y agoGreat question! It's something I thought a lot about. When we originally did the project, I engineered for long-term sustainability. I picked Java because even then it was obvious that Java was the new COBOL. Which had its drawbacks, but that meant high stability and longevity. I avoided complex dependencies; it ran by keeping all data in a single process and writing everything out to a set of XML docs on a filesystem. There the bet was that Moore's Law would progress faster than the data set size or the usage volume; that turned out to be true. The only real dependencies were on the core Java and Java Servlet stuff, plus an XML library. That simple architecture made it relatively sysadmin-friendly. Data was backed up by a simple script that just checked everything into CVS every 15 minutes. When they needed to move it to a new machine there was just setting up a standard Tomcat container, dumping in the WAR, and pointing it at the data. So there was never any significant downtime. I also wrote a bunch of unit tests, so that in theory it would be easy for another developer to pick up. Only a couple of other devs worked on it, though, so it's hard to say how much that helped. But I was really happy to have the tests a few years later when we reved it. Eventually it got rewritten in whatever their in-house dev was using so it could be more integrated with the existing accounts. The original code base lasted a decade or so, though, so I'm satisfied with how most of the initial choices worked out.