Washington, D.C.

Why Jayson Werth Will Help The Nationals

Considering the less-than-thrilling manner in which the Washington Nationals’ 2010 season expired, I’d pretty much been avoiding watching baseball regularly. In fact, I avoided it so well that I had no idea that winter meetings were beginning. But the Nationals sure didn’t forget. They kicked off winter meetings with the stunning announcement that they had signed free agent outfielder—and former Philadelphia Phillie—Jayson Werth to a 7-year, $126 million contract. I’ll paraphrase my reaction: “What? We got him?”

Redskins vs. Buccaneers: The Good & The Not-So-Good

You know how after a loss, athletes and coaches often make reference to the fact that the loss wasn’t attributable to any specific play but rather to a whole host of missed opportunities? Well, to a certain extent, that’s true. For example, against the Buccaneers, the Washington Redskins wasted numerous opportunities to put the match in a choke hold. We’re talking missed field goals, blown red-zone possessions, and untimely turnovers. But in a way, blaming a loss on missed chances doesn’t cut it. For example, against the Buccaneers, the Redskins fought their way back after being down by one score, only to lose the game because of one play that went horribly wrong (more on that later). Of course, either way, you’re still talking about a loss, so maybe the finer nuances of responsibility aren’t worth griping about. And on that note, I present to you the good and the not-so-good from Sunday’s game against the Buccaneers.

Redskins vs. Giants: The Good & The Not-So-Good

You know, the more I think about it, a 31-7 beatdown was exactly how I thought things would go for the Redskins on Sunday. They haven’t beaten the Giants in nearly three years (a span during which the team has been outscored 138-50), so it’s not like I was holding out any hope for an upset win. I was, however, still determined to still hold the team to the standard of what has become my unofficial mantra for the ‘Skins 2010 season: “Just don’t embarrass yourselves, guys.” But like always, they didn’t even meet that expectation. Here’s the good and as much of the not-so-good as I can stomach from Sunday’s loss in New Meadowlands.

Redskins vs. Vikings: The Good & The Not-So-Good

Being the experienced Redskins fan (and closet pessimist) that I am, when I heard the news that Minnesota had fired Brad Childress and replaced him with Leslie Frazier, I had one of those sinking feelings that told me the ‘Skins would lose this game. Oh, sinking feeling, why are you always right? Of course, it’s not like the team didn’t have chance to pull out a victory. But once again, the Redskins found ways to beat themselves. Here’s the good and the not-so-good from Sunday’s loss to the Vikings.

Redskins’ Offseason Plans: Drafting Needs & Saying Goodbye

Once again, it looks like it’s going to be another tough offseason in Washington. That’s because, as is their custom, the Redskins are long on needs and short on draft picks. The team also has plenty of unproductive salary and old weight dragging on its roster. But for a team that’s been as poorly-managed as the ‘Skins have for the last decade, that’s par for the course. So no more stalling; here’s what the Redskins need to do this offseason to keep them on the path to contention.

 

Redskins vs. Titans: The Good & The Not-So-Good

The Washington Redskins are still alive. With a decidedly unpretty victory in Tennessee on Sunday, the “Gold Pants” Brigade evened their record at 5-5, ensuring that they remain two games ahead of a resurgent Cowboys team and at least one game behind either the Giants or the Eagles. But more importantly, they washed the stink of last week’s humiliating loss away. And while the team’s 19-16 overtime decision against the Titans might not have been the best bounce-back performance, the Redskins can still call themselves winners—at least for the next week. Here’s the good and the not-so-good from Sunday’s contest.

Eagles-Redskins: The Good & The Not-So-Good

Over the weekend, I posted some of the key questions that Monday night’s game would answer. But in a 59-28 defeat, the Redskins decided to answer a question that I apparently forgot: Why just lose when you can completely and utterly implode?

Fun Facts about Eagles-Redskins

Since we have an extra day to kill before this week’s latest installment of the Eagles-Redskins rivalry, I’ve put together some interesting numbers to help pass the time.

 

(NOTE: The predictive value of these stats is highly questionable considering all of the mitigating circumstances involved. But I love looking at stats, so I figured I’d see what I could find. Basically, you should just take them with a grain of salt.)

Eagles-Redskins Should Answer Some Key Questions.

How fitting that during the week in which it holds a marquis slot, the rematch between the Eagles and the Redskins will also likely be one of the most compelling games to watch. Just look at the storylines that surround the matchup. On one side, a resurgent Michael Vick has returned to the field for the Eagles and is continuing his trend of making Philadelphia an all but unstoppable opponent. Meanwhile, the Redskins have been weathering the fallout from Mike Shanahan’s questionable decision to bench Donovan McNabb for two weeks and are a undoubtedly ready to put that wonderful chapter of their season behind them. But will they? Or will they just become the latest obstacle to be steamrolled by Michael Vick’s high-powered Eagles offense? Those are just a couple of the questions that this game will answer.

Questionable Call Of The Week: Why Bench McNabb?

In just two short days, Mike Shanahan’s now-infamous fourth-quarter decision to let Rex Grossman run the two-minute offense instead of Donovan McNabb has gone from merely frustrating to utterly outraging. If the sports media’s talking heads are to be believed, Shanahan has now embarrassed himself, humiliated a high-caliber quarterback, lied to reporters, and completely lost his locker room. So considering all of that fallout, why even bench McNabb in the first place?

Syndicate content