Monday, February 06, 2017

The Patriots Are the Pick

I’m no fan of the New England Patriots. Now that I think about it, I have probably rooted against them in every Super Bowl they’ve ever played.

I suppose I was neutral on them up until 2004 when the Pats defeated my Carolina Panthers in that wild Super Bowl 38. Carolina lost 32-29 after a crazy fourth quarter that saw the Panthers score three touchdowns, New England two, and the Pats hit a game-winning FG at the end.

That was New England’s second title in three years, so it was easy to root against them thereafter as they dominated season after season. It has never come close to rising to Duke-level dislike (deep and unchangeable in this Tar Heel), but it’s been a pretty consistent feeling of antagonism toward the team for me nonetheless.

That said, I have one rule in Pigskin Pick’em I’ve (almost) unerringly followed for years. I always pick New England. No matter what.

Last night Vera and I attended a fun Super Bowl viewing party, and just about everyone there was on the Atlanta Falcons side, too. Here in North Carolina most were either Washington Redskins fans or Atlanta fans growing up, as they were the teams always featured on regional coverage here up until the Panthers franchise debuted in 1995. Not too hard, then, for many around these parts to be leaning Atlanta’s way last night.

It was pretty festive up through the middle of the third quarter as Atlanta surprisingly built that 28-3 lead. The largest comeback ever in 50 previous Super Bowl had been just 10 points, so a 25-point lead seemed more than insurmountable.

Actually the party remained fun during the Patriots comeback. Everyone wanted Atlanta to win, but it wasn’t like we were Falcons diehards. The fact that the game got closer as the night wore on ensured the game remained the focus of everyone’s attention the entire way.

If you watched, you saw how it all went wrong for Atlanta. You may not understand it, but you saw it.

Bill Barnwell breaks it down step-by-step this morning in an article titled “Anatomy of a Miracle” over on ESPN. It was way more nutty than that Panthers-Pats finish 13 years ago. It was also much more improbable than the New York Giants’ unlikely win over New England in SB 42, or the Seattle Seahawks’ surprise gift to the Pats two years ago at the end of SB 49.

It was a bit like watching a player with a 10-to-1 chip lead heads-up lose flip after flip to let victory slip away. There were several bad-luck plays for Atlanta, the incredible catch (and release and catch) an inch above the turf by the Patriots’ Julian Edelman on that tipped ball during the game-tying drive late in the fourth quarter the most memorable example. There were so many if-they-just-get-this-one-it’s-over plays in there, it was kind of like watching queen-six beating ace-ten over and over.

But you’d have to mix in some self-inflicted wounds from Atlanta, too -- a costly turnover, very bad clock management (multiple fourth-quarter snaps with 15-20 seconds on the play clock), and blowing through what turned out to be needed timeouts spring to mind.

Some questionable play calls in key spots do as well, most glaringly when up 28-20 with just under four minutes left and looking at a second-and-11 on the Pat’s 23-yard line. Atlanta went high-risk with a pass play, got sacked, then after another pass play ended with a holding penalty they were out of FG range, having to punt to New England (who still had their two timeouts) with three-and-a-half minutes to go.

There’s no denying New England couldn’t have climbed back out of such a historically deep hole without some help from Atlanta. Nor could they do it without the “cards” falling their way, too. Before overtime began, someone at the party correctly predicted New England would win the coin toss and march down the field for a winning TD, and indeed, things bounced the Pats way again and he was proven correct.

That said, the Pats were relentless from the midpoint of the third quarter onward -- like an almost flawless, “optimal” poker player who never seems to choose incorrectly. And when he does perhaps do something uncharacteristically risky (e.g., the pass into double coverage resulting in Edelman’s spectacular grab), it still works out for him.

Am seeing this morning a best-to-worst ranking of the 51 Super Bowls already putting last night’s at the top of the list. I’d charge recency bias, but sheesh... a 25-point comeback? A team down 19 to start the fourth somehow pulling it out? That stands out.

I’m still no fan of the Patriots. And I’ll still root against them. But I’m not picking against them any time soon.

Labels: , , , , , ,

Friday, January 20, 2017

Finishing First

Everyone was ganging up on 2016 as the year concluded, what with all of the bad news punctuating seemingly every week of the calendar year.

For your humble scribbler, the year seemed to involve an inordinate number of second-place finishes. My Carolina Panthers came up short in the Super Bowl in February, then my UNC Tar Heels also took runner-up in the NCAA finals in April. Then in May I finished second in a poker tournament in Monte Carlo, and came here to whimper a little at having come so close to winning only to have it snatched away.

The presidential election in November was hardly considered a victory here on the farm either, I’ll confess. It was right after that I remember messaging a friend and after listing all of the second-place finishes making a stubborn proclamation: “I am winning the gotdamn Pigskin Pick’em and that’s all there is to it.”

I was referring to the Pauly’s Pub football pool, of course, which I wrote about a bit during the course of the NFL season here although not as much as I have in past years. This was the eighth year running I’ve participated. I won it once before (in 2011), and this year managed to get off to a fast start to tie for the lead in Week 2, then take the lead all by myself in Week 3. By November I had built up a long streak as the frontrunner, and would remain in the top spot into the final weeks.

My largest lead over the chase pack was five games -- six, in fact, for a brief period halfway through one Sunday’s games -- but it had been reduced to just one game heading into Week 16. I was a bit of a basket case, I’ll admit, worrying that I was sadly, slowly careening toward yet another second-place showing.

Week 16 saw games happening all over the place as the NFL scheduled things around (and on) Christmas (which was a Sunday). I believe games took place on four different days that week. I enjoyed some great fortune in three games that mattered a lot, as in each I’d gone one way and my trailing opponent(s) went the other.

The first was the Atlanta-Carolina game where I took the Falcons, others took the Panthers, and Atlanta won easily. Then came the Cincinnati-Houston game the night of Christmas Eve. I had the Texans, my nearest foe had the Bengals, and while Houston led 12-10 in the final minute Cincy was driving for what seemed a certain winning field goal. With seconds left, Bengals kicker Randy Bullock tried a 43-yard field goal that somehow went wide right, and Houston won.

