Amazon Banner

Monday, October 31, 2011

Week 8: The Washington aftermath




That game in Toronto was pretty bad.  Honestly, there's just not a lot that can be said about it (well actually, there is PLENTY that can be said, but I'm trying to stay positive).  What has now been made painfully clear to everyone watching, is that The Redskins are still a work in progress.  Of course that isn't breaking news.  But the total breakdown of this football team in so many areas is.

Predictably, the calls for Mike Shanahan's head have begun.  Jason Reid of the Washington Post and Rick Snider of the Washington Examiner haven't called for his resignation yet, but they have both implied that this scenario is on the table.  Ladies and Gentlemen, welcome to Washington's darkest hour.  Today, there is no joy in Mudville.

Friday, October 28, 2011

FOOTBALL FRIDAY: Week 8 - Thoughts, Picks, and Other Stuff

What a day.  What I thought would be a breeze of a day turned out to be a bear....ugh!  The good news is that nothing earth-shattering happened, besides me not being able to post my Friday picks until after the workday.  ;-]  


Seriously, I would love to throw out last week's picks.  Man, they were terrible!  I tell ya, I learned last week that picking football games on the record is not as easy as I thought.  Then again, a little bit of humble pie never hurt anybody.  I am a better man for it.  Now that I've indulged you with my petty excuses for that crap last week, let's get to the picks!




Last week: 2-2
Against the Spread:  0-4 (uuuuuugh!!)








Jacksonville Jaguars (2-5) vs. (-10) Houston Texans (4-3)


Houston really made me look like a fool last week for pickin' against 'em.  I won't make that same mistake again this week.  Jacksonville played inspired ball on Monday Night, but can they Win with a rookie quarterback on the road against the top dawg in division?  Nope.  Division games are tricky, but the Texans won't fool me twice!  They should cover the 10 points.





Minnesota Vikings (1-6) vs. (-31/2) Carolina Panthers (2-5)

The Rookie Bowl.  Now that it is Christian Ponder's Vikings facing off against Cam Newton's Panthers, this game has a good bit of intrigue.  Two Rookie Quarterbacks, both drafted in the 1st Round of this past April's NFL Draft, makes this one a game to watch.  Or, at least peek in on.  For me, it's simple; Cam Newton is AWESOME!  I say he Wins at home and looks fabulous.  I'll even take him to lick the spread (but it should be close).




(-14) New Orleans Saints (5-2) vs. St. Louis Rams (0-6)

Man, maybe the league shouldn't schedule doormat teams to play New Orleans.  Apparently, the Saints DON'T like losers (just ask Indianapolis), so I expect this one to get pretty ugly.  Conversely, the Rams just can't buy a break.  They have had BY FAR the toughest schedule in the NFL this year.  Of course, this week, it doesn't get any easier.  But the good news for St. Louis fans is that they'll be able to get a busload of picks for trading the #1 overall draft choice.  Saints roll.  (and cover)






(-3) Detroit Lions (5-2) vs Denver Broncos (2-4)

I like Detroit all the way in this one.  In fact, I'm surprised they're only throwing Denver 3 points.  T-bag is a gambler's dream, cause he won't beat any teams of Detroit's caliber.  I'll give him those three points.  He's gonna need 'em!




BONUS MATCHUP!



Dallas Cowboys (3-3) vs (-31/2) Philadelphia Eagles (2-4)

This will be a slugfest!  Not only is it an NFC East game in prime time, but its Cowboys-Eagles.  Philly absolutely hates Dallas, so they'll be extra motivated to beat them and pull to one game under .500 on the season.  The Cowboys have their own motivations, given that a Win in Philadelphia would put them in second place in the division, poised to make a move on division leading New York.  The stakes are high for this mid-season matchup, so it should be fun to watch.  I'm taking the Eagles in a close one here.  Dallas has talent, but their not going into Philly and beating the Eagles.  I'm not convinced they've got that kind of moxie this year.  Philly Wins in a nail-biter, but doesn't cover.




