Michigan needed that game.

I'm not upset. They slept walked through the game. Got win and now Hoke has there attention. This is a young team. The defense made mistakes. Gardner was horrible and the lines were horrible, but they won. Now when coaches tell them that they aren't that good, now they will listen.

I'm with you.

Most players don't follow college football half as much as we do. They don't realize that this year's ND team is nothing special. In their minds, they just beat the defending NC Runner Up. I can definitely see how they went into this game thinking they are invincible.

Now come back to earth and use UCONN to prepare for Big 10 play.

Hopefully they do learn from it. I hope they show that game in practice every week for the rest of the season. Frankly, they should have been able to play 2nd and 3rd stringers and still won that game.

I wouldn't be surprised it they come out and destroy UConn next week.

fishgoblue22 wrote:

I wouldn't be surprised it they come out and destroy UConn next week.

I hope you are right. They need to make that happen...big time!!!

I am all in with the new banner!!!!!!!!!!!!

Go Blue!!

fishgoblue22 wrote:

I wouldn't be surprised it they come out and destroy UConn next week.

They had better, Fish, or I'll never hear the end of it, here in Maryland, home of this "other" U-M which
dumped the Huskies yesterday (32-21)...

For me, the best thing to come out of the most embarrassing, humbling victory (pardon the paradoxes)
in our program's history was Taylor Lewan's post-game rant:

"We did not prepare. We should be ashamed of ourselves for our fans, our students, our coaches, our
university. It's all on us, captains and seniors. It will NOT happen again. If we have more weeks of
practice [like this last one], we won't win another game all year."

I'm of similar mindset as Fish.

Am I happy with yesterday? Well, of course not.

However, I knew we were going to come into that game extremely sluggish. Multiple people mentioned the spread on the game to me during the week (all non-UM fans that like to bet CFB), and I told every single one of them to take Akron to cover. I believe the line was 32, maybe a little higher? Despite how bad Akron has been over the last few years, I just knew we were going to come out flat. My pregame prediction was that we'd "give up an early FG, and the O will start very sluggish. We come out second half and get it back together. 38-9"

The first part of my prediction was spot on...not the rest, of course.

Anyway, we can sit here and bitch and moan about what happened, or we can move forward.

We're certainly asking (demanding) that the team learn from this, move on and improve. As fans, I think we should do the same.

If we continue to lament on this game, I have this weird gut feeling that it's going to have a negative effect on our team in the long-term of this season.

I would hope that this team doesn't give a damn about what posters on an internet board think and say. If it does care, then it has a real problem.

Yesterday doesn't come as too shocking to me. Did I think that would happen? Not exactly, but Akron runs a version of the spread.

2ndComingOfBo wrote:

Yesterday doesn't come as too shocking to me.  Did I think that would happen?  Not exactly, but Akron runs a version of the spread.  

I get your point, it makes sense. I guess I expected akron to score a bit too. Just not 24. the real surprise was our offense. it was offensive.

IMHO the offense was to blame for that game. Turnovers create momentum swings and guess what? We lost FOUR of them...

2ndComingOfBo wrote:

IMHO the offense was to blame for that game.  Turnovers create momentum swings and guess what?  We lost FOUR of them...

turnovers are normally the one best indicator (if you have to pick one) and it was 4-2, but when a team that's coming off 3-33 the last 3 seasons and losers of 27 (now 28) in a row on the road, who got rolled by the D1 team they played this year gets 21 first downs, 400 yds and 9-18 3rd down conversions, it's hard for me not to say the defense was a big problem.

'shoes