drvenner
#LiftUpEllie
- Joined
- Jan 17, 2010
- Messages
- 44,822
- Likes
- 189,445
The proper throw would have been low and to Jennings's right. Window was there he just missed it. Wasn't a difficult throw either.
It's a big one, though. Every single base is important in the post-season. You don't give them up because you don't run hard out of the box. You just don't do that.You say this after the two run dinger. Par for your course. Which sucks.
Of course he needs t hustle more... sometimes. That’s his only fault.
i don’t see it that way. The point of DWAs route is to clear out that middle for Jennings. You’re not running a 3drop Timing hitch at the goaline very often if ever. I think he’s waiting on him to come across and when he doesn’t it kind of throws JG off and Then that’s the throw he gets. Not saying you’re wrong or I’m right just this is how it makes sense to me.Disagree, if he expected him to keep going I wouldnt think the ball would end up on his back shoulder. This is a good illustration of JG's lack of anticipation as much as anything. Ball needs to be on the way out the second JJ is even with that LB, because he clearly has the inside open. Ball needs to be on JJ the second he turns in, which if you watch the timing is the moment JG's 3 step drop completes. Ball should be coming out the second that back leg plants at the end of the drop. Instead there's a little shuffle step, a ball pat and then he over compensates by trying to throw a lazer in there that ends up high and a little behind. It's a little thing, barely a second or so, but those little things make all the difference in the red zone. Here it allows the man who got beat enough time to get back and make the interception. On the season it's why they're 7/14 or so on scoring TDs in the redzone.
I think it really surprised them how bad he’s been because from everything I heard over summer and through camp, the offense was way ahead of the defense. And now we know that might’ve been true but only because we get zero pass rush and our corners have been really bad.Week 1 - JG threw 40 passes and had 10 rushing attempts that were basically pass calls that turned into tucks. So we basically called 50 or so pass plays. The RBs had 21 attempts. (Chandler 6)
That game plan was designed to get JG going under the premise we would win the game handily either way. JG had a poor game and the defense was a cluster. The rest is well documented. No excuse for the plan or lack of attention paid to the opponent.
Week 2 - JG threw 28 passes (essentially half the attempts) which tells me against a better team we were already scheming around him. The second half of the game alone was evidence. Chandler had 26 of our 49 carries. Even with a really bad throw that cost us BYUs only TD in regulation we still win the game without a busted coverage and probably by 10 or so points. UT controlled the game until the turnover.
The game plan for BYU just on offense beats Ga St by 2 tds.
I think the BYU game plan was fine and good enough to win the game. Theres absolutely no excuse for the Ga St plan or the way it was carried out.
I don't think Chaney is trying to beat a square peg through a round hole. I honestly don't think after watching JG through out the spring and summer that he felt like he would respond like this. The BYU game (moreso than Ga St.) was the point where he shifted gears. I think he's tried to help JG and nothing to this point has worked. Thus the reason they are giving guys chances that they really didn't want to.
So Bama shouldn't fire that Saban guy for starting JH over Tua for all that time, based on practice?you're portraying all of this as if there's only 1 way for it to be interpreted.....that's it "bad".
we don't have enough depth across the roster, so there is a point where you have to make a decision....play they guys you have and get as many ready as you can or play the guys you think are the best at the risk of too many reps, exposing them to injury and being gassed late in games.......
there were no real easy calls on this particular topic. i haven't always agreed with how they've shuffled folks around at different positions, but i understand why they did it.....especially on the O line.
y'all keep saying this is the coaches being dumb, but you still don't realize (or acknowledge) what kind of shape this roster is in top to bottom.
there's not a ton of answers, and the few they do have, they can't play them all the time...they have to find others that can contribute....if nothing else just to spell the other guys....
and at the end of the day, you don't have an answer at QB. that's a big deal....and affects the rest of the offense in a big way.
It didn't appear to me that JG threw the ball before he stopped. At some point you just throw it where your guy can get it with the least chance of a defender touching it.I don’t think Jennings was supposed to stop and sit there tho based on design. I think he was intended to follow behind DWA across the formation. If he was supposed to stop there then yes. That would have been it.
Disagree, if he expected him to keep going I wouldnt think the ball would end up on his back shoulder. This is a good illustration of JG's lack of anticipation as much as anything. Ball needs to be on the way out the second JJ is even with that LB, because he clearly has the inside open. Ball needs to be on JJ the second he turns in, which if you watch the timing is the moment JG's 3 step drop completes. Ball should be coming out the second that back leg plants at the end of the drop. Instead there's a little shuffle step, a ball pat and then he over compensates by trying to throw a lazer in there that ends up high and a little behind. It's a little thing, barely a second or so, but those little things make all the difference in the red zone. Here it allows the man who got beat enough time to get back and make the interception. On the season it's why they're 7/14 or so on scoring TDs in the redzone.
LOL, thanks. I got other things to say but I will let @Orange Studs say them for me.On inskip, duh.
Inskip GrillWhere is this? I work near Inskip.