Then on Christmas Day I’d taken Pittsburgh over Baltimore (whom my closest challenger took), and after a crazy back-and-forth game the Steelers got a go-ahead TD with just over a minute left to win 31-27. I was up four games heading into the final week, a relatively comfortable place to be.

For Week 17 all 16 games were played on Sunday, and after making my picks I realized I could very well have it all locked up by mid-afternoon. But it didn’t go so easily.

Up four versus three opponents tied for second, two of them gained two games on me in the early afternoon games, cutting my lead to two. In the late afternoon games one of those two and I made identical picks for all six of them, which meant I’d automatically clinched beating that player as there was only the single night game left.

With the other opponent we’d picked five games the same, only differing in one -- the New York Giants (whom he picked) at Washington (whom I’d picked). The Redskins were playing to earn a playoff spot while the Giants had nothing to play for at all, having already clinched a seed that wouldn’t change with a win. But NY played their starters throughout, Washington struggled mightily, and the Giants won the game.

Now with only the Green Bay at Detroit night game left to go -- the 256th of 256 regular season games -- I had a one-game lead. And I had a strong suspicion my opponent was going to go with the underdog Lions in an effort to close the gap.

I was facing an interesting “game theory”-type situation, I realized. And I had about an hour before the kickoff to ponder it.

I had already chosen Green Bay, but could change my pick if I wished. That said, I had imposed on myself a strict “no-change” policy according to which I never changed a pick once I had entered it. I estimated the likelihood my opponent was taking the Lions to be at least 75%, perhaps even higher. If he did and I switched to Detroit, I’d clinch the title as soon as the game kicked off. But if I stuck with Green Bay and he took Detroit, I’d have to sweat one last game.

I decided not to change my pick, and when the game began I saw indeed he’d taken Detroit. Then the Lions led for the first half, and I was filled with misgivings for having let a superstition of sorts overrule my rational analysis of the situation. Green Bay stormed back in the second half, though, with Aaron Rodgers leading the Packers to three TDs in four drives to build a two-touchdown lead. I don’t think I finally exhaled, though, until after Green Bay covered up the onside kick at the very end after Detroit had made it 31-24.

I couldn’t help but laugh, thinking how I’d spent 10-plus hours during the first day of 2017 fretting about the pool, thinking all along how if things had gone just slightly differently I might’ve clinched things during the early afternoon and avoided all the stress.

Today the trophy arrived, which turned out to be a shiny bit of fun amid a dreary day in which a newly-inaugurated president is going on about “America First,” seemingly unable to understand the difference between national pride and jingoism. (Not to mention unaware -- or perhaps not -- of the term’s history and less than appealing connotations.)

In any case, I’ll say it was fun to be first nearly all year, and even more so to end up on top -- a nice finish to start a new year.

Labels: , , , , ,

Tuesday, December 06, 2016

Big Numbers at the Bellagio

The World Poker Tour has returned to the Bellagio this week for the WPT Five Diamond World Poker Classic, a $10K buy-in event that has become a huge punctuation mark of sorts to the poker calendar each year.

I had the chance to help cover this one three years ago, the last time (I believe) it still had Doyle Brunson’s name attached to it. Dan Smith won the event that year, topping a 449-entry field to win about $1.16 million.

In 2014 they drew 586 entries, and Mohsin Charania won it, earning $1.18 milly. Then last year there were 639 entries, with Kevin Eyster taking the title and a big $1.59 million first prize.

This year the Five Diamond is even bigger with a whopping 791 entries, which means the first prize is way up to $1.938,118 and even the runner-up will win seven figures. It’s a re-entry tournament, which helped boost the overall total. Still, that’s a huge turnout, suggesting the Five Diamond has become kind of a must-play for many top pros as they plan out the close of their tournament year.

Am seeing Jennifer Tilly is second in chips out of about 270 players heading into tomorrow’s Day 3. Tilly sent a funny (and insightful) tweet late in the day alluding to her status near the top of the leaderboard.

“Trying to hold on to my big stack is exhausting!” she wrote. “It’s like trying to keep a giant rock from rolling down the hill.”

I know some players thrive when they have a big stack, and in fact some aren’t comfortable otherwise. But many (most of us?) are more used to being in the middle somewhere or on the short side, which can sometimes make the new challenges presented by having a lot of chips especially taxing or even anxiety-producing.

I guess the Five Diamond (and WPT) is itself kind of experiencing having built up a “big stack” (in a way), with such a big field having turned out. As always happens with tours and particular events, drawing huge numbers presents a new challenge for organizers, sometimes causing problems as they discover various reasons why it isn’t so easy to accommodate so many. Thus will certain events peak in terms of turnouts, then fall back to something more sustainable thereafter.

I haven’t followed things that closely, so don’t know how well the Bellagio -- which doesn’t have the biggest room -- managed things these last couple of days. Hope all has gone well, though, and that sucker can continue to grow going forward.

Have to admit Tilly’s giant rock metaphor made me think as well about my status in my Pigskin Pick’em pool, where I continue to maintain a lead (and have for most of of the season). It is exhausting -- that is, the amount of mental energy I’ve found myself putting into this sucker when both picking games and sweating them every Thursday, Sunday, and Monday.

Am hoping Tilly can keep that big rock of chips right where it is as the tournament continues. Meanwhile I’ll be jetting in the other direction tomorrow, heading over to Prague for the European Poker Tour’s last festival, where I imagine some of those playing in Las Vegas this week will be heading once they are done.

Will have to see how well EPT Prague does to close out both 2016 and the EPT (nominally, anyway, as the rebranding begins in January).

Image: “2008-03-26_IMG_0519_Las Vegas - Fountains at the Bellagio” (adapted), Dieter Weinelt. CC BY-ND 2.0.

Labels: , , , , , , , ,

Monday, November 21, 2016

Risk Versus Reward

I continue to lead in my Pigskin Pick’em pool, which means I’m necessarily locked in and following closely just about every NFL game each week. I’d be watching and checking scores anyway, but my motive for doing so has increased considerably thanks to the pool standings.

Amid all those missed extra points yesterday (which created a few interesting spots, strategy-wise), there were a few instances of coaches faced with key fourth-down decisions late in games. A couple stood out, both involving teams that were ahead and looking at a fourth-and-short with just a few minutes left.

