Bayless with great explanation on why QB Sneak call was okay....
According to him 1 QB has ever been hurt doing a QB prior to Mahomes.
<iframe width="560" height="315" src="https://www.youtube.com/embed/FgljPtO-7ZU" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
So that means it's really not OK?
|
Dang Pete when you get stuck on something you really get stuck on something.
|
F*** Bayless... How many of those players were asked to run that play with an ankle injury? He had no business being in that game with a lingering ankle injury that was reaggravated just before the short week. And they knew this, which is why the Bieniemy worked Matt Moore into the game plan before the game.
|
I'd agree with Shannon the pro over Skip the pundit
|
I see valid points made on both sides of this argument. Football is a game of risk, shit happens.
|
I’m with Bayless. A play that is one of the lowest injury risk in football is not foolish to call. Now if Reid has dialed up a bunch of plays that take too long to develop and cause Mahomes to take a bunch of hits, I would criticize that. He didn’t.
|
I guarantee Mahomes was perfectly fine with the call. And that's all that really matters.
|
Quote:
I've read a lot of stupid shit on CP over the last few weeks, and this is probably tops. |
Quote:
|
One of you idiots that didn't like the play call please explain to me how you dislocate your knee cap from having a hurt ankle on the other leg? He has a better chance of hurting himself on a non contact play then he does hurting himself on a ****ing QB sneak. I have never in my life heard a fan base bitch and cry because a QB ran a sneak. All the hits he takes after he throws the ball have a higher chance of hurting him, then running a QB sneak. Some of you are so ****ing stupid it hurts.
|
Quote:
|
Quote:
|
Quote:
|
Quote:
Weakness team we've played thus far. |
All times are GMT -6. The time now is 05:10 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2024, vBulletin Solutions, Inc.