This should be an especially fun weekend for football.  Enjoy the games everyone!  Until next time.



Thursday, October 27, 2011

What Makes A Losing Football Team?

Hey everybody.  Happy Thursday!  Today, I am going to begin a discussion of the elements that contribute to a football team's success or failure on the field.  Obviously, a lot of factors play into the eventual results that any Pro Football team achieves on the field.  However, I intend to specifically deal with the results obtained strictly through gameplay.  And for the sake of easy comparison, let's go from bad to good.  Check it out.



So what exactly explains why teams some teams lose or are considered losing teams?  Is it bad play?  No talent?  Poor Coaching?  Bad luck?  I would say yes to all of these questions.  And let's face it:  in the NFL, everybody will lose a game at some point or other.  That's pretty straightforward.  But what I'm interested in discussing is why certain teams seem to consistently get beat week in and week out.

In fact, in scanning what was already out there before this post, I noticed that Pat Kirwan of nfl.com had written an article awhile back on practically the same topic.  I enjoyed his insights when he worked for Sports Illustrated,  but I don't get to read him much now.  As for his article, I think he's right, although I would add several more factors for consideration.  Observe this list and notice how many of these you spot in the next game you watch.



  • Losing teams have a low talent level - Many losing football teams suffer because they simply don't have much talent compared to rival teams throughout the league.  This is typically the toughest hurdle to overcome, because it's hard to compete with a team that is more talented.  A poorly talented team doesn't make plays consistently enough to Win football games.  
  • Losing teams have no depth - For a losing team to have any success, it relies on a small core of players to play at a high level just to be competitive.  If any of these core players are hurt, the entire team is sunk because the talent level behind the best, or core players is inferior.  Winning with no depth is unreasonably difficult.
  • Losing teams are hurt by turnovers - This is such a critical factor, because a good team can have a losing season due to a turnover-plagued campaign.  Turnovers kill.  Nothing is harder to watch than a football team hurt itself with fumbling away the ball deep in their own territory or throwing the decisive interception at a critical point in a contest.  Conversely, a defense hurts it's team by a lack of forcing turnovers.  But turnovers on special teams are probably the worst, since special teams plays involve scoring or trading possession of the football.  To give the football right back to the other team is a death knell.  Turnovers represent giving, or gaining extra opportunities to score and Win.  Most times, turnovers decide football games.
  • Losing teams are hurt by penalties - The fact of the matter is that penalties are as much a part of the game as blocking and tackling.  All teams commit penalties, but only some teams get snake-bitten by them.  I like Kirwan's thoughts on this matter, and will borrow his concept of "concentration penalties".  These are precisely the sorts of penalties that beat losing teams.  Procedure penalties are a reliable partner in sabotaging games and seasons.  False starts on 3rd and Goal, defensive holding on 3rd and 17, running into the kicker when receiving a punt, and dead ball fouls that keep opposing drives alive.  These are examples of the penalties that help defeat losing football teams.  
  • Losing teams fail to capitalize - Every team plays well in stretches, and losing ones do as well.  But often what separates losing teams from the pack is the fact that they typically fail to take advantage of opportunity.  Perhaps you've seen a game where x doormat is outplaying y contender for a period of time, but x team can't seem to fully take advantage of it's good fortune.  Maybe they can't score touchdowns.  Or maybe they get a crucial turnover but don't score.  Or even their opponent suffers an injury to it's best player(s), but aren't exploited by these injuries.  Good teams take advantage of the opportunities presented to them and capitalize upon them.  Bad teams don't.
  • Losing teams have bad luck - You've seen this one before too.  And not just in football.  When it rains, it pours.  The problem for losing teams is it seems to do both on it's head!  In a game that a team could be Winning, it gets a touchdown overturned, or loses it's best player, or has the fluke play go against it.  It could be any number of things that are only explained by labeling them as "bad luck".
  • Losing teams beat themselves - It never fails to amaze me how often a losing team will beat itself!  A losing team does not only fail to take advantage of the opportunities it gains, it also hands its opponents prime opportunities to beat them.  A losing team will have a trick play called that fools their opponent at the right time, and fail to execute the play!  A loser will score a touchdown on a special teams play, only to have the play overturned due to penalty.  A loser will be Winning a game late into the 4th quarter, only to commit an turnover on a needlessly risky play call.  A loser will knock itself out of field goal range for the Winning score because of a routine procedure penalty.  Losing teams too often help their opponents beat them.
  • Losing teams have poor execution - This is endemic to a losing football operation.  Fumbled snaps.  Shanked punts.  Muffed punts and kickoffs.  Dropped passes.  Horse collar tackles.  Facemask penalties.  Dead Ball personal fouls.  The list can grow quite long, but the point is the same.  Bad teams suffer from not executing routine football functions and plays properly.
  • Losing teams play poorly - To me, this is the worst factor on the list!  Not all losing teams have no talent.  In fact, many have an impressive level of talent, yet play below reasonable standards.  Poor play is defined by a lack of effort that leads to bad results.  For instance, a team that offensively cannot string together successive first downs is playing poorly.  A team defensively that is unable to stop their opponent from steadily moving the football down the field and/or scoring is playing poorly.  Poor play is normally the culmination of several factors on the list, if not all of them.  And invariably, poor play reflects either insufficient talent, a team experiencing a learning curve, a team dealing with adversity, a young or inexperienced team, or a poorly coached team.
  • Losing teams are consistently flawed - A team's success rate is reflected by the habits it develops in the heat of competition.  Unfortunately, losing football teams develop bad playing habits that plague them on a regular basis.  These bad habits show up reliably at inopportune times, leading to substandard results.  


