1. Blatherskite River – “Blathering Blatherskite” – Fenton Crackshell
2. Former Site for Adult Services on Craigslist Island
3. Kayne’s Isle of Sadness
4. Hashtag Games Whose Popularity Confuses and Depresses You
If you are looking for Webinometry on this map, it was sunk somewhere just south of Miscellaneous Blogs on a fateful journey from the Sea of Zero (0) Comments to the eastern coast of Tech Blogs. You see, I was shipping my blog content to a competition with an arch nemesis regarding who has the most mathematical references per post. To throw him off, I shipped it under the disguise of an ice cream freighter. I was informed by my trusty accountant Whimperman that it was sunk by a sea monster. Reaction below:
Last week, I’ve started to learn Python through a peer-to-peer learning session set up through nextNY. The material that we’ve gone through has made learning programming very easy to wrap our heads around, and the environment of cooperative learning has been awesome. I’m looking forward to being a Python ninja* pretty soon.
With four and half chapters of Python at my disposal, I wanted to put my skills to the test. Since I’m a huge baseball fan, I thought I’d try my hand in simulating who would lose the World Series this year, a pillow-fight match-up between the New York Yankees and the Philadelphia Phillies.
The first thing to do was to crunch the numbers. Crunching the numbers means exactly that, figuring out the probabilities of events occurring over a seven game series. I incorporated things like Ryan Howard’s immense strike-out rate, Derek Jeter’s incredible lack of range at shortstop, and Brad Lidge’s ninth inning ERA. I also made sure to incorporate correlations, or how related each variable is to each other. Funny enough, the highest correlation I found was between having a runner on first base with less that two outs in the seventh inning onwards and Arod weakly grounding into a double-play. Numbers never lie.
Now this got me a pretty good picture of who would lose the World Series, but I hadn’t taken into consideration the qualitative variables, the intangibles, the “Cole Hamels’ is a play-off pitcher” and the “Mariano is unhittable in the World Series” bullshit bullshit. These are usually the ‘statistics’ that overzealous fans throw out (with no meaningful data except their distorted memories) as their defense to a player’s immortality.
The classic intangible lies on the shoulders’ of the Yankee captain, Derek Jeter, a ball player that seems to find himself at the right place at the right time in the postseason. Yankee fans have constantly spouted his ‘greatness’, and refuse to admit that he was horribly out of position on the Jeremy Giambi play at the plate, and doesn’t even register as having the highest batting average in a World Series (that designation goes to Billy Hatcher who hit a sickening .750 for the Reds in 1990 in 12 ABs). Heck, Jeter doesn’t even deserve the nickname “Mr. November” for his play in the 2001 World Series. He had 1 HR, 1 RBI, and 2 runs scored in November, numbers that were almost matched by a pitcher for the Arizona Diamondbacks (1 RBI and 2 runs scored). Oh, and that pitcher also won two potentially series ending games in two days that November with a 2.22 ERA, .96 WHIP, 8Ks in 8.1 innings. Derek Jeter, I’d like you to meet the real “Mr. November,” Randy Johnson.
Okay, so I wrote my little Python program to capture all of this. The stats, the pseudo-stats, the Phillie Phanatic’s rants, and the countless times we’ll hear “26 World Series rings.” With so many probabilities and interactions, this program chugged along for two days, and finally, yesterday before the first pitch, I got the result: Value Error: Let’s Go Mets.
*Looking forward to the day when ninja is not used in start-up world employment searches and reverts back to its original awesomeness of stealthy nighttime assassin.
This past weekend was one of the most outrageously fun times I’ve ever had, and it showed how really unbelievable it is to have great friends. I think everyone there was looking forward to this wedding for months and it 100%, without a doubt, did not disappoint.
Here’s the video montage of the wedding festivities. With the massive cooperation of everyone at the wedding, Mohs and Laura had no idea that this was going on (you’ll see them at the end, Mohs in his sweat drenched shirt and orange tie, and the lovely lady in red Laura dancing up a storm). What started off as a cutesy gag gift for the bride and groom eventually turned into a “what could we possibly get away with without them knowing” full on puppet wedding production, all entirely made up on the fly.
Even the near fatal miscue moments turned into some fantastic shots, like the entire family picture, the wine glass clinking kiss with Amy (sitting right next to Laura), and my personal favorites, the party barn shots with Mohs at the bar and Laura on the dance floor (brilliant work by Gabs on those two). No risk, no reward.
The couple’s first look at this video had them, as Mohs put it, simultaneously laughing and crying. I glad to see the art of puppetry hasn’t lost its magical touch on our souls. And if this whole web application thing doesn’t work out, maybe my next career path can be puppet wedding videos. I’d love to hear company names and tag-lines for that.
UPDATE: My friend Justin just informed me that the actual formula in here is .002 + e ^ (i * pi) + Sum (1/(2^n)) from n = 1 to infinity. This reduces to .002 -1 +1, which is much more interesting than .002 + (some random number) + 1. This is a brilliant response to George Vaccaro’s unbelievable encounter with Verizon’s billing department.