How many times have I written a "this is just so frustrating" post? 25 times? And now I'm supposed to write it a 26th time? Interceptions, fumbles, muffed punts (two!), drops, a blocked punt, and a fairly balanced game becomes a blowout. This is just so frustrating.
Yes, I'm on the record with two things:
1. We were going to lose this game by 20.
2. After our crazy turnover luck the first four games, a correction was coming.
This was (more of) that correction. And we lost by 19. So by tomorrow morning, I'll calm down and see that things are more or less aligned with my expectations. But when you get a defense that only allows Nebraska to be 4-12 on third down, and you pick up 509 yards on offense, and it doesn't come anywhere close to mattering because of two interceptions, a fumble, four drops, two muffed punts, and a blocked punt... it's just so incredibly frustrating.
And in the midst of my frustration meltdown in the second half, what happens? Bobby Roundtree gets a strip sack, Jake Hansen falls on it, it squirts out of his grasp and squibs out of bounds - Nebraska ball. I don't care what you say, that's turnover #6 for the game. That's a fumbled fumble.
You know what - I need to pause for a wind rant. I don't think I've had a single wind rant the entire year.
HOW IS IT POSSIBLE THAT WE STILL DON'T UNDERSTAND THE WIND??? It's been my pet issue for nine (NINE!) years. We play our football games in CHAMPAIGN, ILLINOIS, where the closest hill to disrupt the wind is in Beardstown, and we're in the Big Ten, the windiest wind conference in all of Windville, we practice in the wind every day, and we still don't know what we're doing.
The punt to Carlos Sandy was into the wind. He should have been spending two hours every week practicing with the backup punter, understanding how quickly that ball is going to hit a wall of wind and just die. Does he know that? No. Because we apparently don't address the wind with our punt returners.
So freshman walkon Jordan Holmes gets a shot after Sandy's fumble. And his punt return is with the wind. What does it do? It does what every Big Ten punt with the wind in history has done - drifts high on him. Was he prepared for that very regular occurence? No. I can only assume punt return practice is "go catch that ball - it will just drop out of the sky at the same rate every time since we're in the midwest in the fall and there's no winds". And kickoffs, too. Dre Brown - who was so good today it makes me angry that he's not more of the offense (his heads-up play on the blocked punt saved 7 points) - let a kickoff drift too high on him (WIND!) and fumbled it. He picked it up and returned it... to the six.
There's no way we're prepared for the wind. We play football IN CHAMPAIGN ILLINOIS and we're not prepared for the wind. How is that even possible?
I mean, I've even gone Inception with this issue. I got to interview Lovie Smith and Tim Beckman right after they were hired and I loaded up the question: "Big Ten stadiums are Wind Tunnel USA in the fall - what will you do to teach your players to play in the wind since it's going to be really windy with all the wind?".
It drives me insane where we place our returners. I cannot stand that we don't let the wind direction factor into fourth-down go-for-it decisions. It drives me nuts that the wind is a constant issue, game after game, and everyone acts surprised when it affects us.
I mean, sure, maybe we do emphasize it. Maybe Carlos Sandy and Jordan Holmes are just freshmen and even when you're told "this ball is going to drift on you further than you can possibly imagine", you get out there in front of 80,000 fans and forget everything you're taught.
But it's just so frustrating to see progress (the whole game last week, the offense today) completely undone by mistakes (especially wind-aided mistakes). If this is a hard-fought game, back and forth, and Nebraska wins because they put up 600 yards to our 500 and it's basically a Big 12 game that ends 52-48, fine - we fought hard on the road and lost. But to lose with 5 turnovers and a blocked punt (and all those drops!) - it's just so frustrating.
+ Let's talk about the drops for a second. First, I was worried about drops with Stampley before the season. Here's what I wrote in the big preview:
What about junior college transfer Dominic Stampley? Stampley, who is from Champaign, joined the team just this summer (meaning he didn't sign in February and was a "blueshirt" recruit who joins the team once fall camp starts). Stampley certainly has the quicks (very fast in and out of his cuts), but after several dropped balls during training camp, can the coaching staff count on his hands?
Answer: no, unfortunately. It's something you can correct, and this is just his first year of Big Ten football, but for now, with all these drops, it's hard to count on him.
Which makes me long for Dude K. Do you know what I would give for this offense with Dude K right now? Heck, add Shaedon Meadors to that list. The plan this year was Dudek, Smalling, and Appalachian State's leading receiver from two years ago who transferred here to give Big Ten football a shot (Meadors). He got injured before training camp even began, and Dudek was injured in the first game, and here we are, without receivers we can really trust.
What can you do with that? Honestly, I have no idea. You just have to accept it, I guess. I'm fairly impressed with what Rod Smith has been able to do with the offense given that there's no go-to receivers emerging. It's been done with the run game (even with Epstein out), so it's impressive.
But with two games left, I just don't think there's anything that can be done with the passing game. It's broken and won't be fixed until the offseason.
+ We really do need to pause and talk about the offensive line. I've questioned a lot of things about Luke Butkus over the past few years, but props need to be given. These big runs are constant. RB1 and RB2 are injured and his line produces a big run from Dre Brown and a big run from Ra'Von Bonner. 7.8 yards per rush today a week after 12.3 against Minnesota a week after 6.6 against Maryland a week after 5.8 against Wisconsin. Do it for the fourth game in a row (this time with your third and fourth running back) and props must be given. We can run the damn ball.
If Corbin is out for the rest of the year (let's face it - running back, ankle injury, two games left - he's probably done for the year), and if Epstein does not return, then I don't think we have home run potential anymore. Iowa and Northwestern can both stop the run, so I feel like the running game will grind to a halt these last two games (which means we aren't winning again). But everyone returns next year besides Bush and Allegretti, and I'm excited to see where this running game goes.
+ So, that defense...
Here's what I'll say. These next two games give the opportunity for defensive hope next year. Neither the Iowa offense nor the Northwestern offense are all that explosive. This Nebraska offense was always going to be a challenge, and 5 turnovers basically gives you no chance at all (short fields, "hey defense get back out there we screwed up again"), so let's just burn this film.
Now, Iowa and Northwestern. They're playing right now, as I type this, and the score is 3-0 in the third quarter. Yes, they both have solid defenses. But the both have methodical, the-opposite-of-explosive offenses. Can our defense, designed to stop the more methodical offense, take two big steps the next two weeks?
Because let's face it - those crazy thoughts we had after last week's blowout win (the ones about doing something crazy and making a bowl) are completely gone now. It was just a one week hiatus and now we're back to "oh, right, a defense that needs to be completely overhauled in the offseason". We're going to finish somewhere between 120th and 130th in most defensive statistics, and that's the story of the entire season. A defensive head coach with his worst defense ever.
But the next two weeks, an opportunity. The offense is there and will probably only get better the next two seasons. Now - give us some hope that the defense is going to get somewhere.