"DC" Skins Postgame #11 - Titanic Effort Returns Hope

Yes... another late blog. I do realize this should have been posted about two days ago, but who's keeping track?

Anyway, after being left for dead after the massacre against the Eagles last Monday night on national television, the Redskins have gotten some hope back with this 19-16 overtime win against the Titans. This was a game that the Redskins had to win, and going into the game, it didn't look good because the Titans won all the games against the NFC East, and they were very banged up with a lot of key injuries. Not to mention, the Titans are just plainly a lot more talented than them.

As the game was played, it didn't look to good for the Skins initially as well. They allowed the ball deep into their own territory for the first Titans possession, then allowed a touchdown punt return during the next. But fortunately for them, they were only down 7-0. They responded a possession later and tied it at 7, but they could have easily been down by a lot.

Then, the injuries started coming. Special teams players started to go down, then some offensive linemen, then Clinton Portis (again), then more offensive linemen. They were banged up already to start off the game, and they started to lose even more players? It looked bad. Very bad. The coaches were moving people around the line, putting tackles as guards, players who played normally played on the left on the right side, and so on. That offensive line was a patchwork job, and it didn't look like it was going to hold up, especially against a defense that sacked the quarterback the most in the NFL.

But the Redskins offensive line really surprised me. Despite this line being banged up and abnormal, it still probably put up the best effort it has all season. McNabb was only sacked three times, and in most cases, they gave him time to throw the ball. The mistakes that McNabb made and the interceptions he threw were more on him than on his offensive line. There was even one interception he threw where he had forever to throw the ball. Along with the fact that Vince Young was replaced by a rookie quarterback in the 4th quarter, this gritty play of this offensive line, as well as key stops on defense kept the Redskins in it in the end, and the game came down to a Redskins field goal in the end of regulation, which wasn't made. Therefore, it went to overtime.

