Meanwhile, Renfree throws 3 straight swing passes for 2-3 yards each on the next possession.
Full Version: Devils/Deacs
Zero pass rush, Price gets all day to pass, no wonder they ran all pass plays on that TD drive.
Meanwhile, Renfree throws 3 straight swing passes for 2-3 yards each on the next possession.
Meanwhile, Renfree throws 3 straight swing passes for 2-3 yards each on the next possession.
Can't believe WBTV put this game on. Seriously.
QUOTE(DevilDJ @ Oct 22 2011, 01:27 PM) 
Can't believe WBTV put this game on. Seriously.
It's on tv? Damn. There's no way the cameramen can get favorable angles of the crowd today. Looks like the Blue Zone.
Only Duke. Prior to that quick TD , WF had 1 yard of total offense in the second half. Devils STILL trail by a point. 
19 yd field goals are for losers. Just sayin'
Several big coaching mistakes IMO.
1) Penalty gives Duke a first down on the 3 or 4 with 8 seconds left in the first half. One time out. Cut trots out Snyderwine. There was time for at least one shot at the end zone, maybe two.
2) On Duke's last TD, Cut didn't call for a deuce. The way Duke was playing on D, you have to go up 4 here instead of 3 IMO. Then a FG ties it even if Wake scores a TD.
3) 19-yard FG? Really? Worst case scenario, Wake gets pinned on the Duke 1 or 2. Still don't understand the kick here.
4) The timeout on the second-to-last drive was horrible. Absolutely no need to take it. If Cut has another TO to burn on Wake's last drive, Duke all of a sudden has a hell of a lot more time to work with and get into FG range.
5) The clock management and play-calling were bad on that drive, too. Still can't figure out handing the ball to Scott on first during the last set of downs.
6) Before the final drive, the coaches HAVE to tell the offense to let Wake score on any turnover. When Renfree threw a pick on his final pass, the Wake DB was on his way to a pick six but the Duke coaches were jumping up and down on the sideline yelling at the offense to tackle him. If Wake scores, Duke's down 8 with a second or two left and Wake kicking off. Pretty bleak, sure, but not as bleak as, you know, THE GAME BEING FEKKING OVER.
I like Cut and I think he's done a good job, but my confidence in him is waning a bit vis-a-vis his game management. Outstanding motivator, great recruiter, but he needs to step it up when he's on the sideline.
1) Penalty gives Duke a first down on the 3 or 4 with 8 seconds left in the first half. One time out. Cut trots out Snyderwine. There was time for at least one shot at the end zone, maybe two.
2) On Duke's last TD, Cut didn't call for a deuce. The way Duke was playing on D, you have to go up 4 here instead of 3 IMO. Then a FG ties it even if Wake scores a TD.
3) 19-yard FG? Really? Worst case scenario, Wake gets pinned on the Duke 1 or 2. Still don't understand the kick here.
4) The timeout on the second-to-last drive was horrible. Absolutely no need to take it. If Cut has another TO to burn on Wake's last drive, Duke all of a sudden has a hell of a lot more time to work with and get into FG range.
5) The clock management and play-calling were bad on that drive, too. Still can't figure out handing the ball to Scott on first during the last set of downs.
6) Before the final drive, the coaches HAVE to tell the offense to let Wake score on any turnover. When Renfree threw a pick on his final pass, the Wake DB was on his way to a pick six but the Duke coaches were jumping up and down on the sideline yelling at the offense to tackle him. If Wake scores, Duke's down 8 with a second or two left and Wake kicking off. Pretty bleak, sure, but not as bleak as, you know, THE GAME BEING FEKKING OVER.
I like Cut and I think he's done a good job, but my confidence in him is waning a bit vis-a-vis his game management. Outstanding motivator, great recruiter, but he needs to step it up when he's on the sideline.
QUOTE
Pretty bleak, sure, but not as bleak as, you know, THE GAME BEING FEKKING OVER.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.