Einstein

It’s also hard to stop him from blocking when the line is a sieve.

I would be shocked if they did this. 11 seconds is about the cut-off for running a play and getting a spike off. And they would have needed to get 10 yards on that play to make things equal. Thankfully, McDermott all but just admitted at the press conference that it was a mistake so I don’t think we see it again.

For all those defending this decision, I hope you enjoy it - because I don’t think you’ll ever see it done again. I think McDermott knows he made a mistake and I don’t think he would ever do it again.

He is on pace for 10 total receptions this year. Thoughts on his usage in Brady’s system of small ball?

Preach! so.. many… people … they just don’t understand this concept. This thread is essentially an IQ test of the members of this forum.

I don’t think you understand how defenses play in this situation. They guard the sidelines. They force you to throw the ball to the middle of the field, where time runs out.

By this logic, any decision that results in a loss, was the right decision. If Josh took the ball and purposefully ran out of the back of the endzone, creating a safety and losing the game, that’s the “right” decision just because the outcome is the same (a loss)? No.

A lot of people are missing this. Passing brings with it so much risk. Bingo.

Actually it does. Getting a first down guarantees overtime, but comes with considerable risk if you don’t get the first down. Running gives you the best chance of getting to OT without the risk of throwing to get a first down. Yes it was. Actually throwing deep was the only thing that gave us a fighting chance. The deeper passes is what took an extra second or two off the clock (which is Gunner’s point). Short passes are essentially a run.

An excellent point that I hadn’t considered yet. From every angle, it was a terrible decision.

I have the actual time stamps (from the frame rate). They were as I said. But you’re going off the game clock - not the timestamps - which makes sense. Regardless, the point is still the same. Our run plays were taking between 4-6 seconds on average. Which is exactly what our passes took on that drive. The extra 2-3 seconds they may have received still would not have been enough time, with no timeouts, to get into field goal range.

First pass play: 4 seconds Third pass play: 4.5 seconds It was just the one pass that took longer than normal. I just went back to our previous drive. Our average rush plays, from snap to whistle, were between 4 and 6 seconds. Even if they have 3 or 4 more seconds, it’s not enough time. They would have to snap the ball, run a play, rush to the line, spike the ball, in 11 seconds. And it would have to be a 10+ yard completion to equalize what they got from what we did. And I have no problem going for a first down. But you HAVE to run twice on first and second down, make them take the timeouts, then on third down you pass, but only if someone is wide open, otherwise tell Josh to uncork it deep. If was absolutely brutal coaching.

Bingo! Even if you’re going to pass, run the first two downs and set up a 3rd and short. Then you can even run a play action and perhaps open up a big play.

Maybe it would have. We honestly don’t know - because angles change the further back you kick. Bur even if it was good from 63, then you tip your hat and say good kick. At least you made it harder on him. You don’t defend stupid coaching just because making it harder on them, may or may not have mattered.

I actually like McD. We can do a lot worse. But let’s call a spade a spade… regardless of his security with the team.

If we assume Cook just gets 1.5 yards per carry. Thats 5 yards. Plus they wouldn’t have had the 5 yards they got on the last second play. So you’re 10 yards back. They need 10 yards, with no timeouts, and not enough time to run a play and spike the ball. There only chance would be to throw a 10+ yard out. And that only works if the coaches are stupid enough to not defend the sidelines. There is no defending this. It was stupid.

Well, duh? You don’t make coaching decisions based on no detail or foresight. You make decisions based on the math and probability of what could happen. Then you’re as wrong as the coaches. It’s that simple. You mean when he got hit as he was throwing it?

Statistics show that you need 8-11 seconds to run a play and spike the ball. They wouldn’t have had the time

So you’re saying the coaches would have left the sideline open? So you agree the coaches are an issue?

In that case, you’re missing the yardage gained on the run plays. If we gain 5 yards on the run plays, and Houston can’t gain 5 yards on the last second play (because they have 0 timeouts), the 59 yard kick is now 69. You think they’re making a 69 yarder? I don’t… I don’t think they’re breaking a NFL record.

Agreed that we are lacking in talent. Mack Hollins losing track of TWO deep passes, one that hit him in the hands, is inexcusable.

What if we made it harder on them? Uh, good? That should be the goal? 1) A kick looking good from 64, when kicking from 59, does not mean it actually would have been good from 64. Why? Because when kicking from 64, the entire angle of the kick changes. Much easier to block too. 2) Running 3 times, removes all timeouts from Houston. Know what that means? It means they can’t run that last second play to gain another 3 cards. So it wouldn’t have been 64, it would have been more like 67. .

You have no problem with losing as long as it was entertaining? Goodness. God bless ya, but fans like you are a different breed. I can’t relate.

I don’t understand the thinking at all. They thought we were going to drive 70 yards in 30 seconds? From our own endzone? Even if we ran 3 times, got 5 yards, and punted… Houston would have been without timeouts, more time would have been off the clock, AND the kick (if there was one), would have been from 63+.

No, this takes the cake Last week was bad, but we were out coached and outmanned. This week, the coaching design to pass 3 times out of your endzone instead of making Houston burn a single timeout is outragoeus