Week 1: The good, the bad, and the missing

[Alphadawg7]

52 minutes ago, VW82 said:

I thought Shaq Lawson was excellent. He's so skilled at batting down balls at the line and even though his initial rush isn't anything to write home about, his second effort yesterday was very good. There was a lot to like defensively vs the Jets and Shaq was near the top of the list.

 

100% agree, but the D had so many good performances on it that my OP would have been twice as long if I singled them all out.  But Shaq has himself a game for sure.

25 minutes ago, PromoTheRobot said:

Can't see why Daboll on the bad list. His offense worked all game, derailed only by stupid turnovers. If anything waiting to use Singletary was a stroke of genius. The Jets had no answer.

 

I felt he struggled in the first half with some of his play calling.  I also felt he stuck too long with Gore and should have looked to get Singletary involved earlier as well as I thought we had a real opportunity to get our RBs more involved in the passing game early too.  The first play in the second half was terrible too, and honestly will admit that stuck with me a lot and led me to lend towards the bad.  But I did give him credit for adjusting in the second half and I still feel good about Daboll, was just being honest on how I felt about this one game.  Just like I feel real good about Cole too despite the rough game.

[Jerome007]

It's only ONE game. Before you guys start cutting players, chill out.

 

It's OK to mention it all and "take notes" though. But you know what? I'm sure the coaches do too...

 

Edit: in the Good, I'd add Morse. The botched 4th and 1 was him but so little snaps during preseason. In the 2nd half, he was all over the field. That dude can really run for an Olineman! 

Edited September 9, 2019 by Jerome007

[TBBills Fan]

2 hours ago, DabillsDaBillsDaBills said:

I'm more than a  little worried that Gore had 11 carries to Singletarys 4. I'm having the worst flashbacks to Michael Tolbert, I thought I had repressed those memories.  

 

 

I think that has more to do with the Vet getting the first start and opportunity, now that he did, and Singletary came in and did what he did the number of reps will shift greatly to singletarys favor 

 

 

[Patrick Duffy]

1 hour ago, Alphadawg7 said:

 

Did you NOT read my post where I called out Foster and every WR NOT named Brown?  Lmao, it’s all you focusing on Zay, not me

Probably not. It must have been too long of a post and some may have "skimmed" over it and missed that part. lol, my guess anyways, or yeah it's the other.

[BuffaloBill]

It’s really hard to evaluate this game because for 1/4 of the team (if you split it up as offense, defense, special teams and coaching) the first half of the game was about is bad as it can get.  I don’t put Dabol in with this as the Bills were moving the ball until players killed drives with turnovers and penalties.

 

As for the “Beasley” interception I don’t find him as much at fault as you do.  I think it is a 50/50 on him and Josh both.  Josh was inaccurate and behind and is often the case the ball came in hot.  Beasley is a NFL wide receiver so I get it that “you get your hands on the ball, you catch the ball” however he was asked to catch a tough ball.  Let’s hope they both learn from the play.

 

It’s time to move on.  All that matters is a W was checked.  On to the Giants.

[1ManRaid]

3 hours ago, Alphadawg7 said:

1. HONORABLE MENTION:  Duke Williams:  I am sure I will get flack here, HOWEVER, watching the game yesterday I could not help but think Allen could have really used someone with a big catch radius who goes and fights for the ball.  If the above 3 cant start making an impact, I think Duke may get his chance sooner than some think.  And I don't expect Duke to come in and make a Pro Bowl, but his big catch radius and reliable hands could be useful to a young Allen IMO.  

For a second I thought you were the guy who compained that Duke needs to "get more game time", not realizing he is on the practice squad.

1 hour ago, SlimShady'sGhost said:

Isn't this a fallacy?

 

The Bills Defense gave up 11 points 

6, 2 pt cnv and a FG.  

Yeah, the pick six and safety weren't on the Bills D, but what game were you watching where the Jets scored a field goal?

[Nextmanup]

 Allen's performance proved to be good enough yesterday.

 

But it will not be nearly good enough going forward. 

 

 

[Pine Barrens Mafia]

1 minute ago, Nextmanup said:

 Allen's performance proved to be good enough yesterday.

 

But it will not be nearly good enough going forward. 

 

 

 

65%, 300+ total yards, 2 TD.

 

Not NEARLY good enough for Nextmanup.

 

[1ManRaid]

2 minutes ago, Nextmanup said:

 Allen's performance proved to be good enough yesterday.

 

But it will not be nearly good enough going forward. 

 

 

Despite the numerous fluke turnovers, in the first half (with Mosley still in) the Bills O still managed 12 plays of 8+ yards, and 3 plays of 25+ yards.  We were better to the eye than on paper.

[ddaryl]

3 hours ago, Alphadawg7 said:

Good:

 

1. Beasley:  Love the signing, love the potential still this season.  But there is no sugar coating this, he had a bad game and made to huge mistakes, both of which could have cost us the game.  The pick 6 put us in a hole, and then the best pass by Allen on the day he dropped in the 4th quarter.  Both plays almost lost us this game and the offense as a whole bailed him out or we would have lost this game and either play would have been big reasons why.  

 

 

 

I'm just not calling the pick 6 int a Beasley Mistake. It was a low quick dart throw that took and unfortunate bounce. Better throw and its caught, or if Beasley doesn't catch it and it ends up an inc we would be calling it a less that perfect throw by Allen

 

the 2nd pass late that he dropped was his fault as I did not see him aggressively go after the ball he let it come to him 

[billsredneck1]

3 hours ago, Mike in Horseheads said:

Pretty spot on. Bob Foster will end up cut, he was the best of the worst wr's in the league last year. No he's a after thought.