Overtime was more of the same. The Titans moved the ball a little bit, and depended on Chris Johnson to do so, but apparently the Redskins play made it clear that they would make Rusty Smith (Vince Young's replacement) try to beat them. And of course, he wasn't able to. And after they punted, and when the Titans gave the ball back to the Redskins, offense did it's thing and allowed McNabb to make a few plays. But at the same time, Titans also committed a lot of stupid penalties in this period, including a few unnecessary roughness and holding penalties. So, in the end, the Redskins moved the ball far enough so they had a chance at a field goal. Ironically, that field goal was a yard longer than the field goal that was missed to end regulation. However, Gano (the Redskins kicker) was able to boot it in for the win.

As I said, this is a good win for the Redskins, and it restored some hope in this town and showed that the season is not lost (yet). They beat a team that they weren't supposed to beat and are clearly more talented than them on paper with a very bad offensive line, after a demoralizing loss a week before. Therefore, people in DC have started to rejoice for the week, because the smiles are more apparent after the win. Not to mention, the "P" word could be back in the conversation if there happens to be a couple more key wins. And that starts next week, with a very winnable game against the Vikings (who has a geriatric quarterback with some off-the-field camera phone "issues" and also just fired their head coach).

But, with this win, people here in the DMV should feel good, for now. If they play with that same heart, as they get healthy, they will definitely get back into the postseason conversation. But, it's still very hard to say whether this win determines if this team will be playoff bound. It may be doubtful that the line will perform the way it did that day, and how well (or if) everyone heels up as the season goes on. 

For now, just take it for what it's worth... a win against a more talented Titans team. Whether it gives momentum throughout the upcoming games, we'll just have to wait and see. It does restore hope though. I always believed that hope is the rope of the faithful and loyal. And from living here all of these years, the fans of this team are one of the most faithful in the country. 

That being said, Redskins fans can have something to hang on to for now. Let's just see how long it hangs out there.

HTTR,

-OBE

"DC" Skins Postgame #10 - Shocked and Embarassed

I'm not going to say too much about this game. Simply put, it was tough to watch if you're a Redskins fan. The team got embarrassed, humiliated, degraded, or any other negative verb you can throw out there that summarizes pure disappointment.

I am not going to blog about it, not only because it may be a little tough to do so as a fan, but also, the local, as well as the national reaction to the overall Redskins performance (as well as the overall Eagles performance) is practically mutual... the game was not even close. (And that's an understatement).

Instead of talking about it, I'll post a rant from one of the more respected sports radio shows out here in this area, because of the unbiased commentary. This was from Chad Dukes and Lavar Arrington from 106.7-FM "The Fan". Chad Dukes was mad, and really exhibited the passion, and frustration the fans from this area have been going through in years, and just shows how loyal the fans are in this town.

If anybody from the organization heard this rant, I hope they took some notes. People are really disappointed in major failure and expect the best from what they pour their heart out to, as it is in real life.

With that being said, for this team as it relates to this season... this is "Rock Bottom". And when you're at your very worse, you can only get better, which is the way I see it. Although I am probably as disappointed as Chad Dukes with this performance, I always try to find the positive that may come out of a bad situation.

We'll see how they play against another solid team in the Tennessee Titans next week, to see if that pain can actually serve as a motivator to turn the season around. But with this performance, even though I am cautiously optimistic, I still remain more skeptical that this team can turn it around for this season.

So until then, we'll see how it goes. But I will say right now, since I put a lot of faith in my team in that last prediction and lost a lot of it, it may be hard to pick them for the rest of the season.

I will say, that I was right about one thing though. I was right in titling the pregame entry "Redemption". That game yesterday was indeed "Redemption", but it was just more appropriate for the other team.

That's all I gotta say about that.

-OBE

"DC" Skins Postgame #8 - Haunting Loss

Being that yesterday was Halloween, it is fitting that this loss against the Lions is haunting for the Redskins. As I said, they had all the momentum and the opportunity to go into their bye-week at 5-3, with a winning record, on the thick of things on the race for the division, or maybe in the conference. Yet, they blew a game they had a great chance to win down the stretch... and now more uncertain about the future than any point in the season. And I didn't even mention the "Bench-gate" scandal that took place in the end of the game.

As expected, the Lions were a tougher out than their 1-5 record indicated. Matthew Stafford is a decent young quarterback, he came back from an injury, they have a talented defensive line, and they were well rested, playing at home, coming straight out of their bye week. 

Stafford looked rusty to start off the game, but luckily for them, the Redskins offense couldn't capitalize with their opportunities. It was a defensive battle to start off, with the Lions defense getting pressure on McNabb, and the Redskins making a few plays. If I can recall, the first points weren't scored until the 2nd quarter.

But, as when the scores started to come, it was a see-saw battle. When the Lions scored, the Skins countered with another score. The Redskins were able to get two quick field goals in the end of the half to lead by 6 at break.

Come the 3rd and 4th quarter, the battle continued. It was a pretty good battle. Score after conter-score, with nice drives, as well as defensive and special teams plays. It continued up until down the stretch, up until the end of the game. When McNabb got intercepted, and the Lions scored that field goal, even though they were down by 6, the chances weren't that good.

But, what really sealed it was when McNabb got benched for Rex Grossman with under 2-minutes to play still only down for 6-points. And in the first play, "Sexy Rexy" got sacked, fumbled the ball, and gave up the go-ahead score to seal it.

Before I give my opinions on that particular "bench-gate" incident, I want to talk about what I generally saw in the game. The Lions defensive line dominated the front line, as they totally destroyed that shaky Redskins offensive line. And honestly, the way it looked, it could have been A LOT worse. With the pressure they got on McNabb, it's a surprise he didn't get hit more, or leave the game injured. Not to mention, the Skins couldn't get the run going, and most of their plays that they made in offense were on the air. And, a lot of the scores they got were from good special teams or defensive plays getting them good field position.

So now... the issue with Shanahan benching McNabb. Like many people who saw it... I'm not buying his reasons. Yesterday, he said he benched them because McNabb didn't know the two-minute terminology as well as Grossman did, since he's been in the system a lot longer. After the press conference today, he said that he wasn't well-conditioned and that his "cardio" wasn't good enough.

As much as I don't like to say it, that last statement is kind of making Albert Hayneswoth look more credible with his issues with Shanahan earlier in the year, and makes him look like he uses "conditioning" as a trump card to give him an excuse not to play people. And, the fact that Haynesworth actually had another solid game yesterday, shows that he isn't as bad as Shanahan made him out to be earlier in the year.

Regardless, no matter what shape you think your player is in... if he's clearly the best player you got, you put him in down the stretch. And clearly, McNabb is better than Rex Grossman. He's more mobile, can allude the rush, and has been and thrived more in pressure situations than "Sexy Rexy". Even if he knew the terminology more, the fact that you put an immobile quarterback against a shaky offensive line that has been killed all-day long by that Lions frontline was a very questionable move.

As far as the reason that it was said that McNabb wouldn't have been capable of running the two minute offense because of his "cardio" or his capability... I don't buy that at all. He says that the Skins have never been in a two minute situation all year. Apparently, Shanny couldn't turn the clock back a couple of hours, because McNabb got some much needed 3-points in a two-minute situation before halftime. Sure, it was only a field goal, and it was earlier in the game when he is supposedly not as "tired", but still... he showed he's capable of doing what he needed to do, when he needed to do it.

Looking forward to the rest of the season, this loss, and the "bench-gate" situation can lead to two different results, both on the opposite sides of the spectrum...

• One is (which is the one that most people I have heard in the airwaves are predicting), that this is a crippling loss, which will take the Redskins out of contention, and they will fall apart as the year goes on (adding all that to the fact that the McNabb negotiations have all been killed and this organization has to go back to square one, and be uncertain about the future again). 
• OR... this loss can fire up this team, like how the loss to the Rams ealier in the year fired them up to win against teams that they are supposed to lose to. And just like that Rams loss, who do they play in their next game? Donovan McNabb's Eagles. Rewind back into last year, when Andy Reid benched McNabb in favor or Kevin Kolb. When McNabb got his spot back, he played his best football of the year and almost closed the year with a division championship (until the Eagles pooped it out against the Cowboys in the last week of the season, then in the opening round of the playoffs).

As someone who is normally an optimist, I'm inclined to think that the latter option is more than probable for the Skins. And realistically, I do think they can come back from this loss and do better. I hate sounding like an apologist... considering that they haven't really done anything mind-blowing so far in the first half of the season, but from looking at the schedule, it looks like they might've gotten the tougher games out of the way. IMO, the toughest games they have left are against the Giants twice, and the Titans. If they can steal a couple of those games, and beat the teams that they're supposed to beat (and yes, I predict the Buccaneers to slowly as the year goes on), they can get back in the conversation.

But, as we all know, the NFL is a week-by-week, "what have you done for me lately?" league. You're only as good as your last performance... and if the Redskins happen to bounce back after this loss and convincingly win against the Eagles, people will start talking about them again.

It's a shame though that they will not get that chance in another 2 weeks. Their next game won't be until Monday the 15th, so they have A LOT of time to think about this win... and the local media has a lot of time to stew on this loss and fill the airwaves with a lot of chatter. That's why I said that it was important that they get this win... not only for their psychological outset in these two weeks, but also, because of what I previously said, that this area is so linked to this football team, that when the team loses, the mood in this area is terrible. Therefore, most people will feel terrible during the first half of November. (I say "most", because this statement won't apply to me.)

As I last year, the President isn't dead... so all is not lost in DC in these next two weeks. But, if this city's football team can bounce back from their latest setback (which I can see that they are more than capable of)... then all will be much better again.

D4P...PD!!!

-OBE

"DC" Skins Postgame #7 - Game Turnover

As I noted while watching this game on Twitter, this Redskins game against the Bears has probably got to be one of the ugliest games I've ever seen. It was so ugly, that it was pretty comedic... and I had a lot of moments where I was laughing out loud.

As both teams' records indicate, this was a close game. However, I thought that more points were actually going to be scored. Cutler clearly has the capability to throw the ball and run up the score if given the protection, and I thought Donovan McNabb would put in a better performance than he had put, since he was playing in his hometown. Instead of an offensive performance on both sides of the ball, what we got is a low-scoring, and sloppy, defensive, turnover-laden game.

During the 1st half, the Redskins were dominating the field position battle, and usually got the ball on or around mid-field to start off possessions. However, they couldn't finish off drives, by either having 3-and-outs, or by turning over the ball when they were in enemy territory. The Bears D kept it close for the 1st half, and one interception by them put them over on the scoreboard come halftime (despite being dominated statistically by the Redskins).

In the 2nd half, the Bears seemed to have all the momentum, and they were moving the ball up and down the field. However, it was their turn to be sloppy. The Redskins defense (most notbably, Albert Haynesworth), caused a key goal line fumble that prevented the Bears from going up 21-10. But despite the opportunity, the Redskins offense didn't really capitalize and didn't move the ball deep enough out of their own territory to give the Bears bad field possession after a punt.

The Bears still continued to move up and down the field, however the Redskins defense kept showing up. DeAngelo Hall (the Redskins quarterback), kept on picking off Jay Cutler, and he ended up with 4 interceptions to end the day (which ties an NFL single-game record). One of those interceptions was taken all the way back for a touchdown, and gave the Redskins the lead. 

But even though the Redskins defense kept giving the offense opportunities, they failed to capitalize. As either McNabb immediately gave the ball right back by throwing an interception, or they would be relegated to a 3-and-out. Had the offense played a lot better during the game, they would not only had a chance to close the game down the stretch, but this game would not have been close (considering how much advantage the Redskins had in field position).

Overall, both teams' defenses keep their team in the game. They kept it close, and each had more than their share of turnovers. So this game could be classified as "ugly", because of all the turnovers, and all the mistakes. But a lot of people like low-scoring, "ugly" defensive battles in football, so if you're into that, this was the game for you.

I also thought that because of the Bears' offensive line woes, that the Redskins will sack Jay Cutler a lot more. If you checked my twitter, I was actually tweeting each time Jay Cutler got sacked, because I thought he would have gotten sacked a lot throughout the game. In the first 20 minutes of the game, it looked like my prediction was gonna be correct, because Cutler got sacked 3 times. But as the game went on, he was only sacked one more time. I probably should have tweeted the number of turnovers that took place in the game (9 total... 6 on Bears, 3 on Redskins). Or, if I tweeted every time DeAngelo Hall had an interception, I would have matched the Cutler sacked number.

I did say in the pregame blog post, that the winner of this game would look more like an NFC contender. I'll have to retract on that statement, because the Redskins have not really separated themselves from the "midcard" of the NFC. Seems like the defense may start adjusting to the scheme, but when the offense is not firing, and the running game is stalling (as it has been all year), then their chances of winning will go down significantly. Not to mention, the Redskins have yet to have a "statement game", in which there was no question that they were truly the better team on the field.

But, I will say that this was a good win. It was an important win that they had to get, because it's a win inside the NFC, and could play in down the stretch when it comes to tie-breakers. It was also a win against a team that played well so far in the season, and had a decent record with some wins against quality opponents. 

However, as good this win is, next week's game against the Detroit Lions actually worries me A LOT. Detroit has been a laughing stock of a franchise during a good part of the decade, but it seems they are slowly starting to turn things around. They are currently 1-5, but they're record is not indicative of how good this team could be, or actually is. They were pretty much in every game they were in (4 out of their 5 losses were by one possession), and they destroyed the Rams, which were a team that manhandled the Redskins earlier this season. Their rookie Ndamukong Suh seems to also be paying dividends for that defense. To add on, the Redskins seem to play down to their competition. If the Redskins looks at this team's record, and happens to take them lightly, especially if they are picked to be favorites (which they may be, because of their superior record), they are going to get embarrassed. But to make matters worse, the Lions will be coming off of their bye-week, which means they will be well-rested and probably be healthier than they have been all year. They might have their starting QB back, Matthew Stafford, and he picked the Redskins apart last year as a rookie to end the Lions' infamous 17-game losing streak.

I'll talk more about the Lions' next week. For now, Redskins nation can enjoy this win, as this was a hard fought win. They have to continue to work hard, and keep the momentum going. This area is so tied with this team, that if the Redskins continue to win (no matter what the circumstance), this area remains happy. 

Got to keep the happiness going.

HTTR,

-OBE

"DC" Skins Postgame #6 - Can't Stop the Colt Train

I would have done this blog shortly after the game, but I was sleepy and went straight to bed shortly after. But, this blog is just in time for lunchtime, and you could choose to read it since a popular topic around the DMV during break time would usually be how the Redskins played the day before. It could definitely add some new insight on your discussions.

If I could simply put it, if there was a game that would be considered a "good loss", in my opinion, this game would be it. For most of the game, Peyton Manning was what he usually is... a smart, calculating, quarterback with a high football IQ that can pick apart defenses at will. However, the Redskins defense exceeded my expectations in this game, forced key turnovers, had key stops, and kept it close. They did what they can do to keep Peyton Manning off the field and give the offense as many opportunities as they can, which included sacking Peyton Manning deep in Colts territory to cause a fumble which eventually led to a score. As I previously predicted, I thought the Colts offense would put up 30+, but they held them under 30, which was a win in itself.

However, contrary to what I just said, a lot of people would blame the defense for this loss, most especially, the secondary for allowing a few big plays (including one touchdown), and not catching interceptions. It would have been great to have those interceptions (and the result would have probably been different if that was the case), but defensive backs are not paid to catch balls. They are paid to mess up plays, and make sure the opposing offense doesn't go forward. Picks and turnovers are usually considered "icing on the cake", and it's the offense's job to score points. But, they have had 3 turnovers, so there's not much more you could really ask from them. Not to sound like an apologist, but although many people would blame the Redskins defense for losing the game, it's not simply the case.

In my opinion, the offense was more to blame for the loss. Don't get me wrong, they've had a solid game also. As expected, the running game seemed to have woken up playing a historically bad Colts run defense. Not to mention, Donovan McNabb led the offense to two long touchdown drives. But, it was down the stretch and when it mattered when the offense did not produce. When the Colts got greedy and decided to pass under the two minute warning to seal the game, the Redskins defense stopped them and held them to a 3-and-out. The Redskins offense got the ball back with the opportunity to tie or win the ball game. However, the Redskins didn't respond and was held to a 3-and-out of their own, which all but sealed the game for the Colts. (Sure, they had their remaining two timeouts left, and had a chance to hopefully get a last second touchdown with one big play, but more often than not, the odds weren't on their side, as the game ended with an interception.)