One came late afternoon when the Los Angeles Rams were up 10-0 against the Miami Dolphins with six minutes and 45 seconds remaining. The Rams had a fourth-and-1 at the Miami 30-yard-line, and rather than go for it decided to try a 48-yard field goal that like those PATs ended up a miss (hitting the left upright).

Miami subsequently marched down the field to score a touchdown in less than three minutes, held the Rams to a three-and-out and got the ball back, then took just a minute-and-a-half to mount another TD drive to win 14-10. Rams coach Jeff Fisher was maligned somewhat afterwards for not going for the first down rather than try to stretch the lead from 10 to 13 -- certainly more so than would have been the case if L.A. had managed to hang on to win.

Another instance came in the night game between Washington and Green Bay. In that one the Redskins were up 29-24 and in fact there was exactly the same amount of time left -- six minutes and 45 seconds. In Washington’s case, they were on their own 41-yard line and facing a fourth-and-1. They decided to go for it, got a couple of yards and the first down via a quarterback sneak, then went on to score a TD themselves and more or less seal the game.

Of course, in the latter situation Green Bay’s offense was proving hard to stop for Washington (they’d scored TDs their last two possessions), so the desire to retain possession was higher there than was the case in the Rams-Dolphins game where Miami hadn’t scored a point in any of their 11 possessions. In any case, Washington coach Jay Gruden earned accolades for what was deemed a gutsy decision to go for it on fourth in that spot, although again it’s easy to imagine the decision being judged differently had it not worked out the way it did.

“Gruden was feeling risky all night,” writes ESPN, alluding both to the fourth-down try and Washington having gone for two-point conversions twice earlier (failing both times).

Meanwhile many noted the very conservative game plan followed by the Rams who had rookie QB Jared Goff making his NFL debut, with Fisher’s decision to try that field goal earning some censure for being too risk-averse. “Los Angeles could have won that game if Jeff Fisher was less conservative on fourth down late in the game,” concludes RamsWire, articulating a thought shared by many.

Neither of these fourth-and-1 decisions were unambiguous in terms of their reward. That is to say, making the first down didn’t guarantee victories, although certainly would meaningfully improve the team’s chance of winning the game. The risk each presented wasn’t cut-and-dry, either, although it appeared Washington faced a greater one with a smaller lead and worse field position.

I saw a stat not long ago stating that over the last 20 years nearly half of all NFL games ended up being “one score” games decided by seven points or less. Games finishing with margins of eight points up to 16 are also often still in doubt by the middle of the fourth quarter, which means the majority of NFL games present situations in which teams that are ahead face similar challenges to weigh risk versus reward when it comes to clock management and possession.

Like a player with a final table chip lead, such teams and coaches still often have to continue to take risks in order to increase their chances of winning. In other words, they usually can’t just “fold” their way to the win.

My frontrunner status in the pool is causing me to identify somewhat with this position. And the example presented by these coaches and their disparate ways of handling the endgame is making me recognize I shouldn’t become too conservative with picks going forward, since being overly risk-averse may lessen my chance at the reward of winning the sucker.

Photo: Advanced Football Analytics.

Labels: , , , , ,

Wednesday, November 09, 2016

Upside Down, Unexpectedly

Poker steels a person to handle the unexpected.

Those who’ve played the game even for a short while -- and who’ve paid attention enough to absorb some of the odds and probabilities and learn what is likely and what is not -- become accustomed to surprises. You know, kings cracking aces, the occasional one- or two-outer showing up on the river, or various runner-runner revelations that can make improbable winners of all-but-certain losers.

Of course, even when in possession of this knowledge, we still experience a certain level of surprise when such things happen. If we’re human, that is. Experiencing such emotion is part of what helps keep the game interesting to a lot of us. After all, in our “normal,” day-to-day lives, we rarely experience surprises, and indeed often try to map out our activities so as to avoid them.

Regardless of who you supported, the result of last night’s presidential election was more than likely not what you expected to happen.

Watching the coverage play out starting during the early evening when the first polls closed on the east coast, all the reporting emphasized the high likelihood of Hillary Clinton winning. In fact more than one outlet used a poker metaphor to describe Donald Trump’s needing to win several states in which Clinton was favored, saying his position was like “drawing to an inside straight.”

A couple of hours in, though, just after nine o’clock ET when another round of states’ polls closed and more projections and calls were delivered, the situation suddenly swung the other way. For Trump supporters, it was a delirously exciting 20-25 minutes or so; for those backing Clinton, it was a nightmarish sequence, occurring rapidly enough to make it hard to grasp fully the implications of what was happening.

The betting markets were slightly ahead of the game with their numbers last night. My friend Rich Ryan was tweeting out Pinnacle’s lines on a regular basis all night. Actually he’d been doing it for a week, with “HRC” the big favorite, climbing as high as -780 as things got going last night. In the space of an hour that figure dropped to -124, then after lingering there a while the sucker flipped to show “Trump/Other” at -122. An hour later Trump was up as high as Clinton had been, and by shortly after 11 p.m. here it already seemed all but certain there was no way Trump would lose.

I had CNN on, and sure enough Jake Tapper was revisiting that poker analogy not long after the flip had occurred. Recalling the earlier reference to Trump’s seemingly slim chances, he noted how the situation had been changed to Clinton being the one drawing not just to an inside straight, but to an inside straight flush, suggesting the need for a one-outer rather than a four-outer. (Am still hunting down the exact quote -- when I find it I’ll include it here.)

I was mentioning yesterday Nate Silver’s much-cited election forecast. He’d famously predicted 49 of 50 states plus D.C. correctly eight years ago, then got all 50 of them right along with D.C. in 2012. This time he (or his models) whiffed on five key states -- Florida, North Carolina, Pennsylvania, Wisconsin, and Michigan -- all of which he had going Clinton’s way, and all of which Trump won.

Signing off from the coverage over on FiveThirtyEight last night, Silver actually wrote he wasn’t surprised by the outcome given that the polling had indicating the possibility of a competitive race. But he also admitted that “in a broader sense... it’s the most shocking political development of my lifetime.”

Yesterday I also brought up the analogy of picking NFL games, bringing up again that Pigskin Pick’em contest I’ve enjoyed over the last several years. Sometimes when writing about the contest I’ve alluded to those “Win Probability” graphs and how wild they sometimes appear in games that end with unlikely finishes where one team snatches victory away from the other following a final, surprising twist (or two or three).

