Random Commanders Thoughts

We are currently the 32nd ranked defense in the league. That is simply unacceptable.
 
tr1 said:
It'll be interesting to see if Haslett is just as testy as he was last week after the loss.

Maybe he sees some writing on the wall?
Click to expand...

Could be, but is anyone hopeful Raheem could do any better? I mean injuries and rookies aside our secondary has been **** since he came on board.
 
283 of the Packers passing yards came after the catch. That is ridonkulous. James Starks ran for 132 yards. First team in NFL HISTORY to have a 450-yard passer and 125-yard rusher in the same game. First in NFL HISTORY! Aaron Rodgers not only threw for 480 yards, he completed almost 81% of his passes, and averaged almost 11.5 yards per attempt.

Its not really hyperbole to say our defense was completely useless.
 
Lanky, there were more records broken yesterday than after a Milli Vanilli concert.
 
When the Redskins first drafted Griffin and through the regular season in 2012 I thought we had acquired a natural leader and that would be a positive long-term for the organization (in addition to his obvious talent).

Now, seeing him in that playoff game lying to the coach and refusing to come out for a healthy Cousins and basically doing the same thing to start 2013, I am beginning to think he is more selfish than anything else and he would rather see the team lose than win or be more competitive without him until he is really back healthy.

Once again, folks, it seeming more and more as if the Washington Redskins have another 'sacred cow' player much like Clinton Portis was back in the Gibbs days.

The individual is once again bigger than the organization and no one is going to challenge that.

You don't see this in Green Bay or New York. The team always comes first.
 
What I am saying is that he fails to see that he may actually be hurting the team by going out there far below 100% and doing less than Cousins seems capable of.

But at the end of the day, it is the COACH and GM and OWNER that TOGETHER need to decide organizational strategy and communicate that TO a 23 year old player.

The entire organization should not tilt on the individual decisions of a 23 year old that is just starting his second season in the NFL.
 
What sucks is living in Akron and people saying the browns are a better team......

My thoughts are that they will get it together, but it may be after the bye week. I didn't think that Griffin would be this rusty, but it is understandable that he is. It is a long season and we are only in week 2!
 
At some point you hand your car keys to your teenager, and let him take the wheel - its just a fact of life. Sometimes they crash, you just hope they learn from it, and drive safer next time.
 
it's almost axiomatic that a team that goes 4-0 in the preseason ends up stubbing their toe come the opening month of the season.

the last time the Redskins were 4-0 in the preseason, 1985, was the ONE year between 1982-1987 that the team failed to reach the postseason during that first Super Bowl series run.
 
This interview with RG3 is the most pissed I have ever seen him.

I guess I would be pissed too, if I had a dude dry-humping me from behind, and trying to manipluate my body's answers to the interview questions.

 
Last edited:
Lest we forget, KC1 is going to be a little rusty, as well.

You want Sexy Rexy starting?

Nick
 
Well, if we are going to run a drop-back passing attack and that is what Cousins is used to running and suits his skill set, a bit rusty or not, he would appear to be a better bet than trying to morph Griffin into a different kind of player on the fly.

If the goal here is to leave Griffin in the pocket and try and imitate Peyton Manning this team is going nowhere.
 
This is why some of us didn't like the Kirk Cousins pick. Griffin is not perfect and he's bound to struggle and suffer growing pains and you have to let him. I remember when the pick was made saying that the second Bob had a couple bad games people would be calling for Cousins and here we are. We were absolutely blessed and insanely lucky that Bob had such a stellar rookie year but he's still a young guy and he needs to be on the field.

It is crazy that people are calling for Cousins after a couple bad games, but sadly, not entirely unexpected.

Sent from my SGH-T999 using Tapatalk 2
 
We are not calling for Cousins over Griffin. What we are recognizing is that if you draft Griffin to be a dynamic playmaker and then put him behind a plow-horse and expect him to be a 'system' passer than Kirk Cousins, who has better fundamentals and better footwork in the pocket becomes a better choice.

Whether Shanahan/Allen decided to change the offense on their own to protect Griffin or Griffin went to the team and indicated changes needed to be made, the result is that you have taken away the threat that Griffin presents to a defense.

Philly and Green Bay were not afraid of the run game, they were not afraid of Griffin rolling out and making plays downfield as a mobile passer.

Let's not kid ourselves. Griffin has a lot of talent. But he did not operate a typical NFL offense in college for 3-4 years as Andrew Luck did.

Trying to turn Griffin into Andrew Luck is not going to work.
 
You trade two firsts and a second for a QB and he has to be everything you need in a QB for the next fifteen years. And if he's not he needs to learn. You do not put that kid on the bench if he's healthy enough to play. Period.

Sent from my SGH-T999 using Tapatalk 2
 
Henry said:
This is why some of us didn't like the Kirk Cousins pick. Griffin is not perfect and he's bound to struggle and suffer growing pains and you have to let him. I remember when the pick was made saying that the second Bob had a couple bad games people would be calling for Cousins and here we are. We were absolutely blessed and insanely lucky that Bob had such a stellar rookie year but he's still a young guy and he needs to be on the field.

It is crazy that people are calling for Cousins after a couple bad games, but sadly, not entirely unexpected.

Sent from my SGH-T999 using Tapatalk 2
Click to expand...

I don't know if we should put Cousins in or not, but the argument for doing so wouldn't be that Griff is playing poorly, it would be that he's not physically ready and needs more time to recover. That's exactly why you have a backup and its exactly why our front office and coaches were smart as hell to grab Cousins.

It depends on what is really going on with Griffin IMHO.
 
Is he healthy? If so, why is the offense unrecognizable from what he ran last season?

Judging by his erratic performance staying in the pocket and inability to lead a consistent attack in the first half of games when they are still competitive, something has to give at some point.

You don't just write off a 16 game season and a locker room of 53 players because one player is perhaps 70% and the team is too timid to bring him back according to a reasonable schedule.

Bottom line, this team has not been competitive in facing two teams in Philly and Green Bay whose defenses were lit up in their other games this season. San Diego rolled up yardage, points against the Eagles and the 49ers worked the Packers pretty good.

These same defenses face the Redskins and BOTH throw 30 minute shutouts and a 50-7 halftime advantage?
 
Boone, what I'm reading is that becauce Griffin can't run an offense like Luck can he should be pulled for Cousins. Sorry I think that's nonsense.

If Griffin can play but has to learn to adjust his game, you have to let him. He's 23 years old, and despite last year's heroics, he has a lot to learn and has a lot of growing to do. Its not just his health. Hes healthier than he was against Philly and Dallas last year when our offense was still productive as hell. He needs mental reps, and if we weren't going to be patient enough to give him that wr shouldnt have spent so much to draft him.

You put Cousins in when Griffin CANT play. Not when you think letting Griffin play is inconvenient.

Sent from my SGH-T999 using Tapatalk 2
 
You must log in or register to reply here.

Users Who Are Viewing This Thread (Total: 3, Members: 0, Guests: 3)

Who Read This Thread (Total Members: 116) Show all

Help Users

You haven't joined any rooms.

    You haven't joined any rooms.
    Top