These tend to represent the hallmarks of bad, losing teams at any level.  And as I am certain you will note going forward, these factors do indeed rear their ugly head on struggling teams.  Watch and see for yourself.  How many bad teams have you seen play this season?


COMING SOON: What Makes Up An Average Team?



Tuesday, October 25, 2011

That Was A Very Ugly Bellyflop

The Baltimore Ravens' 12-7 loss to The Jacksonville Jaguars was confounding.

It seemed like all that was required of the football team was to show up, bodyslam the Jags a few dozen times, and strut away with an easy Win.  A 'W' that could give them some serious momentum en route to eventual possession of home field advantage throughout the playoffs.  Or so the conventional wisdom went. Then, inexplicably, they played woefully and handed Jacksonville the hammer to bash those plans into tiny shards of broken glass.  Unbelievable.

Some of the post game analysis I've seen from Mike Preston of the Baltimore Sun squarely hits the mark.  Frank Sullivan of yardbarker.com lends interesting insights to this game as well.  It's hard to quibble with what these guys have offered in reaction to the game.  However, I feel there is a bit more to add.







  • Flacco just seems (inexplicably) incapable of turning the corner to consistency.  Sorry Baltimore fans, but there are too many times when you watch this guy play that you blurt out "what the fuck was that?"  I've defended him many times, cause he plays well enough to fool ya.  As soon as you start giving him props though, he pulls one of last night's numbers.  That crunch time interception feeds the fire in Bmore that he can't get it done when it counts.
  • For my money, the weirdest aspect of the game, was that Ray Rice barely touched the ball.  I understand that he was puttin' the rock on the ground.  I understand that the staff sat him for awhile to teach him a lesson.  But the Ravens can't don't Win without this guy.  And they didn't.  Observe that the Jags knew that they couldn't Win without Maurice Jones-Drew, no matter how many times he fumbled.  They stuck with him...and he rewarded that commitment by rushing for 100+ yards on the night.  Maybe the Ravens should learn from the opponent's example, eh?
  • Further, the Defense allowed waaaay to many rushing yards.  Clearly the Rookie Quarterback wasn't going to beat them.  That dink and dunk stuff Jacksonville called was not an effective passing attack.  So their only option was to rely on the run.  And it worked.  The Jaguars controlled the clock, the tempo, and the field position the majority of the night.  The Raven defensive coaches had to know that given the scenario, their opponent was severely limited.  Yet they still let the rush beat em.  To me, that was the difference in the game.
  • But it was the Jacksonville kicking game that actually Won the contest.  Kicker Josh Scobee had an MVP night, nailing 4 field goals, including 3 50-yarders(!!) to beat the Ravens.  But it was the Jags punt and kickoff teams that really controlled the game, bottling up Baltimore with bad field position--a textbook example of why special teams are the critical third element of the game.
  • All that said, the most egregious offense on the night was committed by Ravens Head Coach John Harbaugh.  Right after the Baltimore touchdown, Harbaugh had two timeouts, a talented veteran defense, his own quality kicker, and most importantly, a couple seconds before the two minute warning.  The announcers in the booth, as well as myself, fully expected him to kick it deep for a touchback (so the game clock would not start).  That way, after Jacksonville's first play of their possession, there's a guaranteed timeout because of the 2-minute warning stoppage.  And with two timeouts, theoretically, the timeouts would stop the clock as the defense held the Jags to a 3-and-out.  They punt, the Ravens would get the ball around midfield with plenty of time left to mount the game winning drive.  At the time of the kickoff, the score was 9-7, so a Baltimore field goal would be the go ahead score.  Harbaugh elected not to go that way.  He onside kicked, the Ravens were penalized for illegal touching, and although the defense prevented the first down, Jacksonville was already in position for the game-clinching field goal.  Once Scobee nailed that (based on how poorly Bmore's Offense had played), the game was essentially out of reach.  That's poor tactical strategy on Harbaugh's part.  Plain and Simple.  


Baltimore was humiliated on national television with such a surprisingly lackluster performance.  The die was all but cast that they were the class of the AFC with a much anticipated Win.  But in the aftermath, the thinking has changed considerably.  Of course at 4-2, the Ravens are in a pretty good position overall.  The most damaging aspect of this loss comes in ceding the division lead to their hated rival Steelers.  But there's more than enough time to sort that out.  What we do know now is that there is no clearly dominant team in the AFC this season.  The Baltimore Ravens are right there though.  But it's also clear that they're right there in the jumble, and not able (or willing) to separate from themselves from the crowd and stand alone.



Monday, October 24, 2011

Six Things I Learned About The Washington Redskins After Week 7


Good Morning everybody.  Well, I've had time to sleep on it, wake up, drink some coffee and relax a little bit.  Ahhh, yes.  Now back to talking more shit!

Washington is a team that is rebuilding.  That is the cut-and-dry, no-nonsense, tell-it-like-it-is truth.  Most Skins fans don't wanna hear that crap though.  Of course it doesn't help matters when the Head Coach is running around saying shit like he doesn't like using the term 'rebuilding' because it implies that you can't Win now.  Fine dawg; do what you do.  But don't be surprised when Redskins fans actually expect to Win NOW.

Now don't get me wrong: I watch every ballgame expecting to see the team Win too.  That is the nature of competition.  Still, my expectations for this year's team is 9-7.  I think The Redskins have a decent shot of attaining this goal.  It'll take a few lucky bounces, sure.  And the fellas will have to beat three or four legitimate quality teams.  That shouldn't be too tall an order...let's hope.

Anyhow, with this goal in mind, let's review the six things I learned about the Washington Redskins after Week 7.



  1. Washington Needs More Depth - There is no doubt about it.  We're reaching that point of the 2011 campaign when every team is a little dinged up.  Some more than others, obviously.  What will keep the Redskins in the mix throughout the course of the season this year, and for years to come is having quality backups ready to come in and deliver at a moment's notice.  I'm not sure that the team is quite there yet.
  2. John Beck Needs Time To Settle In At Quarterback - This is why I disagreed with making the switch.  Beck (and the entire offense) looked out of sync yesterday.  It is wholly unreasonable to expect him to come in, after not starting since George W lived in DC, and  play well.  Hell, I wanted him to, but that is asking a lot from the guy.  But that doesn't mean he's no damn good either.  It just means he needs to get acclimated.  I expect better play up in Toronto this Sunday.
  3. The Defense Clearly Had A Bad Day - A football season is a marathon and not a sprint.  Under those circumstances, I consider that defensive performance to be a 'bad day'.  Now this is the second time in a row that they got hit square in the chops.  Last week they fought back admirably.  This past Sunday, they got their ass whooped.  Hell, it's the NFL.  Happens to everyone at least once.  I can forgive that, because overall, the D looks good this year.
  4.  The Redskins Must Start Playing To Their Strengths - It's not rocket science y'all; Washington, beats people in 19-13 kinda games.  They don't Win shootouts.  This is not New Orleans.  I am getting sick of watching The Redskins pass so much when they are within one score of the opponent!  That is not the team's strength at the moment.  This team is built to control the tempo by running the ball, play action pass off the rushing threat, play to Win a field position battle, and play sound defense that keeps em in every ballgame.  That gives em opportunities to Prevail. 
  5. Washington Will Learn Who They Are Now - Earlier this season when the team, was 3-1, everything was peaches.  Now with consecutive losses for the first time this year, we will all find out who this Washington Redskins team is in short order.  I am a firm believer that adversity tests character.  Are The Skins legit?  Or are they a mirage?  We'll find out now since they've been humbled a little bit.  Here's the test.  The Next opponent, The Buffalo Bills, think they're pretty good.  And they have a record that reinforces that belief.  Now what kind of Washington team will show up in Toronto?  A flat, lethargic, complacent bunch -- or a horde of ass-kicking goons that kick open the door and start swinging?  I wanna see them goons!!!  We will find out soon.
  6. A Successful Season Is Still Possible - The reality is that with a 3-3 record, DC's season can go in myriad directions.  Many of those directions leads to positive outcomes.  But the fact of the matter is that it's decision time.  Every team gets banged up.  Every team suffers a little adversity.  Every team has a few tough draws, or difficult stretches on the schedule.  What truly matters is how a team deals with these types of obstacles.  Successful squads navigate these stretches well and overcome any percieved obstacles.  Where does Washington rank?  Stay tuned.




Sunday, October 23, 2011

Week 7: The Post-Game Rant (Part Deux)



What Now, Coach?


The squad is 3-3, on a two game losing streak, and the injuries are piling up AFTER a questionable (by me) Quarterback change that produced nothing but more doubt.  Oh boy.  And we haven't even entered the difficult part of the schedule.  And if the Head Man doesn't get this mess straightened out soon, Washington's going to end up on the wrong side of .500 after Week 8.  Do you think Mike Shanahan is having fun these days?

Going into the Regular Season, my read on the team was that they could make some noise if   a)D.C. got great play from the quarterback position  b)they stayed healthy  c)The Redskins had an outstanding year in turnover differential, and  d)Washington caught a few lucky breaks.  Those things are true of the overwhelming majority of the teams in the NFL.  Washington's no different.  But in order to succeed in the short term, meaning this season, The Redskins Football Team had to handle all four areas in order achieve measurable success in 2011.

  1. Quarterback - Before the season (and this blog) began, The Redskins held an open QB competition to determine the team's starting quarterback.  And at that time I favored John Beck, but Rex Grossman beat him out.  No biggie, just Win ballgames.  That's what Grossman did.  But the book on that guy's always been he's a turnover machine.  Of course he did turn the ball over during the course of the season, but we already knew he was prone to this kind of behavior.  That didn't seem to be a big deal until he famously threw 4 interceptions in a home division loss to the Philadelphia Eagles in Week 6.  He played like shit that day, but he did lead Washington (at that point) to a 3-2 record.  So what does our sage Head Coach do?  He fires him!  He benches him for the rest of the game in the 2nd half (understandable) and switches QBs during the week (WTF!?).  I disagreed with that move because it looked panicky, and was very risky.  I hope those reservations have not come to pass.
  2. Injuries - Look, staying healthy just ain't happening.  This is an ominous sign of troubled waters ahead.  Truthfully, the ballclub just doesn't have the depth to withstand a signifigant bout of injuries.  The starters can play with damn near anybody.  But the backups, particularly at certain positions *Offensive Line* *AHEM!* simply couldn't make too many other NFL rosters.  Consequently, when a team with depth issues starts gettin' hurt, that team's ability to beat quality competition is diminished GREATLY.  Consider by the close of the game, The Redskins were playing without their starting #1Wide Reciever, Running Back, Left Tackle, Left Guard, Tight End, Center, Free Safety, and Inside Linebacker.  If you include the Quarterback change, that's almost 40% of the starting lineup out.  It's tough to beat anybody with a roster that banged up.
  3. Turnover Differential - A quick definition is how many times a team gets the ball vs how many times they give it away.  Honestly, I haven't even viewed the official stats in awhile, but I do know that The Redskins Offense has been far too turnover prone, while the Defense can't seem to force the turnovers.  Take Sunday for example.  Washington turns the ball over 3 TIMES(!!!) and doesn't force a single one.  That gets you beat, plain and simple.  Turnover diff. is the most important stat in football for that very reason.  NO OTHER FACTOR has more impact on deciding individual games and entire seasons.  The Skins are not Winning in this critical area.   That's the bottom line.
  4. Opportunities - There can be a very fine line between success and failure in the National Football League.  That's the reality.  So when a team faces an opponent that is vulnerable, that team must capitalize upon the opportunity presented to it.  At the beginning of the year, Washington did this.  They faced a New York Giants team that was badly beat up in the season opener.  They capitalized on this opportunity by beating them.  Good work.  In the next few games, the team faced opportunistic circumstances in terms of their opponents on the schedule.  Fortunately, they were able to take advantage of these favorable circumstances.  Fast forward to this past game.  I felt that although Cam Newton was a dynamic sensation, he was still a Rookie Quarterback, facing a high quality defense.  I did expect him to give The Skins some fits, but I definitely wasn't prepared to watch him thoroughly beat their ass the way he did.  Hell, if that was a fight, I'd have called the police!  That was disgraceful!  That is NOT taking advantage of a Rookie QB.  In fact, we all know who got took now.

