BigDeacEnergy
Well-known member
- Joined
- Apr 6, 2020
- Messages
- 966
- Reaction score
- 862
He also takes off way too early (but still slowly) and doesn't get the first down.Lol "turtles in the pocket." That is exactly what he does
He also takes off way too early (but still slowly) and doesn't get the first down.Lol "turtles in the pocket." That is exactly what he does
It's very obvious live that he looks at one receiver and if that dude isn't open then he runs. I suspect the coaches told him to do this to avoid sacks since he has no pocket presence and can't progress through reads.He also takes off way too early (but still slowly) and doesn't get the first down.
I agree.It's very obvious live that he looks at one receiver and if that dude isn't open then he runs. I suspect the coaches told him to do this to avoid sacks since he has no pocket presence and can't progress through reads.
Duke's 10 4th quarter points came on drives of 54 yards for a TD and 48 yards and a FG. The FG drive was embarrassing, but the offense gave Duke a short field on both of those drives.
It sure looked like a designed play.My favorite play from last night, FWIW, was on 4th and short running our slowest back parallel to the LOS. I refuse to believe that was the actual play call and think that the OL just buckled and forced him to run that way, but a few F bombs may have been yelled about that call.
The worst thing is that he can't hold on to the ball when he runs so we just trade the probable sack/INT for a probable fumble.I agree.
What about Duke's 3 play 60 yard TD drive or the 14 play 75 yard TD drive in the 2nd quarter?
Sure the offense gave Duke a short field in the 4th but this defense once again failed to get key stops against a one dimensional offense when the game is on the line
I would disagree that Wake got beat in all three phases of the game. Special Teams absolutely. We outgained them 400-257 and 6 to 4.5 yards a play, had a more successful 3rd down rate, had a higher red zone success rate (this was basically a tossup though) and lost the turnover battle. The two turnovers, the two missed field goals, and the idiotic penalties on their last two scoring drives were the difference.
It doesn't matter at all since we lost but I'd imagine on the "how badly did we lose" chart and post game win expectancy charts that we "did not lose badly at all" and "should have won" based on how the game played out. Of course this gets into why did we lose and I think you don't have to look much beyond ill timed Mitch Griffis, bad kicking, dumb defensive plays, and somem questionable coaching decisions.
Well. Let's put it another way. If I'm Clawson, NO job is safe in December. This team is putrid.Not sure getting rid of the only coordinator with a track record of success is the way to go here.
A better question would be why our 3rd defensive coordinator hire in a row continues to allow struggling offenses to miraculously "get right" when playing against Wake
The D has been fine. They also clearly know that the weight of being in the game falls on them. Can you imagine the mental toll it takes to keep stopping decent teams and then immediately give the ball back to them? Or knowing that if you give up one touchdown at all you may be out of the game?What about Duke's 3 play 60 yard TD drive or the 14 play 75 yard TD drive in the 2nd quarter?
Sure the offense gave Duke a short field in the 4th but this defense once again failed to get key stops against a one dimensional offense when the game is on the line
And the 48 yard "drive" included 30 yards of dumb penalties.Duke's 10 4th quarter points came on drives of 54 yards for a TD and 48 yards and a FG. The FG drive was embarrassing, but the offense gave Duke a short field on both of those drives.
Our offense is last in scoring in the ACC.
If Lobo were OC, what would we be saying? Can him.
And the 48 yard "drive" included 30 yards of dumb penalties.