However, in my opinion, Redskins fans still can't feel bad about this loss. The Redskins played an all-around complete and balanced game. Unfortunately, they just played it against a pretty good team, and a very smart and a future hall-of-fame quarterback, so it just wasn't enough. Nobody likes a loss though, so there's definitely understanding that there will be some disappointment during the next few days here in the DMV. However, I will say that if they keep this kind of effort up in the next two weeks on the road (and not play down) against a improved and solid Chicago Bears team, and a much improved Detroit Lions team whose record isn't indicative of their performance, then they have a solid shot of taking a 5-3 record into their bye week, in time for a big Monday night divisional matchup against the Philadelphia Eagles (who destroyed a good Falcons team this week, and in my estimation, may already have Michael Vick back).

However, they just need to take it one game at a time. They have Chicago up next. And if they can build on the positives from this game, the Redskins can continue building that momentum and can possibly become one of the more solid teams in a wide open NFC.

But aside from this game, there were a lot of great games that were shown in my viewing area this week. The Baltimore Ravens lost a close one to the New England Patriots in overtime. Both teams played well and I thought it was going to end in a tie. But as good as Joe Flacco has played in this game and as much as he has grown in the past few years, we've seen why Tom Brady has earned the reputation he has now. As for the afternoon game, the Vikings pulled off a close victory against the Dallas Cowboys. This was a good game, and you can tell that both teams really wanted to win this game. I'm not a fan of either team, but as a fan of football, I enjoyed watching it. But as a Redskins fan, I had to be especially happy of the result, since the Dallas Cowboys stay in last place of the NFC East. But, it's already close to mid-season, and the quality of football should pick up (if it hasn't already). 

