10 Thoughts Following Latest Bills Loss

Posted on November 1, 2010 by Patrick Moran

buffalo bills logoI’m not going to delve into every gruesome detail of the Buffalo Bills latest “heartbreaker” Sunday at Kansas City.  For one, I’ve been on a tremendously undeserved mini-vacation for the past four days.  Therefore, you’ve probably had the game dissected a million different times by now, courtesy of every Bills-related website in the world.

The bottom line is this: The Bills showed up on the road, played hard, gave it the ole’ college try, held the home team to 13 points… and still found a way to lose.

They had every opportunity in the world to cash in their first win, caught Chiefs head coach Todd Haley managing his team in the most amateurish of fashion, had a field goal opportunity to win the game, and blew it. Buffalo woke up to today with a record of 0-7 and cementing their status of being at the bottom of every NFL power rankings poll coming over the next few days.

I’ll be perfectly honest with you. Maybe for the first time ever, and definitely for the first time this early in the season, I don’t mind the Bills losing. If there was ever a NFL organization in need of bottoming out, it’s this Buffalo team.  The good news is they’re getting closer to accomplishing said goal with each passing week.  San Francisco and Detroit picked up their second wins of the season Sunday, leaving Dallas and Carolina as the only one-win teams left in the league.

If the Bills keep up their consistently non-stellar play, they may get that top pick wrapped up by the end of November.

Bring us the next Ryan Leaf or JaMarcus Russell.

As I said in the outset, I’m not going to analyze every facet of yesterday’s 13-10 overtime loss.  I do, however, have ten points in need of getting off my chest, and Aaron Maybin’s second straight scratching isn’t one of them.

♦ A lot of people tend to get too scientific and over analyze every Bills loss.  For now, let’s just keep it simple.  The Bills on Sunday lost a game they should’ve won because this year and for the majority of the past decade, they have a loser’s mentality.  Nothing more, nothing less.  Do you know how as a fan, you’re watching the game and no matter the situation, you literally expect the Bills to end up coming short when the final gun sounds? Well, trust me the team feels the same way. They certainly close games out like it.  They work hard during the week, so I’m not calling them quitters by any means. But they don’t know how to win and when you don’t, you find ways to lose.  When it comes to this organization, the age-old philosophy rings true more than anywhere else that good teams find ways to win and bad ones find ways to lose.  Over the past five or so years, the Bills have found nearly every imaginable way to lose, so this game was merely the latest chapter.

♦ Never thought I’d have to include Brian Moorman as part of an explanation for a Bills loss, but it happened at Kansas City. He was terrible late in the game and it cost the Bills valuable field position.

♦ I’m starting to get angrier at the Chris Kelsay extension than I am for ANY of the Bills bust first round draft picks over the past decade.  At least guys like Donte Whitner, Maybin, John McCargo and Mike Williams brought the element of the unknown to the NFL, just like any college player going to the next level.  Meanwhile, the Bills organization had several years to evaluate Kelsay, determine his worth and figure out what to do with him.  He’s been complete garbage this year, isn’t likely to get better at this stage of his career and yet the front office rewards him with a $6-million per, four-year extension.  It’s hard to fathom what Ralph Wilson, Buddy Nix, Russ Brandon and the upper-heads are thinking these days.

♦ If you were fortunate enough to miss the game and only saw that the Bills gave up 13 points, you’d think the Bills defense was solid. They weren’t.  Kansas City grounded up 274 rushing yards on a run defense that was already last in the league in stopping the run.  Jamal Charles ran for 177, including eight yards per carry.  They did “hold” backup running back Thomas Jones to 77 yards on 19 carries.  The reason the Chiefs didn’t put a pile of points on the board is because Haley and offensive coordinator Charlie Weiss called one of the worst game’s I’ve ever seen in my life.  Why Matt Cassel attempted 26 passes when the Chiefs could’ve ran for 400 yards is beyond me.  Think Chicago’s Matt Forte is licking his chops right now?

♦ The good news is the Bills didn’t give up a monster game to a tight end.  But while Kansas City failed to generate a touchdown from their tight end, little-known Tony Moeaki still hurt them with three big catches for 45 yards, including a huge 18-yarder that helped set up the Kansas City win.

♦ Stevie Johnson had another big game with a franchise-record tying touchdown catch for a fifth straight game. He’s legitimizing himself further each week as a reliable starter.  After seven games he’s up to 409 receiving yards and six scores, giving him an excellent shot at 1,000 yards and 10 touchdowns.  The Bills have many holes to fill over the next few years, but with Johnson, Lee Evans, Roscoe Parrish, David Nelson and perhaps Marcus Easley next year, wide receiver isn’t one of them.

♦ I’m not going to comment on Ryan Fitzpatrick too much because I was never that high on him to begin with, even after the Baltimore game.  Fitzpatrick is what he is; a well above average backup quarterback that can make plays in the short term, but he’s not a long-term answer by any means. His numbers Sunday weren’t horrendous (24-of-48 for 230 yards, 1 TD, 1 INT), but he made plenty of mistakes as the game was on the line late. I’ve heard plenty of talk recently, mainly by fans, saying the Bills should address other needs in their next draft ahead of quarterback. I say that’s complete nonsense.  If Andrew Luck, Ryan Mallet or a quarterback the Bills really love is available with the first few selections, they better take him.  The kind of play you got Fitzpatrick Sunday is what you’ll see out of him 9 of 10 times, and it’s not going to get you a lot of wins.

♦ I’m losing my patience with the lack of playing time for C.J. Spiller. Six carries Sunday for 17 yards, and four catches for 28 yards.  In seven games he has just 120 rushing yards and only has 32 carries.  If you’re going to take him ninth overall and project him to be a game-changer, then he has to see a lot more action. It won’t happen on the sideline. The Bills are 0-7 and with respect to Fred Jackson, who’s a fine running back, it’s time to start going to Spiller because frankly, thoughts of Eric Metcalf or Blair Thomas, depending on your perspective, are creeping into my head.

♦ People thought Kyle Williams would be the weak link to this new Bills defense. To this point, he’s been one of the lone bright spots. The undersized Williams continues to hold his own on a unit woefully underachieving.  He had two sacks Sunday and a team-high three for the season.  Along with Dwan Edwards, Williams is the only one pulling his weight on the defense.

♦ Lastly, the Bills failed to record an interception again against the Chiefs and near the halfway point of the season, the stat sheet reads one total team interception and zero by the secondary.

That’s pathetic… so is watching this team right now.  Next up are the reeling Chicago Bears Sunday in Toronto.  Who else sees this being the game the Bills finally put it together, pissing off the majority of Bills fans even more that it happens in Toronto?

Share and Enjoy:
  • Print this article!
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks

Leave a Reply

Add Your Comment

Read This Before Leaving a Comment

Please make sure your comments follow our guidelines:

  • Use your real name, not keywords
  • No signature links in your comments
  • No foul language (please)

Comments that do not adhere will be deleted or marked as SPAM.

by Comments Policy for WordPress
 

SEARCH BSD
Phrase:
FOLLOW US