Skip to main content

The Redskins are fools

  • What killed the Redskins last season was the break down of the offensive line. The defense ended the year ranked 4th in the league, behind only Steelers, Ravens and Eagles. That means the Redskins defense ended the year ahead of the Giants D with their vaunted d-line. Granted the Redskins D didn't make much game-changing plays (28th in sacks and 17th in INT). But given all that, you would think the pressing need this offseason would be getting O-line help, right? Well that's conventional logic. Around here, we buck convention. We went out and got Haynesworth (DT) and Orakpo (DE/LB). We re-signed DeAngelo Hall (CB) and signed a FA punter. For the O-line, we signed a former Redskins that didn't play last year in Buffalo (not exactly a team with a stout o-line).
  • For the first pre-season game, conventional logic say you give your starters enough reps to get in a rythm, then you play your backups. Against the Ravens yesterday, we allowed Jason Campbell to pass just 6 times (3 of which were incomplete)! Meanwhile, Joe Flacco (a second year QB) was out there slinging passes like a multi-year pro-bowler.
  • To further buck convention, we decided to hold out a few of our starters. Santana Moss, Clinton Portis, Albert Haynesworth, Carlos Rogers and Randy Thomas weren't even dressed for the game. Granted Thomas was hurt, but why not put your $100 million man (Haynesworth) out there to see what he can do in your scheme? If you are scared of injuries, wouldn't you rather he got injured now than later?
  • Conventional logic says you can't take anything away from preseason games. But I think that's not true. This was the Ravens first game since last year (and they've had less time since they went deeper in last year's playoffs). They were more physical, sharper, crispier (save for a few penalties) and to add insult to injury they blanked the Redskins and put up 500 yards of offense (to the Redskins' 196). This from a team that's predominantly run-first. So yeah, theRedskins can take away 2 things from this game: 1. we suck and 2. unless things change, Jim Zorn better be looking for a good realtor.
I know it's only the first preseason game but I think Redskins fans are in for a world of disappointment this year. Being Redskins fans, we ought to be used to it by now!

Comments

Popular posts from this blog

The Teenage Years Cometh

If you're lucky, a few days after your twins are born, the hospital just let's you walk out with them. In fact, they insist you take them with you. No training, no classes, no probation...they really just let you walk out with 2 humans. #fatherhood — Tundey A. (@realtundey) November 28, 2021 This was me 12 years ago: And now look at them. In a little over 6 months, they'll be teenagers!   Every time I look at them, I am reminded of Obama's quote on being a parent:  "One of my favorite sayings about having children is it's like having your heart walking around outside your body." — @POTUS — White House Archived (@ObamaWhiteHouse) October 21, 2015

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said: InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... ( more ) Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A h

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology. InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment , has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options: convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations) use one of Al Gore 's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously . You'll need every bit of time you can get. quit immediately while you still have your sanity First, InfoPath: To me InfoPath is like programming in assembly language . Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button : in most technology: buttonA.enabled = false (or something similar). In InfoPath, you simply