zeppelinnn

@General is right. Here's a great link about what this process generally involves and why you would do it: http://www.pokerology.com/lessons/calculating-expected-value...

Your statement is true about the "feel" players, but even those players will perform EV analysis away from the table because by estimating percentages of certain tendencies you can figure out what the right play is in tricky situations, and over the long run that ends up saving more money than anything else

True, the way cards come out is chance in a single instance of a hand, but in the long run, over thousands, maybe millions of hands, the cards that you expect to come out will do so more often, and the skillful players will win more often (as opposed to the occasional bad beat). If you are talking about professional basketball then of course there is luck.. at such a high level a few points, basically a basket, can make the difference between a championship and a lost series, but again, we see the best teams (for the most part) every year in the playoffs repeatedly. The same can be said for rec basketball - the closer the skill levels are of the players to each other, the more luck may play a factor.

This is awesome. Reminds me of all the data viz they are doing on rapgenius. You forgot Atmosphere though (Slug)

TOS in general are vague but encompassing. I guess that's the point though

I'm really glad someone took the time to do this, and came with quite a wholesome set of resources in the end. For someone who has moderate web dev experience such as myself, I think it's also definitely useful for review as well as the aspects of web dev you may be less/not at all familiar with.

looks like a great guide.. i was working through the original "how to learn angularJS" tutorial, but it got dry through some parts because it was too much material at once without too much of the application behind it in the big picture. I think this tutorial will definitely help with that, good looks!

I think this is correct for personal projects, but when working with teams it's better to create dev branches especially for major feature/functionality additions. I personally try to stick with separate branches and then merge just to uphold that practice, as well as being able to revert/find your mess-ups quicker.

I personally like apple's recent approach to the scrollbar. Hiding it when not in use minimizes distraction. It's very easy to tell how long a single content page article is without needing the scrollbar to persist on the window.

looks like a pretty awesome tool, making web dev possible for anyone. excited to see where this goes!

This looks pretty awesome. Definitely going to give it a try.