The way it's looking approaching the midway point of the year, adversity has visited the Nation's Capital big time.  It remains to be seen how The Redskins Football Team will navigate through this turbulence, because the record is even towards midseason.  That means that success is still within reach.  What remains to be seen, however, is will Coach Shanahan be able to right the ship, and steer the team towards reaching it's predetermined goals - or not.  Stay tuned, because the season got a lot more interesting today.  But we do know one thing for certain: I am wearing my Skins hat to work in the morning.  Damn right!!


Week 7: The Post-Game Rant



Let the laughter begin.  That game, from a Washington Redskins fan's perspective was painful.  It reinforces the notion that Redskins football still has a pretty long way to go before it's taken seriously again.  Believe it or not, I'm not going to overreact -- mainly because I cussed out the TV before I passed out after the game.  Therefore, I'm good!  But let's just touch on a few things...

Washington entered Sunday 1 game over .500 playing a team that they "should" beat.  True, Carolina has Cam, but those guys don't have much else.  And now they've got to face a top 5 defense with a top 5 pass rush.  Tough sleddin' for the Panthers.  Or so the conventional logic went.  And then they played the game.






And then there was THIS ONE!







Man, that dude is amazing!  Even I stood up and hollered after watching that one.  And all that happened on the First drive of the game!


Okay.  Getting back to the rant.
As much as it pains me to say, it's beginning to look like Washington's turned into pumpkins after the fast start.  If you insist on some of the gory details, check out the DC Sports Bog.  Steinberg's gotchu covered.  Me, I had to take a shower after reading the coverage.  It hurts to watch your favorite team in life become the homecoming opponent.  When will The Skins stop fuckin up and act right?