The graph tracking last night’s developments was similarly dizzying. Just below is the one from The New York Times, which is pretty much identical to the ones created by other outlets overnight:

The reasons both for Trump’s win and for the failure of so many to see it coming are going to be discussed for some time. I have my own ideas, though don’t necessarily want to try to sort them out here just yet.

When a poker hand or football game gets all twisted around at the end, it’s usually easy enough to isolate the card(s) or play(s) that caused the outcome. This one is a lot more complicated, though still can be explained.

All of that effort will have the effect of lessening the shock of experiencing that head-spinning half-hour last night. When the blue and red graph lines unexpectedly dived upon one another, crossing paths in a sudden rush that literally turned the story they were telling upside down.

I mean, really... whatta river.

Image: “Election 2016” (adapted), DonkeyHotey. CC BY 2.0.

Labels: , , , , , , ,

Tuesday, November 08, 2016

On Being “In Play”

Happy Election Day, all.

I voted this morning. I would have tried voting early, but I was on the road -- to Malta, then to New Jersey -- for pretty much the entire time early voting was available for me.

I arrived at the nearby church that functions as my polling station right at 6:30 a.m. so as to avoid any long lines later today. The place was already packed, and in fact it was hard finding a place to park. But the whole process only took about a half-hour to get through, and now I’m back on the farm where I’ll be tuning in tonight with everyone else to see how it all goes.

North Carolina is a “battleground state” this year, with enough electoral votes to matter and genuine uncertainty over whether it’ll be tipping toward Hillary Clinton or Donald Trump. I noticed yesterday Nate Silver had placed NC on a “Tier 1” line with Florida as a key indicator of how things are ultimately going to go.

Eight years ago the state barely chose Obama, while Romney won by a wider margin in the last election. The polls having been suggesting Hillary wins NC by a smidgen this time, but it’s truly up in the air at the moment. (Bill Clinton lost NC by small margins in both ’92 and ’96.)

It’s curious to be voting in a state that is “in play” like this, given how most elections that hasn’t really been the case. It reminds me a little of the Pigskin Pick’em game that has been increasingly distracting me every week since I’ve been out front in the sucker since Week 2.

Every week’s slate of NFL games contains many games that essentially aren’t significant since practically the entire pool picks the same way. Such was true, for instance, with last night’s Buffalo-Seattle game in which almost everyone took the Seahawks (and won, although it was a close one).

Meanwhile other games last weekend were most definitely “in play” -- e.g., Philadelphia-NY Giants, Carolina-Los Angeles, and Denver-Oakland, which in each case saw about half the pool go one way and half the other. Those outcomes therefore meant something, affecting the pool standings, while the unanimous (or near-unanimous) games did not.

Of course, what I’m describing is all a matter of perception. It’s like when we talk about a poker hand and after fourth street brings an apparent “blank” we cheerfully say “the turn changed nothing.”

But almost always the turn is not wholly insignificant (except in those relatively rare instances when a player is already drawing dead after the flop). It moves the game forward another betting round, having meaning even if it doesn’t change who is ahead in the hand.

So, too, do these games (or states) that aren’t “in play” still significant to the overall contest. (In fact, who’s to say, really, which states are and are not, until later tonight?)

In any event, regardless how the election turns out, things have certainly changed here in the U.S. and will continue to do so going forward. After the last year-and-a-half, it feels like practically everything is “in play” now.

Labels: , , , , , , ,

Monday, October 03, 2016

Fumbles That Hit You Right in the Feelings

Football season is in high gear, even if my Carolina Panthers are off to a woeful start.

Yesterday’s game versus the Atlanta Falcons was especially distressing, given how evident it was from the very beginning the defense wasn’t going to be able to stop Atlanta’s passing game. Reigning MVP Cam Newton going out in the second half after suffering a concussion just made things less pleasant.

The Panthers losing presents a specific problem for me in my Pigskin Pick’em pool (where we pick games straight up, not versus the spread), as I dislike picking against them. That bias wasn’t so much of an issue last year when they went 15-1, but it’s already earned me three “X” marks this year.

Otherwise I’ve done well so far with my picks, although yesterday got me thinking once more about the relative pain and pleasure that comes from various outcomes.

My buddy Robert Woolley, a.k.a. the “Poker Grump,” wrote a nice article for PokerNews recently titled “Mountains, Swinging, and the Fear of Loss in Poker” in which he shares some research regarding the way losing can hurt more than winning can feel good.

According to findings of the economist Robert cites in the article, the “loss aversion” ratio for most people is “in the range of 1.5 to 2.5.” In other words, for many it is somewhere either above or below being twice as painful to lose than it is pleasurable to win.