So until an entertaining NFL Week 7...

HTTR,

-OBE

"DC" Skins Postgame #5 - Pack It Up

This is definitely one of those games where I don't mind being wrong. Most of what I wrote in the last blog turned out to be untrue, from how the game was going to be played, down to the prediction. As far as these prediction blogs, I will always take a Redskins win over being right.

Got to give it up to the Redskins during this game. They played the game short-handed, with Portis being out with injuries, and with Haynesworth gone from grieving the loss of his brother, and it definitely showed. Portis' absence definitely showed, because that Redskins running game looked like as bad (if not worse) than it has all season. Not only that... but one lesser appreciated fact about Portis, is that he is one of the best pass-blocking tailbacks in the game. He is usually effective blocking linebackers. Up until he got injured late in the game, Green Bay linebacker Clay Matthews abused the offensive linemen all day long. As far as Haynesworth, he could have definitely helped against the Packers running game. For example, Green Bay RB Brandon Jackson had a 70+ yard gain in the first quarter, which eventually set up a touchdown. In my opinion, there was no way he would have gotten that with Haynesworth plugging up that D-line. The Packers running game has been bad all year, but the Redskins actually made it look good for 3 quarters.

The Redskins gutted out that win. They came back down 10 in the 4th quarter, and ended up tying the game to force it to overtime. McNabb made some plays through the air (because there was no running game), and wide receiver Anthony Armstrong had a few big catches down the stretch, including a 50+ yard touchdown catch. But more importantly, the defense made a lot of key stops down the stretch when they had to, pressuring Aaron Rodgers, and hit him when it counted. They also got off the field quick, and gave the Redskins offense some opportunities towards the end.