Look, the squad's 3-3 and still in contention for a lot.  The trouble is that the fellas is slidin' the wrong way with a no-nonsense opponent on deck.  The Buffalo Bills have been playing some quality ball this season, and they sat home on their bye and watched a Redskins team play like chumps.  I can hear them licking their chops.  It doesn't get any easier.





Saturday, October 22, 2011

THIS IS A TOUCHDOWN??? BULLSH#%!!!





Here's a really good one for ya.  This comes from a college football matchup between the Wisconsin Badgers visiting the Michigan State Spartans in a crucial "Big 10" showdown.  If you follow college ball, then you know all about the money-grubbing conference realignment stuff.  Hell, the Big 10 ain't had ten teams in their conference since I was in school (let's just say that was a looong time ago).  That's another discussion altogether.

Anyways, check the scenario:  Wisconsin showed up in East Lansing (State's home turf) undefeated on their season, and ranked as the #6 team in the country.  Michigan State has been having a helluva year themselves, ranked #16, and looking like they wanna be a Big dawg.  There's plenty on the line here:

  • Wisconsin entered the game in serious contention for the Big 10 Title AND the National Championship.
  • Michigan State entered the game leading their own division within the conference, looking to make a statement on national television.
  • The Winner would be the hands down favorite to take the conference title.

Now the game ended up tied, going into (likely) overtime after the final play.  And this part happens all the time.  A tied game is headed to the extra session, except for the hail mary pass at the gun.  And of course 99 times outta 100 the pass gets knocked down.  That other time...take a look





"Instant replay will have to decide now."  

What....THE FUCK....is that??!!!

I've got a huge problem with how this game ended.  Now I'm not mad at the Spartans.  They Won - cool.  What bothers me is how this game was determined.  The Winner was decided by some unseen, unknown bastard in a booth.  That's bullshit!!!

Wisconsin got robbed.  Consider two points: 1)the ruling on the field was that the guy didn't get in   2)typically under the circumstances, i.e. a tight ballgame, the refs let the players decide the outcome.  Now watch that clip again.  Was the ball crossing the goal line definitive enough to hand Michigan State the game, the inside track on Winning the Big 10 crown, end Wisconsin's undefeated season AND likely dash their National Championship hopes?

There's a whole lot riding on that call; not only does it have to be definitive enough to hand one team victory over another in the moment, it must be solid enough to withstand the avalanche of criticism.  Especially from Wisconsin backers, because it ended their championship hopes.  Do you see my point?

At this juncture of the season, a pivial matchup can have all kinds of implications.  Not just directly on the teams' seasons in the game, but also on the outcome of a given conference race, and even on the National Championship picture.  If Michigan State beats Wisconsin in OT, or the Badgers simply fuck up and hand Sparty the game, that's one thing; we can all live with that.  But such high stakes literally being decided by an arbitrary instant replay call is nonsense.

The solution to this mess is was simple.  Let the call stand on the field, go to overtime, and stand back while the Badgers and Spartans fight as long as they needed to, to settle it on the field.  Now THAT was the right call.  What do you think?

Friday, October 21, 2011

FOOTBALL FRIDAY: Week 7 - Thoughts, Picks, and Other Stuff

I love Fridays during the season.  All the fans are wearing jerseys, shirts, and hats of their favorite teams.  The flags with team logos zipping around town, and the billboards supporting the community team always puts me in a good mood.  I love the banter between the followers of different teams, and listening to their (reasonable or otherwise) prognostication of the weekend's matchups.  But I truly love reading the sports page of the papers to get a feel for the games, and the individual teams.  


It's fun to read a guy's opinion on a team or matchup in the paper and rant about it.  I don't know how many times I've read some dumbasses' take on a game and thought "does this dude even WATCH the games?"  But there are also times when I've scoffed at some hack's call on a ballgame and thought late into the third quarter "well how about that?  That sonbitch was right!"  And of course I can do a better job than half those fools.  So....I did the foolish thing and decided to pick a few games my damn self.  Have fun ranting at my opinions.

Hello World!

First of all, I sincerely thank you for visiting this site; this is the 1st blog post I've made in my life!  I'm really excited about the prospects, and I do hope that you are too.  Aside from my friends and family humoring me by making the obligatory visit, I will assume that one or two people out there in internet land check out these posts.