Reek Woolen has to go

[douche]

I've always thought that the primary goal should be to simply bat it down. As you say, if the receiver is not looking back, then don't look back. And here's an idea... if he is looking back, look into his eyes and watch his hands. His eyes will tell you if the ball is coming. Raise your hands in front of his and deflect it.

Of course, it's easier said than done. But I think these guys sometimes overthink it. Or are just too focused on making the INT.

[Donn Beach]

You can turn you head without stopping. I have seen it thousands of times. It is kind of impossible to make a pick if you aren't looking back towards the LOS.

its not about stopping, maintaining the speed of a NFL wide receiver with your head turned in the wrong direction is 100% impossible. If you turn your head too soon you are going to lose a step to the receiver and you are screwed, that is all they should need to toast you. Proper technique is to read the receiver, figuring out where the ball is by their behavior rather than turning and looking for it. This of course is something the receiver tries to not happen. It truly is a difficult thing to pull of successfully, and at the same time you are out there alone with the entire world watching if you fuck it up.

Here is an idea, wait until the WR turns his head and then turn your head. If you both are running with your head turned then you both have the same disadvantage right???? Also you have to know at what point the ball either has to be in the air or the QB is either sacked or scrambling on a run right????? Not turning your head is going to result in a PI or completion unless it is a bad throw or a drop. They always say you have to play the ball or the officials will call a PI and they almost ALWAYS do. You can't play the ball if you can't SEE it!

yeah, you read the receiver. The issue with that however is they will try and fake you out because they understand their movements are key to the thing. They will fake a move for the ball that if you fall for it they can get that extra step. In fact this is what happened to Woolen on the 45 yard completion isn't it? I remember RS commenting on it, the move he fell for. But I have seen others comment that he in fact had recovered from the move but somehow screwed the pooch anyway. I do have a lot of sympathy for corners, its not easy

[Donn Beach]

Wasn't he a safety in college? Maybe he can still learn some things, but the window is closing.

WR, reason for some of the comparisons to RS I guess. I really don't know much about the guy. I am sort of poking around, looking for RS's comments on him. Woolen really is highly regarded terms of his qualities. He gets characterized as RS but with more speed

[Donn Beach]

I've always thought that the primary goal should be to simply bat it down. As you say, if the receiver is not looking back, then don't look back. And here's an idea... if he is looking back, look into his eyes and watch his hands. His eyes will tell you if the ball is coming. Raise your hands in front of his and deflect it.

Of course, it's easier said than done. But I think these guys sometimes overthink it. Or are just too focused on making the INT.

Yeah, except the receiver understands you are trying to do that, I think that's one of the thing about being a great receiver, you aren't allowing the corner to read your eyes

actually AI claims its a mistake to try and read the eyes...

A cornerback's goal is to avoid reading a receiver's eyes and instead focus on their waist or hips to anticipate the route, then turn to locate the ball once it's released to either intercept it or break up the pass. This technique requires disciplined eyes and body language reading to stay in phase with the receiver and make a play on the ball.
Why reading eyes is a mistake
Disguised intentions:
Receivers are trained to disguise their routes, and their eyes can be a misleading indicator of where they plan to go.
Losing the receiver:
Focusing on the receiver's eyes makes it difficult for the cornerback to track the receiver's movement and can lead to losing them in coverage, especially when the receiver is about to make a sharp cut.

[57reasons]

its not about stopping, maintaining the speed of a NFL wide receiver with your head turned in the wrong direction is 100% impossible. If you turn your head too soon you are going to lose a step to the receiver and you are screwed, that is all they should need to toast you. Proper technique is to read the receiver, figuring out where the ball is by their behavior rather than turning and looking for it. This of course is something the receiver tries to not happen. It truly is a difficult thing to pull of successfully, and at the same time you are out there alone with the entire world watching if you fuck it up.

Here is an idea, wait until the WR turns his head and then turn your head. If you both are running with your head turned then you both have the same disadvantage right???? Also you have to know at what point the ball either has to be in the air or the QB is either sacked or scrambling on a run right????? Not turning your head is going to result in a PI or completion unless it is a bad throw or a drop. They always say you have to play the ball or the officials will call a PI and they almost ALWAYS do. You can't play the ball if you can't SEE it!