But, with all that being said, there are still major concerns about this Redskins team. They still played pretty bad for 3 quarters. I found this game very hard to watch for most of the game. Aaron Rodgers had his way most of the game, and he was leading that team up and down the field. And like I said a few paragraphs ago, the defense (most especially Clay Matthews) was having their way with the offense for most of the game, and McNabb had his share of hits. Their running game is still pretty bad. Until they find a solid running game, it will be hard to discuss them as a serious contender.

This Redskins team was also fortunate a lot of times. In my opinion, if Green Bay tight end Jermicheal Finley wasn't hurt in that first series, Aaron Rodgers would have had another huge option, and the score might not have been as close. Not to mention, Clay Matthews, who proved to be a Redskins killer all game, was out most of the final quarter, because he got hurt. If he was playing in the end, the offense might not have made the plays they'd have made. And Green Bay was also a "doinked" field goal away from winning the game in the last few seconds of regulation.

However, you can't take anything away from the Redskins defense. They really kept the Skins in the game all day. They held a really solid offensive Packer team to 13 points. Despite the Packers marching up and down the field, they held them to one touchdown, and usually had them kicking field goals. The Packers pretty much won all statistical battles (except final score), and the defense had a lot to do with that. They even had a crucial 4th and Goal-line stand in the game that prevented a touchdown early in the game, which ultimately made a difference in the final score. This defense came up tremendous in overtime, stalling the first drive with a huge sack on Rodgers, and with Redskins safety coming up with a huge interception in Packer territory, that all but sealed the game.

