Bent, theJetsBlog.com | Follow on Twitter
The Bills could have easily won Thursday night's game against the Jets. In the end, though, the Jets executed better when it counted -- unlike last week -- and it get them across the finish line with a victory.
In a predictable, but initially effective game plan, Rex Ryan used the same defensive blueprint that opposing teams used to beat his Jets teams, daring the opposing quarterback to beat him downfield. The Jets didn't shy away from doing so and were able to have enough success to overcome three disastrous plays that saw the Bills, whose offense was otherwise pretty ineffective, score three out-of-nowhere touchdowns.
Ryan opted not to adjust his plan, gambling that Ryan Fitzpatrick would make a back-breaking mistake. Thankfully, he didn't and Ryan lost.
This was a bounceback game for the Jets.
For a change, it was their offense that carried them and did a good job rolling with the punches when faced with a couple of huge momentum-changing plays.
Any time you give up 17 straight points and still win, you know there will be both good and bad things to take from the game and that was definitely the case here.
Here are is additional analysis from Week 2, on...
1) Quarterbacks: Early in the game, the announcers mentioned how Ryan Fitzpatrick was one of the league leaders last year in throwing the ball downfield. What they didn't mention was the fact that he was among the worst in the league at having success when he did so >> Read more.
2) Offensive Line: Perhaps the most interesting outcome from this week's film review is that we have an early leader in the ongoing battle between Ben Ijalana and Brent Qvale for the starting right tackle job. Todd Bowles said during the week that someone needs to step up and take this role and Ijalana might just have done that >> Read more.
3) Running Backs: Matt Forte delighted fantasy owners by ending up with a 100-yard, three touchdown stat line, but he had to work hard to get there >> Read more.
4) Wide Receivers: It doesn't seem so long ago that we were bemoaning the inability of Quincy Enunwa to establish himself as a number-three receiver. In the first half Thursday, he basically established himself as a number-one >> Read more.
5) Defensive Line: I was hoping the team could surpass last week's sack total. However, they got to Tyrod Taylor just twice and both were chalked off due to penalties > Read more.
6) Linebackers: Every now and again, Darron Lee will show flashes of the dominant linebacker play Jets fans will be hoping from him all the time. On a fourth quarter run, he diagnosed the play, found his way cleanly into the backfield and stopped the back in his tracks for a loss. However, that came immediately after two preceding plays where he took a step in the wrong direction > Read more.
7) Defensive Backs: The Jets have some work to do in terms of their defensive backfield communication and maybe Darrelle Revis has to make some adjustments to account for that step he claims not to have lost >> Read more.
8) Special Teams: I've been optimistic about the abilities of the special teams, but they mostly did a poor job last night, particularly in kick coverage and the blocking in the return game > Read more.
The Jets have a long week to recover and prepare -- 10 days -- so they should hopefully be in good shape heading into a tough test against the Chiefs, who play the Texans this weekend.
The Chiefs were getting blown out in their first game before regrouping for a come-from-behind overtime win against the Chargers. Their defense was excellent after a bad start, but the Jets will have a good chance to look for signs of weakness from the part of the game where the Chargers were rolling.
With the Jets (1-1) on the board with a win, the season starts here. Here's to a stress-free weekend rooting for all our rivals to lose!
I'll be doing BGA mailbag posts every few weeks. However, if you have any pressing questions, leave them in the comments, e-mail me at firstname.lastname@example.org or tweet me @bent_double and I'll either respond below or include my response in the next post.