From a football and games picking perspective,this is a brief recap of some interesting week 10 NFL picks. (Week 11 picks against the spread can be found here.)
There were a few lucky picks by this blog last week – including a call of the Jets upsetting the Steelers outright (about 3 times, but once qualified with a “maybe”).
But yet all winning picks, as has generally been the case so far this NFL season (starting with week 7 when this blog’s picks began) have been by a reasonable margin against the spread, although the total official ATS record so far, if it’s being added up correctly (convenient, right?) is still 1 game under 500. (Note that the only other upset win offered by this blog so far (at least that I remember – I know, again, convenient, right?) was the outrageous one of the still awful Jacksonville Jaguars against the Browns in week 7, and Jacksonville won.)
But last week’s rather interesting picks started out with the debacle of missing probably my favorite call of the week, the (very same) Browns at the Bengals, followed by the debacle of this blog (see link) going on and on about how I loved the Browns in that game, and why.
Those picks, even without the in hindsight (if still technically non existent) brilliant Browns pick – as they were getting 6 points and clobbered the Bengals 24-3 – still almost went 4-0 on the early games. But they didn’t, going 3-1, as the Dolphins, leading late, lost by four.
But what was also interesting is that I suggested that if there was a game among those early afternoon games that wasn’t a strong pick (or would be a “letdown,” was my poorly chosen wording), it was the Miami – Detroit game!
Sure enough, Detroit came back at the end to win a close one, for the third game in a row.
This seems to follow a pattern with Detroit. Or this blog. Back in week 8 I picked them, giving up 3.5 points, to beat Atlanta in London, but expressed concerns about them not taking Atlanta – who were a well coached and historically hard fighting team who would not do the normal London “bad team essentially mails it in” shuffle – seriously enough.
And saying that if they didn’t take them seriously and lost the game, I would blame their coach. (not that he cares who I blame.) But also writing, amusingly in hindsight:
If the Falcons play tough, but the Lions pull out a close one, I’ll give Caldwell credit, and shoulder all the blame for this pick.
Which, after being down 21 – 0 early, is exactly what happened! Including me, later shouldering all blame, for the pick. (Which I do for all picks, except Oakland. They don’t count. Ever.) As the Lions pulled out the victory 22-21 at the end.
The last two Detroit games – including that Atlanta game – were both won by Detroit by a single point each. This one last week against Miami, after I again warned against the game, saw Detroit get the ball back with 3 minutes left, down by 3 point, and drive for the TD to win outright in the last half of a minute. (Maybe I should start listening to warnings I wrote out – or you should – since in week 8 I also warned, after picking the Bears +6 against New England, how “I’m also always wrong on the Bears.” I also questioned their heart in that post, and they went on to give up 50 or more points in back to back games (separated by a bye) for the first time by any team in the NFL since the 1923 Rochester Jeffersons. Side note: Maybe the now controversially named Redskins can re-take that name for their team, since it appears, last time I, ESPN, or Ted Cruz checked the NFL schedule, there’s no longer a Rochester Jeffersons team active in the league. I don’t think. Although they could be masquerading as the Raiders out in Oakland. Someone call George Clooney, he would know.)
That last moment Dolphins loss by exactly one point more than the spread knocked my “sweep week” to 3-1 (4-1 including the Browns. Though it was about to get a lot uglier in the later games.)
From a football angle, it’s worth noting how the Lions win at the end went down:
If you’ve watched a lot of NFL football, you’ve noticed how often teams have the ball and a less than one full score lead late in the game, and all they need to do is get a few first downs (or less) and the game is essentially over but then fail to do so.
Part of this is desperation on the part of defenses. But a significant part is lack of urgency on the part of offenses, who seem to play as if closing out the game is sort of a luxury, since at least if they punt “they are still leading.” (Forgetting that often by the time hat last second ticks, they won’t be, because their opponents now control the game, and have desperation, and often an effective four plays per each set of downs rather than three, to work with.)
This time, with a bit more time on the clock (3:13 left) Miami didn’t pull the “full turtle up,” by doing the football equivalentof pulling one’s head back inside of a shell:
Taking over with 3:37 left, they ran up the middle, gaining 5 yards on first down. So the run was reasonable on 2nd down.
But in hindsight, Detroit, who probably expected it, stopped them cold, and it might have been a good time for a short pass, and the “risk” of stopping the clock. (They need first downs and to burn off the rest of Detroit’s timeouts at this point, not just to “make sure” to run clock.)
On 3rd and 5 the Dolphins did pass, and it feel incomplete. Strategically at least, it was better overall than the Dolphins “full ostrich” at the end of the Green Bay Packers game in week 6, where they all but willingly gave the ball back to Green Bay rather than try to keep it and win the game. (But it may have only
Detroit only trailed 16-13, and often in these situations teams will ill advisedly play for ties, not wins. But Detroit, under Matthew Stafford, is not that kind of team. More importantly, they had 3:13 left to play with.
Once gain, urgency or not, one has to wonder if at the ends of games defenses don’t repeatedly play a little too soft, as it appeared the Dolphins – who remember held Detroit to 13 points all game – did here. Detroit also put together a nice drive, culminating in a deadly accurate side arm TD throw to Theo Riddick for the go ahead score in the last half minute of the game:
For those who missed the game, it should be noted that while the Chiefs pick panned out, it was a bad call. While it’s true Buffalo couldn’t get it done late, overall the Bills otherwise outplayed them this game
Several things worked against their side of the scoreboard however. For the team that is dead last in the NFL in red zone touchdown efficiency, perhaps the most notable was the loss of 7 points deep inside the red zone:
With 10:30 left to play in the 3rd quarter, running back Bryce Brown was running in for what would have been a nice looking 17 yard touchdown run and a nice 17-3 Bills lead. (They ultimately lost 17-13.) He made it the last five yards to the end zone somewhat easily, but unfortunately the ball didn’t travel with him those last five years – as Chiefs strong safety Ron Parker made an excellent diving play, almost torpedoing his body forward to knock the ball out of Brown’s hands. And the Chiefs recovered it in the end zone.
(It was also not just a loss of 7 points for the Bills, but a pure loss of 7. This means they lost possession of the ball, and lost the full 7 points, instead of scoring a normal touchdown -which except at the end of each half or a defensive score, means giving up possession as well. So by keeping the Bills from getting that 7 points, in terms of scoreboard mathematics, it was the equivalent of the Chiefs adding 7 points to their side of the scoreboard, without losing a possession – or half of a possession of however you want to look at it – in the process.)
For the late games, this blog added the Raiders (+11) and the Rams (+7).
The Raiders were leading the Broncos 10-6 with just a few minutes to go in the half, and playing lights out on defense (they had even batted down an amazing five of Peyton Manning’s passes so far, and manning rarely has balls batted down at the line of scrimmage).
Then they faltered, turning the ball over around midfield and giving up a touchdown, then quickly getting stopped and of course playing characteristically soft at the end of the half on defense (as if Peyton Manning didn’t come into the game with a whopping 35 points already scored in the final two minutes of the first half alone), and suddenly were behind 20-6.
This seemed to demoralize them, and they came out a different team in the second half, and Denver quickly ran up the score.
The Rams on the other hand were leading 14-10 almost halfway through the 4th quarter. Then they gave up a long TD throw to backup Drew Stanton, who’s the guy now for the rest of the season as starter Carson Palmer blew out his ACL on the prior series (and disappointingly for him, as he admitted crying later over not being able to directly partake in what he thought was a great season with an amazing bunch of guys), And now the score was, on the prior seasons, blew out his ACL. Now it was 17-14, and maybe the Rams would battle back, or maybe they would stay behind and the Cardinals would get the ball back and run out the clock.
Or, maybe Austin Davis would throw a pick, then on their next possession throw a touchdown pass, but to the other team. Then get hammered and lose the ball, which would be returned by the Cardinals for their second defensive touchdown in a row, and a somewhat out of the blue 31-14 win. Which is what happened.
Davis was demoted after the game, as career back up Shaun Hill, injured to pave the way for third string rookie Davis in week 1 has been reinstated as the starter. (The Rams don’t really need to see what Davis can do or develop him further for next year as a starter, since they have regular starter Sam Bradford coming back next year.)
Final record, 3-3, and some interesting football.