So what next? What does this mean in the next game? Like I said, they really need to find an effective running game. Not having a great running game would be a huge concern in their next game, against a team like the Colts. Everyone who knows football, that the best way to beat the Colts is to keep Peyton Manning and his offense off the field. The best way to do that, is to have a ball-control ground game, which the Redskins clearly don't have right now! As far as the Redskins defense is concerned, although they have been solid in the last two games, they have been bad in the two games previous, allowing 30 points in each of the two losses. Most of the time, a Peyton Manning-led Colts offense can put up 30 points against anyone. However, I would say that one glaring factor about the Colts that could really give the Redskins a chance is that their defense hasn't been great. That defense lost them two crucial division games, and if the Redskins can take advantage of that, by having putting up points early, and have a great running game that will control the clock, then they have a great chance of winning. Not to mention, over the years, the Colts defense was always known for being relatively weak against the run. So, again, it is CRUCIAL that the Redskins find their running game against the Colts.

But, no matter how ugly it was, this was a GREAT win for the Redskins. It keeps them on top of the NFC East, and for now, one of the top teams in the conference. And like I said, it is against a solid team who was one of the favorites to go to the Superbowl early in the season. So to all Redskins fans, definitely enjoy this win. Hopefully, they can continue to build on it, as there are still some tough games in the next few weeks.

HTTR,

-OBE

"DC" Skins Postgame #4 - Mac 5 Race for Redemption

Well, I won't keep this entry long, as you will probably read enough about this game in the blogosphere. But, as far as how much television drama this game produced before, during, and after the game, I would say that it didn't disappoint. This game definitely made for good must-see television.

