-
Posts
23,920 -
Joined
-
Last visited
Content Type
Gallery
Profiles
Forums
Events
Everything posted by dave mcbride
-
Week 2, Rayduhs v. Bills - Predict the Score
dave mcbride replied to Freddie's Dead's topic in The Stadium Wall
I hate to bring this up, but Jimmy G is 41-17 as a starting QB. He played well against a talented Denver D too. And Davante Adams is arguably the best WR in the league. The Bills are going to need to put up points in this one. I don't know how good the Raiders defense is, but Maxx Crosby vs. Spencer Brown strikes me as a problem. -
Week 2, Rayduhs v. Bills - Predict the Score
dave mcbride replied to Freddie's Dead's topic in The Stadium Wall
Anyone else worried about LDE Maxx Crosby vs. RT Spencer Brown? -
I'm not saying run it every play; I'm saying shift to a run-heavy under-center mode with a non-fumbler, work in play action, and don't turn the goddamn ball over and you'll likely win. Murray never fumbles, and making safe passes on occasion gets you another field goal opportunity or two. It's not like they were passing to set up the run or running to set up the pass; they ran only to slow down the d-line pass rush (or so it seemed) and got into a chuck-and-duck mode that resulted in a ton of turnovers. The only way you lose to Zack Wilson with a ten-point lead is if you play high-risk pass-the-ball-75-percent-of-time-against-an-elite-pass-defense, and that's exactly what they did. Allen was horrible, but the game plan didn't change to account for circumstances and that's on the OC.
-
83.4 is a very low grade from him and he was quite tough on Allen (deservedly so). He seems to be basically arguing that Allen performed poorly 17 percent of the time, which isn't a road to success. Anyway, I wouldn't equate his grading system with that used for a ninth grade math test.
-
It's more about situational football -- having a lead against a team with a very bad QB and sticking with a pass-heavy attack when you could play smash-mouth with a non-fumbling tackle breaker (Murray) with some play-action mixed in and then cruise to victory. Dorsey stuck with his initial gameplan despite the circumstances drastically changing (i.e., Rogers going down at the very beginning of the game). When the facts on the ground change and the situation calls for something else that might not be as flashy but which will more likely lead to a victory, you adjust. He didn't.
-
What will happen with Josh over the next month?
dave mcbride replied to Simon's topic in The Stadium Wall
Your choice, but I'd read the entire thing rather than dismissing it because you disagree about the interpretation of one particular play. -
Rough season opening losses— are we snake bit?
dave mcbride replied to Miyagi-Do Karate's topic in The Stadium Wall
That kick occurred in a blinding rainstorm. -
What will happen with Josh over the next month?
dave mcbride replied to Simon's topic in The Stadium Wall
From The Athletic this morning: https://theathletic.com/4858584/2023/09/13/bills-offense-josh-allen/ Allen took five sacks and nine hits. He was hit on five of his scrambles, too. So where did the pressure come from? According to TruMedia, Spencer Brown was the main culprit with four pressures allowed. O’Cyrus Torrence and Connor McGovern each allowed three pressures, and Mitch Morse and Dion Dawkins each allowed two. Assigning credit and blame for pressures and sacks isn’t always cut and try, so we went back through to see where things went wrong. Sack one: Brown was walked back into the quarterback and clearly deserves blame for the sack. Sack two: This one actually looked like a design run on which Allen got poor blocking and had nowhere to go. Hit three: Allen was hit on an incomplete pass early in the Bills’ only touchdown drive. Again Brown got overpowered and thrown back into Allen, who rushed an off-target throw that Jets linebacker C.J. Mosley dropped. Sack three: With 40 seconds left in the first half, Allen dropped back and had a decent pocket. But the Jets sent six rushers, and Allen didn’t get rid of the ball quickly. Instead, he stepped forward into the pocket and fell into a sack for a short loss. Sack four: Midway through the third quarter Allen had a clean pocket after faking a handoff to James Cook. He dropped his eyes almost immediately and then stumbled to the ground for a sack. This one was entirely on Allen. Hit six: On the next play, Mitch Morse got beat clean, knocking Allen off his spot. Allen launched a pass into double coverage intended for Stefon Diggs that became his second interception of the night. Sack five: Early in the fourth quarter, the Jets sent five rushers. Again, Allen’s eyes dropped when he thought he saw a running lane. But Jermaine Johnson beat Connor McGovern and brought Allen down for the sack. Hit eight: The Jets got a free blitzer through, which happens. Allen made a great play to avoid the rush and flip the ball to Latavius Murray for a decent gain. Hit nine: With 16 seconds left in regulation, Torrence allowed pressure but not before Allen got plenty of time to hang in the pocket and try a deep pass to Gabriel Davis down the sideline. This wasn’t much of a negative play for the offensive line. Brown’s inconsistency is a problem but not a surprising one. The Bills started to give him extra help, so they understand this is an issue. The more concerning trend was Allen dropping his eyes early on multiple occasions. That’s a habit that was more common from him in 2018 and 2019. He’s either not trusting his protection, not trusting his receivers to get open or not trusting what he’s reading in the defense. Maybe it’s a combination of the three. -
A bit deceiving. Sony Michel had 931 yards in 2018 and the Eagles finished 3rd in rushing yards in 2017. Also in 2018, the Pats finished 3rd in rushing attempts and 5th in rushing yards. Good RBs are an asset provided you have a great QB (which the Bills have).
-
New year, same issues with play calling and use of personnel
dave mcbride replied to Alphadawg7's topic in The Stadium Wall
But in a game where Zach Wilson is the emergency backup QB, another FG would have sealed the deal. As I have said in other threads, look at Murray’s fumble stats in the last 750 or so carries: one fumble. And he breaks tackles. -
Welcome back, AKC! D-line equity FTW! 😀
-
Not my point, but whatever. I've said multiple times that Allen was terrible and blew the game. But more than one thing can be wrong with an offense.
-
We can agree to disagree. I don't buy what you're selling and you don't buy what I'm selling. Fair enough. For the record, though, I thought that Allen was godawful last night and cost them the game. I mean, that's freaking obvious. But more than one thing can be wrong on a team.
-
See my point above about situational awareness - both of the score and the quality of the opposing offense. And they literally signed a big back who almost never fumbles.
-
I'm not saying never throw, of course, but I do think that you shift to ball control mode with a big back who almost never fumbles (Murray, who has one fumble in his last 722 carries and two in has last 938) with the occasional safe play action play. Maybe you get another field goal or two, and then put the pressure on Zack Wilson to make a play. Outside of the two early runs by Hall, the Jets did nothing on offense. Hall had 8 carries for 18 yards the rest of the way. Anyway, I'm asking for situational awareness from the OC. I didn't see it last night.
-
Well, I certainly don't disagree with this. But if you're an OC and see this happening -- and you have the lead against a team led by Zach Freaking Wilson -- you adjust your plan. I didn't see that last night.
-
When you're giving up that many sacks and averaging 4.6 net yards per passing play (and passing plays bring more risk than running plays), it's not working. Plus think about the opponent: Zach Wilson is horrible and the Jets' o-line is a sieve in pass pro.
-
?? -- The Bills had nine negative plays on dropbacks: 4 turnovers (one of which was a fumble out of the shotgun) and five sacks. They had 217 net passing yards on 47 dropbacks (including the fumble play) which is 4.6 yards per passing play. That's horrible.
-
I don't know how many times I need to say this, but the Bills had the lead for most of the game and running plays are generally safe plays. Why not play ball control against a team with a terrible QB? They also slow down pass rushes because d-lines have to play differently. The Jets have a good run defense, but their pass defense is even better. Again, I thought Allen was terrible last night. Not trying to deflect blame, but more than one thing can be wrong.
-
Tell that to the 49ers and the Eagles. Run pass balance is used to HELP the passing game because it slows down a pass rush. The Jets were defaulting to pass rushing all night because the Bills were dropping back at such a heavy rate.
-
I'm sorry, but there are reasons that teams run the ball on occasion. And they especially run the ball when they have the lead. By my count, the Bills called running plays 27 percent of the time against an EXCELLENT pass defense from front to back. And they had the lead for close to two thirds of the game.
-
If you run the ball a lot defensive line movement is different -- it's more lateral. It literally slows down pass rushes, which is why teams do it. He was sacked 5 times and hit 9 times.
-
Hardly ever running it leads to jailbreaks on pass rushes versus an overmatched o-line. And that's what happened -- 5 sacks and a lot of hits. Of course Allen was terrible too, but the OC didn't help him. Not my point; of course he was terrible. But more than one thing was bad last night, and the two things -- OC and QB -- fed each other.