Krieg's list
New member
- Joined
- Oct 21, 2014
- Messages
- 50
- Reaction score
- 0
Tyakack":3r18vfe2 said:It was the worst call ever because of the result. If he gets a TD there nobody says anything, obviously. Its easy to call a call terrible when it doesn't workout. I will admit that I think running it was the best option however I don't think the play call was as terrible as people are making it seem. The execution is what was terrible.
Please stop accusing everyone (but yourself, apparently) of results-based decision making. It is patronizing and quite simply wrong, if you've ever read these boards before.
The point everyone is trying to make and you don't seem to get is that you have to take your driver out of the bag in that situation. He already hit his driver (unnecessarily) on the lucky Kearse reception 2 plays before (which easily could have been an INT in its own right) and got away with it. Then on 2nd down he foolishly chose a play in which poor execution could lead to disaster rather than selecting a safer play that would still almost certainly (eventually) get them home.
Even if the execution were better and Lockette made the catch, there would still have been a ton of WTFs and eyebrows raised, but who is going to bother to complain vociferously while they're celebrating a SB victory? This, in fact, is the reason Bevell is still defended by some-- although hopefully fewer now-- here at .NET. Because nobody wants to hear whining about playcalling after a win. There's plenty of whining here anyway, haha, but it's always shot down with flawed "he won us the SB" "we have the #1 rush offense" type of arguments. The problem is people only entertain the complaints after losses, of which there have not been many during Bevell's tenure.
Don't assume that people haven't been complaining about suboptimal playcalling all season and longer just because you weren't paying attention.