yeah, you read the receiver. The issue with that however is they will try and fake you out because they understand their movements are key to the thing. They will fake a move for the ball that if you fall for it they can get that extra step. In fact this is what happened to Woolen on the 45 yard completion isn't it? I remember RS commenting on it, the move he fell for. But I have seen others comment that he in fact had recovered from the move but somehow screwed the pooch anyway. I do have a lot of sympathy for corners, its not easy

Good point Donn. the other factor is that of course WRs have figured this out too, and it's widely accepted practice for them to use "late hands", waiting until the last possible moment to extend them for the catch so as not to tip off the DB. Lockett in particular was very good at that, as was Jermaine Kearse (come to think of it that was really the best skill he had).

[Donn Beach]

Riq Woolen was great today, one week after drawing the ire of many in the Emerald City. He had an early penalty, but that’s the only time I heard his name called which means he was doing his job. Woolen was also the one who hustled all the way down the field and tackled Warren on that long pass play - which turned out to be huge since Derion Kendrick picked off Rodgers in the end zone to stymie a scoring opportunity.

[douche]

I've always thought that the primary goal should be to simply bat it down. As you say, if the receiver is not looking back, then don't look back. And here's an idea... if he is looking back, look into his eyes and watch his hands. His eyes will tell you if the ball is coming. Raise your hands in front of his and deflect it.

Of course, it's easier said than done. But I think these guys sometimes overthink it. Or are just too focused on making the INT.

Yeah, except the receiver understands you are trying to do that, I think that's one of the thing about being a great receiver, you aren't allowing the corner to read your eyes

actually AI claims its a mistake to try and read the eyes...

A cornerback's goal is to avoid reading a receiver's eyes and instead focus on their waist or hips to anticipate the route, then turn to locate the ball once it's released to either intercept it or break up the pass. This technique requires disciplined eyes and body language reading to stay in phase with the receiver and make a play on the ball.
Why reading eyes is a mistake
Disguised intentions:
Receivers are trained to disguise their routes, and their eyes can be a misleading indicator of where they plan to go.
Losing the receiver:
Focusing on the receiver's eyes makes it difficult for the cornerback to track the receiver's movement and can lead to losing them in coverage, especially when the receiver is about to make a sharp cut.

It's the splitting of hairs at the NFL level. And what you mentioned is testament to the skill level and cerebral aspect of the game. The guys who are really good receivers are not only extremely athletic but also intelligent. Same goes for the really good corners. All things equal, it literally becomes a battle of the minds.

[douche]

Riq Woolen was great today, one week after drawing the ire of many in the Emerald City. He had an early penalty, but that’s the only time I heard his name called which means he was doing his job. Woolen was also the one who hustled all the way down the field and tackled Warren on that long pass play - which turned out to be huge since Derion Kendrick picked off Rodgers in the end zone to stymie a scoring opportunity.

You post a lot of quotes but rarely a source. Who said this?

[Donn Beach]

Riq Woolen was great today, one week after drawing the ire of many in the Emerald City. He had an early penalty, but that’s the only time I heard his name called which means he was doing his job. Woolen was also the one who hustled all the way down the field and tackled Warren on that long pass play - which turned out to be huge since Derion Kendrick picked off Rodgers in the end zone to stymie a scoring opportunity.

You post a lot of quotes but rarely a source. Who said this?

Sorry, that's a field gulls article, winners and losers, had him a winner.

[Donn Beach]

Terms of quotes, here's MM on the topic...I want to pump you up! lol

“What people don’t realize is we missed a ton of tackles, … but Riq is the guy that chased [Warren] down from the backside,” Macdonald said. “Talk about ultimate effort, committed to the process, having your teammates’ back, playing with shocking effort, he does that, and he got him down and we ended up leaving that drive with no points.”

“Riq was the guy that deserves a ton of credit on that front and helped us win the football game,” Macdonald said. “I’m really proud of Riq. He’s done a great job this week.”