we need him opposite brown. the two of those could take an entire secondary out. ....and  make some huge grabs.  what i never understood is only having one take the top off guy.

with two that opens up the rest of the field.

[DuckyBoys]

I think you will see the #3 and #4 wrs more involved when we face teams with good secondaries  Beasley and Brown were getting open so Allen didnt have much reason to go his 3rd or 4th reads

[thebandit27]

3 minutes ago, ddaryl said:

 

 

I'm just not calling the pick 6 int a Beasley Mistake. It was a low quick dart throw that took and unfortunate bounce. Better throw and its caught, or if Beasley doesn't catch it and it ends up an inc we would be calling it a less that perfect throw by Allen

 

the 2nd pass late that he dropped was his fault as I did not see him aggressively go after the ball he let it come to him 

 

It hit Beasley in the hands.  I know Allen throws the ball hard, but this is the NFL.  If you can't catch a ball that hits you in the hands, that's a real problem.

[ddaryl]

Just now, thebandit27 said:

 

It hit Beasley in the hands.  I know Allen throws the ball hard, but this is the NFL.  If you can't catch a ball that hits you in the hands, that's a real problem.

 

 

Not blaming Beasley on that pass and still don't understand why anyone would. It was a bad bounce on a less than perfect pass. 

 

At best I wil give you a 50% share blame with Allen but this Beasley had a real bad day is laughable to me.

[dpberr]

I'm curious as to whether the Bills rebounded when Daboll stopped running his play scripts and started calling plays based on what the defense was showing.

 

His absolute allegiance to running play scripts is going to get the Bills in trouble (again).  I'm not sure if 14 straight passing plays and running it up the gut from your own end zone with a 36 year old running back is arrogance or Jauron-esque stupidity.  

 

[thebandit27]

5 minutes ago, ddaryl said:

 

 

Not blaming Beasley on that pass and still don't understand why anyone would. It was a bad bounce on a less than perfect pass. 

 

At best I wil give you a 50% share blame with Allen but this Beasley had a real bad day is laughable to me.

 

I don't think anyone said that Beasley had a real bad day (or at least I didn't see it).  He did, however, have 2 drops that hurt the team.

 

If you don't want the ball to hit Beasley in the hands on that throw, where do you want it to hit him that wouldn't be Allen's fault?

 

I mean, sheesh:

 

 

Edited September 9, 2019 by thebandit27

[ddaryl]

3 minutes ago, thebandit27 said:

 

I don't think anyone said that Beasley had a real bad day (or at least I didn't see it).  He did, however, have 2 drops that hurt the team.

 

If you don't want the ball to hit Beasley in the hands on that throw, where do you want it to hit him that wouldn't be Allen's fault?

 

 

Bad throw low. unfortunate bonce. Plenty of people here posting Beasley had a really bad day.

 

I agreed with the 2nd drop as being a Beasley thing... but the 1st NO. Unfortunate bounce on a low dart throw

 

 

[Alphadawg7]

22 minutes ago, ddaryl said:

 

 

I'm just not calling the pick 6 int a Beasley Mistake. It was a low quick dart throw that took and unfortunate bounce. Better throw and its caught, or if Beasley doesn't catch it and it ends up an inc we would be calling it a less that perfect throw by Allen

 

the 2nd pass late that he dropped was his fault as I did not see him aggressively go after the ball he let it come to him 

 

That’s fair, pass could have been better.  But IMO, it was still on Beasley because it was catchable and one you expect him to make.  But I won’t argue the pass could have been better placed.  

 

1 hour ago, Jerome007 said:

It's only ONE game. Before you guys start cutting players, chill out.

 

It's OK to mention it all and "take notes" though. But you know what? I'm sure the coaches do too...

 

Edit: in the Good, I'd add Morse. The botched 4th and 1 was him but so little snaps during preseason. In the 2nd half, he was all over the field. That dude can really run for an Olineman! 

 

I actually considered Morse but omitted him solely on the turnover.  But agree, he definitely made some plays out there 

Edited September 9, 2019 by Alphadawg7

[thebandit27]

Just now, Alphadawg7 said:

 

That’s fair, pass could have been better.  But IMO, it was still on Beasley because it was catchable and one you expect him to make.  But I won’t argue the pass could have been better placed.  

 

Sure, it could have been better. IMO, if you're an NFL receiver, and you have an unimpeded sight line to the ball, which then hits you in both hands directly from the QBs release, with zero contact, you absolutely have to make the catch.

[Alphadawg7]

15 minutes ago, ddaryl said:

 

 

Bad throw low. unfortunate bonce. Plenty of people here posting Beasley had a really bad day.

 

I agreed with the 2nd drop as being a Beasley thing... but the 1st NO. Unfortunate bounce on a low dart throw

 

 

 

2 bad drops in 9 targets, both of which almost cost us the game isn’t a bad game?  He was fortunate in the drop in the 4th the offense bailed him out or we might have lost the game.  That was for a first down on one of our game winning TD drives.  

 

I love Beasley, but he’s not above criticism when he makes mistakes.  I am also not worried about him either and believe he’s gonna have a strong season here.  

 

6 minutes ago, thebandit27 said:

 

Sure, it could have been better. IMO, if you're an NFL receiver, and you have an unimpeded sight line to the ball, which then hits you in both hands directly from the QBs release, with zero contact, you absolutely have to make the catch.

 

This ^

 

I am in full agreement with you on this.  I was just stating that it’s fair to say the ball could have been better placed, but ultimately that was more than catchable and should have been caught.

Edited September 9, 2019 by Alphadawg7