NCAA Saturday Picks

There was 1 game that could sum up the overall picks for Tim and I yesterday. I had San Diego St to cover the 6 point spread, and Tim had under 125.5 total points. At the end of the first overtime, the score was 61-61 (122 total points). So, if either team had won the game during regulation or during the first overtime (even with a last second three-pointer), I would have lost and Tim would have won. As it turned out, the second overtime saw San Diego St score 10 points to Temple's 3 points. The final was 71-64, which meant that I won my bet and Tim lost his bet.

That's very similar to the 2003 Arizona/Gonzaga game in the round of 32. I was in Vegas and had a bet on the under for that game and they finally went over in the second overtime. Although I'm wondering now if my memory is failing me with that game. I just looked it up and the game was tied at 78 at the end of regulation and tied at 89 at the end of the first overtime. That would mean that Vegas had the total at somewhere over 178, which seems very hard to believe - totals just don't get that high.

Overall, I was 6-2 Saturday and Tim was 2-6. Favorites were 7-1. There were 5 games over, 2 under, and 1 push. (Again, just like Friday, there was one game were the total moved enough by tip-off - I had Kentucky/West Virginia over 132, but the top-off total was 134 and Kentucky won 71-63).

Comments

Post a Comment

Popular posts from this blog

Tasker: Get Voice Command

The way I decided to set up Tasker is to use some reusable tasks that can be called from other places. The first one I'll talk about is the Get Voice Command. This task listens for some stock commands like "yes", "no", "cancel", or "repeat". It is a quicker listener than the "Get Voice Input" command which I'll talk about in another post. This is meant some some quick one or two word commands. It uses regular expressions to match commands (meaning, you can say "yep" or "yeah" or "yes sir" and it will return "yes"). Being generic like this means that I don't have to duplicate all these regular expressions everywhere. I can just call this task and if it returns "yes", then I know the user (me) said something like "yes" or "yeah" or whatever. There's an input parameter to the task of the message to speak before listening for the answer. The task will re...
Read more

Finally Have Access Again

At some point last year, my work computer decided that all "blogger.com" web addresses were bad and must be blocked. So I was unable to update this blog from my work computer. I finally got a new personal computer so I'm able to update this site again.  Most of my updates are on March Madness trips. In 2024, I did not go anywhere for March Madness. On Thursday I went out to a local bar and on Friday I stayed at home and hosted some of my friends on my 4 TV setup in the basement.
Read more

How to play a 16 against a 10

This month's Casino Player magazine has lots of good information, and I'll be posting some of it over the upcoming days. In blackjack, here are the rules for playing a 16 against a dealer's 10 up card. If you have a 10 and 6 or a 9 and 7, surrender if you can. If you can't surrender (not allowed), then hit. If you have a pair of 8's, then split them. If you happen to draw another 8 on the split (so you again have 16) and you can't resplit (not allowed), then stand. If you get a 16 after three or more cards (e.g. you start out with a 4-8 and then hit and get a 4), then stand. If you have a soft 16 (e.g. Ace-5 or 3-Ace-2) then hit. I always had a "gut feeling" about that third one - the "card" (see wizardofodds.com for an example) says to hit a hard 16 against a 10, but the card also doesn't differentiate between a two-card 16 and a three-card 16. I didn't know if it made a difference or not, but most of the time I would stand on a thr...
Read more