zsch

This was my weekend project, which doubled as an introduction to the world of Facebook bots and node.js. I open sourced it: https://github.com/zchr/taketen. I'd love any feedback!

That's how it initially was. But I have now made it so that, as you say, it first checks to see if it's a multiple of 7. If it's a multiple of both 7 and 3 (regardless of whether or not you have played it before), then you will no longer be penalized.

I agree. Just updated.

That makes complete sense. I originally considered making a small noise when the sum was added to the score, though I'm leaning more towards flashing the updated score with a different color. Thank you for the feedback.

That's a great idea! The trick will be finding a place to display it. Maybe I'll add a button next to the score, and clicking it will reveal an overlay with played numbers.

Thank you for pointing that out. No it should be on a game by game basis. It should be fixed now.

Thank you for the article. Believe me, I am very much aware that this is elementary. I hoped to – but apologize that I didn't – make it clear that making predictions requires incorporating many many factors. It was a fun script for me to code, and I was excited to see it work the night I wrote it. But I also understand that this will need more testing and to be based off of far more information to be anywhere close to accurate.

I'm sorry it came off that way. I am very aware that the script in its current form does not come remotely close to doing justice given all of the data thats out there and necessary to incorporate. I meant to make it clear in the article that this script is completely elementary – it was a fun thing to code, but nothing remotely resemblant of what it takes to predict sports with accuracy.

The 2012 data I used as the basis of my program actually had the same thing you describe – the longest streak was an 8 game losing streak despite having more wins than losses overall.

And I understand exactly where you're coming from. This is very preliminary, and if anything it was good coding practice for me. Though I very much intend to incorporate more significant factors like the lineup, the opposing team, and their history.

Excellent idea. And it will provide a much faster way to gauge its accuracy as I adjust the script to accomodate more areas of information.

I actually just started that book and so far so excellent.

yeah for now... They're most definitely a thing, though I have a documents worth of baseball elements I hope to incorporate

I understand where you're coming from. My friend's statistics teacher said that if a flipped coin results in 5 heads, it doesn't owe you a tails – this seems to support the gambler's fallacy. Though looking at something like running: say I run the first mile in a race in 7 minutes. Odds are the next mile will be a bit slower given I'm bad at pacing myself and I'm now tired. This is an extreme example, but I've been trying to look at baseball with this approach, that prior games influence the outcome of the next game. And I know that I am simplifying my prediction by just accounting for streaks. I would love to lengthen the script to look at factors like how much the team has won/lost by, who's on the lineup, where the game is (home versus away), etc.

But at its least this was good coding practice.

Their data is excellent – thanks for sharing. Interesting when they take into account so much more than streaks. I would love to dive into the relation of more of that data in the future.

Thank you. Yeah like I said it is by no means a solution to the security problem in the current authentication system. Though it is great that people are thinking of alternatives.

Thank you! I love looking at this kind of real-world data, and the project doubled as a great way to practice Python.