Pregame started by the crowd cheering McNabb, then quickly jeering him after leading the Redskins to a quick 14-0 lead. Then, Michael Vick, who was arguably the hottest QB in the NFL, gets hurt. Thus, putting Kevin Kolb (the Eagles' original hand picked successor to McNabb) against his former mentor. What a turn of events.

The game ended up being close. The Eagles scored a couple of field goals and a TD (with an unsuccessful 2-pt conversion), and the Redskins added another field goal to make it a 5 point game. And, that's what the final score ended up being... Redskins 17, Eagles 12. 

As far as what I saw in the game, although I'm happy McNabb got his redemption and that the Redskins are momentarily the NFC East division leaders, I felt the Redskins played their usual ugly game. As soon as Vick went out, and Kolb came in, it seemed like the Redskins let up a lot (and in my opinion, played down from not being worried about Michael Vick anymore). And even though this was his homecoming, McNabb did NOT have a good game (~60 passer rating is not going to cut it). They kept dropping interceptions, and the offense really slowed down during the 2nd half... again.

In my opinion, even though Kevin Kolb wasn't overly impressive filling in for Vick (and may not get his starting job back if Vick is good to go next week), I felt he still had a more efficient game than McNabb, and he outplayed him during the minutes when they were directly competing against each other. Kolb moved the ball, he was efficient, and even had a higher quarterback rating. If the Eagles weren't stupid with a lot of their penalties, the Eagles could have won this game. They left a lot of points on the board, and the Eagles could have just as easily won as they lost.

As a Redskins fan, the bright side for my team and it's fans is, that the running game looked significantly better during this game. And overall, as this team adjusts to the schemes, this Redskins team could just get better during the season. Not to mention, this is definitely a win that they can build on emotionally, and carry that emotion into the next few games, which will undoubtedly be very tough (as they play the Packers and the Colts in the next two weeks).

So I'm definitely happy with the result of this game, both as a Redskins fan, and as a general football fan. But, I do feel that they could still play a lot better, and they still have a long long way to go to be considered a serious contender. The next few weeks against the Packers, Colts, and Bears will definitely be a good measuring stick as far as where this team stands.

I will say that I'm equally as glad that many people in the area will be happy this week, and that the Eagle fans I know can't talk smack to me this week. :-)

Til next week...

HTTR

-OBE

My Quick Thoughts on the DC Mayoral Race

Primary Election Day in both Maryland and Washington, DC took place yesterday. When I woke up this morning, I woke up to the news that Adrian Fenty, the incumbent mayor of DC, has lost his re-election campaign to Vincent Gray, who will be inaugurated the new mayor in January (that is because whoever won the Democratic primary would win the the ticket due to the Republican party not having a candidate). In some aspects, I kind of surprised, but on the other hand, I knew it the change was imminent.

I won't talk about this subject too much, because I wasn't a registered voter in DC, nor am I a political insider who knows the true situation. I also usually prefer not to talk about politics (due to it being a very taboo and sensitive subject matter to most). But from just hearing from others who have more educated opinions on this, and just from mere observation of seeing where DC is now compared to 4 years ago, Fenty has upheld his office and done well in his job. He has reformed education, re-built schools, and rebuilt and redeveloped several parts of DC. The guy really provided results. All doing so as the youngest elected mayor in the city's history.


So what went wrong? Many say he was cocky, controversial, and downright arrogant. He refused to answer questions about "secret trips", he appeared cocky in his media appearances, and he refused to admit any "mistakes" he may have made, despite what his advisers told him. He thought the results he provided were to enough to get him re-elected. Unfortunately, for him, they weren't. But like I said, I am not in the position to provide full political commentary. So instead please check out this following article by the Washington Post, which is probably a much better read detailing the situation. (It's actually pretty good journalism as well).


Do I think that the DC voters made a mistake in not re-electing Fenty? Perhaps. Like I said, the man provided results and had DC in the right direction, in my opinion. But, at the same time, I do understand why he was not re-elected. To be an effective leader, you have to be genuine and likable. And during these past 4 years, the DC voters didn't feel he related to them enough for them to believe he can effectively lead this city in another 4 years.


But time will tell if Vincent Gray will be a great mayor. I'm hoping and praying he will continue the road that Fenty started to blaze in leading DC in the right direction, and at the same time, not lose touch with the people who put him in office. Good luck to him.

We all have a lot to learn from the results of this particular election. If you're in a position of leadership (or in any position representing others), it is true that results are optimal but certainly not enough, because connection is crucial. (The latter statement in bold, is actually one of the first lessons I learned as a public speaker).

D4P...PD!!!
-OBE