It was early in the NFL season last year I shared a hastily-created “pleasure-pain index” for Pigskin Pick’em, something I was reminded of by Robert’s article as well as by some of the results from yesterday. The index goes as follows:

  • most pain: making non-consensus choice (usually an underdog), being wrong
  • least pain: making consensus choice (usually a favorite), being wrong
  • least pleasure: making consensus choice (usually a favorite), being right
  • most pleasure: making non-consensus choice (usually an underdog), being right
  • After three weeks of following a relatively conservative path with my picks, I broke out of that yesterday somewhat by choosing a few unpopular dogs such as Jacksonville (who won) and the LOLJets (who lost). Those picks ended up evening out for the most part, although one game in particular -- San Diego’s miserable give-away of its game versus New Orleans -- got me thinking the index isn’t accounting for another factor significantly affecting the pleasure-pain measurement.

    I picked San Diego over Indianapolis in Week 3, a game in which the Chargers had a 22-20 lead and a 2nd-and-3 at midfield with less than three minutes left, but couldn’t make a first down and lost the lead on a long TD.

    The Chargers then got the ball back down four and promptly fumbled, then after getting it back one last time with almost no time left fumbled again. Indy won 26-22, with San Diego having gone from an 80.6% “win probability” (as ESPN is now measuring) with two minutes left to losing.

    Despite the pain caused by that failed pick, I chose San Diego again yesterday in their home game against New Orleans, and with just under seven minutes left the Chargers were up 34-21 with possession of the football. Win probability? 98.5%. But they fumbled, and the Saints got a quick TD. Then they fumbled again, New Orleans got seven more, and the Chargers lost 35-34.

    I didn’t actually see either game, save the last desperate minute yesterday when San Diego got the ball back one last time and lost 12 yards, then threw a pick. Reading box scores and play-by-play rundowns of the ends of these two games, the fumbles seem almost purposeful -- the surest way to lose the games. Bill Barnwell of ESPN even tweeted yesterday how San Diego was “trying so hard to lose this game,” and while I don’t actually think they were, it’s uncanny how efficiently they managed to let slip away an all-but-certain victory.

    I’m realizing the pain is heightened when being on the wrong side of these games, and is much greater than the pleasure of winning them, in my experience. I’m referring to games in which as a person trying to predict winners the game concludes in such a way that you cannot help but view yourself as being either “lucky” or “unlucky” when choosing either side -- you know, games decided by unlikely late turnovers, odd or incorrect calls by referees, missed field goals, and the like.

    I certainly like winning such games, but when that happens I can’t say I feel as though I’ve “earned” the check mark like I do when teams demonstrate less equivocally that I’ve chosen the right side (such as when I picked the Steelers last night and they crushed Kansas City 43-14). Meanwhile losing them feels especially bad, and even today I keep looking back and thinking how “undeserving” I am to have been rudely delivered that red “X” in the Chargers-Saints game.

    Each of the four categories above, then, could be split into four more subcategories -- the “lucky” win, the “non-lucky” win, the “non-lucky” loss, and the “unlucky” loss -- with the relative pain-pleasure calibrated for each outcome. Hmm... this is getting complicated. I may have to create a table or graph to represent it all.

    Silly stuff, I know. But the curious part of it is how what I’m describing is precisely the opposite of what happens (to me) in poker, where losing because of bad luck doesn’t hurt much at all, but losing because of my own poor decisions hurts significantly. Similarly, winning by getting lucky doesn’t bring as much pleasure as winning because of smart, skillful play.

    Will keep monitoring it all. And we’ll see if I can ever bring myself to picking the Chargers again -- or perhaps if I can start picking against the Panthers -- and what sort of pain and/or pleasure those picks will produce.

    Image: “fumble!” (adapted), Paul L Dineen. CC BY 2.0.

    Labels: , , , , ,

    Thursday, September 22, 2016

    Travel Report: LAPT9 Uruguay, Arrival -- Hemispheres

    Hello from Uruguay!

    My flights down to Montevideo were fine. No movies for the super long one from Miami, I’m afraid. Just the words “Fasten Seat Belt While Seated” stitched on the back of the seat in front of me to look at the whole nine-plus hours we were on there.

    My neighbor removing his shoes (and -- horror -- not wearing socks) before we even backed out of the gate didn’t necessarily help improve the situation much. But all in all, it could have been worse.

    Actually shared that flight down with my blogging partner for the week, Will, so the two of us had fun catching up during the long shuttle to Punta del Este. Had to wait a little while before rooms opened up, but it wasn’t too bad. By the time of unpacking I was around 20 hours or so removed from having loaded up my suitcase back on the farm.

    Always marvel a little at how it is possible to traverse the globe this way, traveling from the middle of the northern hemisphere down deep into the southern hemisphere -- like 5,200 miles, as I was calculating yesterday -- in less than a day. Probably challenges these two cerebral hemispheres knockin’ around in my noggin more than it should.

    Then later we met up with Sergio for what turned out to be a delicious dinner at Las Brisas, one of the restaurants in the Conrad Hotel & Casino (shown above) which will be our home away from home for the next several days.

    Capped the day off with some NFL football at the large, comfortable hotel lobby bar, and with the Patriots’ win over Houston I managed to nudge into an early lead in the Pigskin Pick’em pool, making for a nice conclusion to the long day.

    On the drive in and during the short bit of walking around I did today, I found it hard even to remember having been here before. It has been three years and I’m staying in a different part of the city, so that’s part of the reason. Also the Conrad is a big contrast (a good one) from the earlier digs, and so the whole feel has changed in part because of that, too.

    Gonna hit the hay now and try to recuperate a few of those lost hours of sleep from the flight before the tournament gets going tomorrow.

    Photo: courtesy Carlos Monti / PokerStars blog.

    Labels: , , , , , ,

    Thursday, September 08, 2016

    Football, Finally

    I’ve been guilty more than once here over the last couple of months of grumbling about the relative paucity of televised sports entertainment. It’s my own fault, really. Imprisoned by my own tastes.

    Sometimes the whining has come under the heading of pining for more poker on the teevee -- such as during the WSOP Main Event (which still hasn’t begun to be aired on ESPN and won’t start until Sunday). Definitely feel like there’s a valley here in the summer that poker could fill for a certain segment of sports watchers.

    I realize there are sports to watch during the couple of months that follow the NBA finals. It’s not that I don’t enjoy watching the occasional tennis match, fourth round of a golf tournament, soccer match, or baseball game. Or even (this year) the panoply of Olympic sports from last month, which I spent some hours enjoying during the first week at least before taking off for Barcelona halfway through the sucker.

    But for me the most enjoyable sport to watch on television is football, and I mean professional football. College is an okay diversion, but it ain’t nearly as engaging to me as the pro game.

    This year begins uniquely for a Panthers fan like myself, given how Carolina gets to play in tonight’s Thursday kickoff game in a Super Bowl rematch versus the Denver Broncos. It’s not an ideal spot to begin a season -- on the road, on a short week, and versus an above average opponent. But it’ll give us all an early idea how bullish we should be on the team this time around.

    Tonight’ll mark the first of 256 attempts at picking winners again as well as I jump back into another Pigskin Pick’em campaign. Hard to have much perspective with tonight’s pick, as we’re pretty well overwhelmed with unreasonable optimism regarding the Panthers around these parts. No Peyton for the Broncos (and an untested fellow in his place behind center) is encouraging many to go with Carolina as well, although I don’t necessarily think the QB situation will hurt Denver all that much.

    Ah well... no more fussing over it. Time to make a pick. The second-guessing is just hours away!

    Image: “Pigskin,” Eric Kilby. CC BY-SA 2.0.

    Labels: , , , , , ,

    Wednesday, December 02, 2015

    Season of the Witch

    Sometimes in all-in situations, say, when there’s one last river card to come, players will entertain themselves by calling out specific cards a beat before the card is revealed. “Eight of diamonds!” will shout a player, enacting a kind of prognosticator’s freeroll that gets promptly ignored if wrong, but celebrated if somehow the guess proves correct.

    That celebration is usually forgotten fairly quickly, too, as it should be. But it still can add up to a fun moment for those involved, the way it goofily suggests the gambler’s dream of extra-normal powers of perception.

    Last week while in Brazil, I was chatting with Reinaldo on Wednesday about the upcoming NFL games. He and I are both in the same Pigskin Pick’em pool and while we’re both far out of the running overall, we’re neck-and-neck with each other, and so are having some fun going back and forth about which of us will end the season with more correct picks out of the 256 total NFL regular season games.

    My Carolina Panthers played on Thanksgiving, and somewhat hilariously were an underdog to the Dallas Cowboys despite Carolina being 10-0 going into the game while Dallas was 3-7. The reason for the line, of course, was the fact that Dallas starting QB Tony Romo was back in the line-up, and so far during the year Dallas had lost exactly zero games when he’d played (three) and won exactly zero when he hadn’t (seven).

    Laying on a little bit of fan-fueled hyperbole, I pretended to express outrage about the Panthers being somehow disrespected by such a line. But in truth I knew the Panthers outmatched Dallas, even with Romo. “The Panthers will roll tomorrow,” I told Reinaldo. “In fact, they’ll knock Romo out of the game.”

    As I mentioned last week, we were able to keep tabs on the T-giving games while at the tournament, and so I greatly enjoyed watching Carolina fulfill my prediction as they jumped in front of Dallas, then continued to pull away as the third quarter neared its close. It was about that time I shot my buddy Rich Ryan a message.

    “Saw this coming all the way from South America,” I boasted. “I’m just surprised they haven’t knocked Romo out of the game yet.”

    Less than a minute after I hit send, Romo was sacked hard by Thomas Davis, reinjuring his collarbone and having to leave the game. Indeed, his season is over.

    “Sick timing brah,” replied Rich before I could even fire back an “ahem” to punctuate the uncanny coincidence of the message.

    Reinaldo was impressed as well, and after asking me what the male equivalent of a witch is, promptly called me a warlock. (That picture up above, by the way, is one of your humble scribbler from long ago, one Vera coincidentally found while I was gone.)

    Even though I have no particular feelings about Dallas, I’ve always liked Romo. And even if I didn’t, I obviously was not glad to have seen him get hurt. Even so I’ll admit to having experienced the momentary, frivolous pleasure that comes with guessing correctly.

    Labels: , , , , , , ,

    Friday, October 02, 2015

    Getting It Wrong

    Watched that Thursday Night Football clash last night to the bitter end. Was a pretty poorly played game, with a lot of endgame weirdness to create an unexpected outcome and thus enough extra drama to keep me watching to the last.

    A couple of weeks pack I shared a pleasure-pain ranking system for evaluating my Pigskin Pick’em picks. Last night’s game -- which I got wrong -- ended up way over on the extreme pain side of the spectrum.

    I picked the Steelers, who thanks to an unreliable field goal kicker and some especially bone-headed coaching decisions allowed the Ravens to complete a 13-point comeback to win in overtime. Making things worse, many in the pool (including the leader) had taken Baltimore, making it doubly unpleasant to lose after having with a couple of minutes left prematurely congratulated myself for having picked a winner. (Amateur move.)

    I mentioned how the Steelers’ field goal kicker, Josh Scobee, had a rough night, missing two in the fourth quarter. Both were very late, and both happened with Pittsburgh ahead 20-17. The first miss was a 49-yarder with 2:29 to go, and the second a 41-yarder with 1:06 left.

    As I had a rooting interest, I wasn’t happy to see Pittsburgh missing field goals. I was less happy, though, to see the Steelers even attempt them. Why? Because I was convinced each time that trying a field goal lessened rather than increased their chances of winning the game.

    If Pitt. had made either FG, they’d have gone up by six, thereby forcing Baltimore to drive the length of the field in the hopes of scoring what would be a winning TD. Down just three, Baltimore instead played for the tie and overtime, and after being unsuccessful on the first try did manage to do so when given a second opportunity.

    Because Pittsburgh missed their FG attempts, Baltimore played for the tie and overtime. They failed the first time, but given a second opportunity the Ravens were able to get close enough to kick a long tying field goal at the end of regulation.

    When Pittsburgh missed the first FG attempt, then, it more or less assured they would not lose the game in regulation, as the Ravens then went for the tie (they still could lose in OT, of course). If Pittsburgh had hit the FG, however, there would have been a non-zero chance they could lose in regulation. Weighing the chances of losing in overtime (after Balt. hit a game-tying FG following a Pitts. miss) versus losing in regulation (after Balt. scored a game-winning TD after a Pitts. make), I suppose hitting that first FG would have been marginally better than punting, although not by much.

    But when the Steelers held Baltimore on downs, then faced a similar decision with less time on the clock (and Baltimore having used their timeouts), trying the FG again was surely a poor decision (especially considering the inconsistent Scobee had just missed one). Punting and pinning the Ravens inside the 20 would have been a much, much better choice. Doing so would have further reduced the chance of Baltimore driving for a winning TD (because of a longer field), although that likely wouldn’t have been the Ravens’ aim, anyway, since the tying FG would’ve been a primary goal for them.

    A Twitter exchange at the time involving Grantland’s NFL guru Bill Barnwell succinctly summed up the situation. A follower asked him “why did Pitt go for FG?” adding “Wouldn’t you rather be up by 3 than 6 there? Have Balt play for FG and OT instead of TD and win?” (This is the point I’m making.)

    Barnwell’s response delivered the same observation in a different way: “NFL coaches optimize decisions to put off losing for as long as possible, not to win.” This was a point he made in greater detail a couple of weeks ago in a column where he was describing almost exactly the same scenario in a different game:

    “Trailing by three in a two-minute drill, coaches will almost [always] settle for a field goal to try to push the game into overtime,” explained Barnwell. “They optimize their decision-making to tie, which only improves their chances of winning to 50 percent (or whatever the implied odds were from the pregame spread), because they still have to win in overtime. Down six and without any other choice, they get aggressive and optimize their play calling to try to score a game-winning touchdown.”

    I’m trying to think of a decent poker analogy here (and struggling a little). Looking at it from the perspective of the team that is behind, being down a FG and playing for a tie would be like being short-stacked enough to fold your way into the money. Meanwhile being down six forces a team’s hand (so to speak), kind of like being too short to take the passive line of folding into the money and instead having to go into shove-or-fold mode.

    That’s not really describing the perspective of the team that is ahead here, though, who makes a choice that seemingly provides a temporary benefit but isn’t the best decision long-term. That would be a little like risking too much to win a single tourney hand when doing so doesn’t really improve your chance at realizing the more substantial goal of winning the event.

    All of which is to say, Pittsburgh’s choice to try a long field goal to go up six with less than two minutes to go -- a decision they ended making twice -- was at the very least questionable even if they’d had a more reliable kicker. And in fact, I tend to think it was just plain wrong (especially in the second instance).

    I’m remembering as I write this a game from two years ago in which Pittsburgh similarly decided to try a long field goal with less than two minutes to go in a close contest. In that case the game was tied and the FG was 54 yards, i.e., a would-be career long for their then-kicker Shaun Suisham. Things went similarly badly for the Steelers there, too, and in a post here I surmised their chances of winning were decreased merely by the decision to kick a FG instead of punt.

    Pittsburgh made some other bad choices, too, most glaringly with regards to a couple of fourth down calls in overtime. Indeed, I think last night it was obvious the team I’d picked had hurt their own chances of winning because of in-game decisions -- i.e., because of things they could control -- which definitely added to the pain of getting it wrong.

    Labels: , , , , , , ,

    Monday, September 14, 2015

    Pigskin Pick’em; or, the Agony and Ecstasy

    The NFL season has begun, and with it another foray into the agony and ecstasy of Pigskin Pick’em, a.k.a. “the pool.”

    As I’ve covered here many autumns before, we pick games straight up (not versus the spread). All 256 of them. I came out of the weekend having gotten 10 of 14, and since that wasn’t 14 of 14 I am necessarily full of second-guesser’s remorse.

    I was thinking this afternoon about the relative degrees of pleasure and pain these picks produce. Poker provides a starting place for such a discussion.

    It’s a common aphorism in poker to talk about how winning a pot produces less pleasure than the pain produced by losing one. Also relevant, of course, is the extent to which one’s winning or losing is the product of having made a good or bad decision as well as how much luck (also good or bad) affected the outcome.

    There’s a lot of luck involved with how NFL games go. But when it comes to picking them, I can’t really blame bad luck on having chosen this team or that one. That is to say, I think I play each “hand” here with equal “skill” (or lack thereof), with some being more difficult than others but my own action (the pick I choose) entirely determining whether I am successful or not.

    Thus when discussing how the pleasure and pain of each game compares, I’ll divide the games and outcomes into four groups as follows:

  • most pain: making non-consensus choice (usually an underdog), being wrong
  • least pain: making consensus choice (usually a favorite), being wrong
  • least pleasure: making consensus choice (usually a favorite), being right
  • most pleasure: making non-consensus choice (usually an underdog), being right
  • On the one hand, these rankings are essentially emotion-based. However, they also directly correspond to the actual value of the picks, relatively speaking.

    The most painful example of going against the grain and being wrong (as I was when I picked Oakland yesterday -- why!?!) hurts worse than missing a game everyone else does, too (as when I picked Seattle, like nearly everyone else). Meanwhile the most pleasurable outcome of going it alone and being right (as when I took Buffalo, as few others did) helps me more than getting the same game right everyone else does (such as when we all took Green Bay on Sunday).

    I’ve written before here about the “hero pick” (i.e., the non-consensus selection). I suppose if I wanted to lessen the emotional “swings” of the game, I’d avoid those or at least minimize them. But who wants to play that way?

    Labels: , , , , ,

    Tuesday, November 04, 2014

    Fantasy Draft and Relying on (Andrew) Luck

    If you read this blog you might follow me on Twitter, and if you follow me on Twitter we might follow a lot of the same people, meaning you very likely saw all of the poker pros and others tweeting about this $20K freeroll that happened over the weekend on this new Fantasy Draft website which is still in a “beta” stage and not quite up and running.

    I’ve written here before about how fantasy sports don’t exactly grab my interest, but like almost 2,200 others I decided to sign up and create a team for this past weekend’s NFL games in order to take a shot at the free cabbage due to go to the top 300 finishers.

    In truth what was being awarded was “fantasy cash,” not actual scratch, which I assume is money that can’t be withdrawn but which can be used to play in future tournaments (once the site starts having them).

    The site is actually very slick and easy to navigate, and it was easy enough to follow how things were going with my team on Sunday as the games played out. There are obviously some elements that are still in development, but I’ll confirm the site is simple enough for a relatively untutored fantasy sports player like myself to be plenty inviting.

    I had loaded up on some players in the Monday night game -- specifically Indianapolis Colts quarterback Andrew Luck and a couple of his receivers -- and so was sitting only in the middling range after Sunday’s games were over. But thankfully Luck had a big night versus the Giants, both my receivers caught TDs, and I grabbed enough points to make it into the money to earn $20 of “fantasy” cheddar. Was nice to win something, at least, as my Pigskin Pick’em entry this year is pretty much in shambles -- not quite #LOLJets bad, but close.

    We’ll see how things go with the site once it gets going for real, but if you’re curious about it you can sign up for an account by clicking here. Links to the site from this post contain my referral code, and it’s clear referrals are part of the overall strategy for the site -- a strategy that seems to be working somewhat well so far, actually, considering how many people already seem to be on it without the games having gone live yet.

    Still much prefer performing risk/reward calculations on flops, turns, and rivers than attempting the same with yards gained, receptions completed, and points scored. Feels a lot like making those WSOP predictions I was referring to yesterday -- a lot of shots in the dark.

    But given how fantasy sports are wholly legal here in the U.S. while online poker continues to be much less available, I might have to get over my aversion to the fantasy thing and figure out a way to make it palatable to me.

    Winning in freerolls is a start.

    Labels: , , , , ,

    Monday, October 13, 2014

    Picked Apart

    After six weeks of the NFL football season, I’m feeling as though I’ve been thoroughly picked apart as far as trying to pick winners in the Pigskin Pick’em contest goes.

    A month ago I was cheerily writing here about getting an average of two out of three games correct and how that wasn’t too bad, but by now I’ve fallen off that pace considerably and am already in a desperate spot in the pool near the bottom and a dozen games out of the lead just over a third of the way into the campaign.

    While yesterday didn’t go well at all for me, last week was even more difficult to get through after losing three early games in which the teams I’d picked all blew big leads. Even worse, all three were meaningful games as far as the pool was concerned, for which the picks were evenly divided and thus getting them right or wrong affected one’s standing more significantly.

    Below are the win probability graphs for those three games as calculated by Advanced Football Analytics where I’ll sometimes find myself much as when playing online poker I would end up over at Two Dimes after suffering an improbably bad beat -- kind of a masochistic seeking out of an answer to the question “How bad was that, really?”

    That’s right -- I had Chicago, Tennessee, and Detroit, all of whom had a WP of 80% or better in the fourth quarter of their games only to lose. The Titans were up 28-3 at home versus Cleveland before blowing their game 29-28. I also had Houston beating Dallas in the early game a week ago, and the Cowboys won in overtime, completing a four-game sweep of close ones going the wrong way.

    This week’s games featured fewer heartbreaks but a lot of surprises (at least for me), thus hurtling me even further down the leaderboard in the pool. Like can happen in poker after enduring a long stretch of losing, I’ve now entered a zone in which I’m doubting my ability to play this game at all. Sure, I might have won at it in the past, but was it all just dumb luck?

    I take a little bit of comfort knowing that I’m not gambling serious cabbage on NFL football -- indeed, I don’t bet on games at all. For those who are, I have great sympathy, especially after yesterday saw not one but two games end with “pick-6” interception returns for TDs that helped teams (Denver and Arizona) cover spreads during the final seconds.

    Speaking of, check out Nolan Dalla’s post today titled “Anatomy of an NFL Apocalypse” in which he spells out in profanity-laced detail the “impalement of the heart, mind, and wallet” that was NFL football yesterday.

    Labels: , , , ,

    Tuesday, September 23, 2014

    Aggression to the Mean

    Feeling a little angry after the last two weeks’ worth of picking games in the NFL Pigskin Pick’em pool. Can be a heartbreak, that.

    After hitting 11 of 16 the first week (and feeling good that hitting two out of three ain’t bad), I slipped to only getting 8 right out of 16 during Week 2. That was a rough week for many, actually, as the overall average of all the people playing in ESPN’s game was only 7 correct picks.

    Then during Week 3 I only hit 9 of 16 (below the average of 10), giving me 28 of 48 so far. That’s six behind the current leader in our group and squarely in the middle of the pack, and four behind my earlier stated “two out of three” goal.

    Was my first solid week an outlier, and have I now “regressed to the mean” (as they say)? Could be, but mainly slipping back to the middle just makes me feel mean.

    Was on the wrong side of some close ones as usually happens, although I did pick Seattle to best Denver on Sunday, a pick that looked pretty iffy once the Broncos made that remarkable last-minute drive to tie the game. But Seattle won the coin flip to start overtime, then drove the length of the field for a winning TD which according to the new OT rules ended things right there.

    I joked on Twitter after the game following Peyton Manning’s clutch series of passes to tie the game in regulation that he messed up with his final call of the afternoon. “Peyton really choked at the end, calling tails,” I tweeted, referring to that fateful coin flip.

    Some wanted to complain about the new OT rules following that outcome, but I like the rules exactly the way they are. The relative difficulty of scoring a TD with one’s opening drive is significant enough to make it worthy of denying your opponent a possession, I’d say. And I like the pressure that comes with a team either failing to score or only getting a field goal with that opening possession, after which the game does revert to the “sudden death” format.

    In fact, that OT format best replicates the back-and-forth that tends to happen during regulation, where in so many cases those final possessions end up deciding games.

    Makes the games fun to watch, the way they always seem to get all of the way to the river card (so to speak) with the outcome still in doubt. But tough to predict.

    Labels: , , ,

    Tuesday, September 09, 2014

    Two Out of Three Ain’t Bad

    Made it through that first week of the NFL season hitting a decent percentage of winners in the Pigskin Pick’em pool -- 11 of 16 correct (picking straight up), putting me one game back of the leaders who got 12.

    I much prefer picking games straight up than against the spread, not because it is any easier, but because it doesn’t twist me into what to me is an uncomfortable position as a fan having not to root for one or the other team to win, but rather for a certain, amenable final score.

    It’s the same reason why I still can’t bring myself to get involved very much in fantasy sports. As much as I love both sports and numbers -- a pair of predilections that I’ve always thought directly informs my love of poker, too -- I just can’t interest myself in the statistical tsunami of fantasy football.

    The start of the season reminded me of last year. For the first three weeks of the NFL season, 16 games are played each week (then the byes kick in). Last year I’d gotten 10/16, 10/16, then 9/16 for a so-so start of 29 out of 48.

    I was already eight games behind the leader, and thus ended up spending the entire season playing catch-up. By the end I was scrambling, picking lots of upsets in a desperate attempt to close the widening gap and ultimately finishing with just 156 of 256 correct (about the same percentage I’d hit during those first three weeks).

    That was way, way behind our group’s winner who picked 178 of 256 games correctly for the season (an impressive 69.5%). Meanwhile there was one genius out of the hundreds of thousands who played the game on ESPN who correctly picked 191 of 256 last year (74.6%). No shinola.

    In 2012, I hit 166 of 256 (64.8%), good enough to bubble the cash. The year before I also hit 166 of 256, which won me the pool that year.

    I was chatting with a friend yesterday who was showing me the results of picks made by the Football Outsiders over the last few years, including how they did picking games straight up. They’ve improved every year over the last six in that category, getting 171 correct each of the last two years.

    That’s getting just about exactly 2 out of every 3 picks right, a good line to shoot for. Getting 11 of 16 just barely beats it. Harder than it looks, though.

    Labels: , , ,


    Older Posts

    Copyright © 2006-2021 Hard-Boiled Poker.
    All Rights Reserved.