Ten Takeaways: Week Two
An unexpected week of chaos.
For those reading on e-mail: click 'view in browser' to see the full contents of today's post
Ten Takeaways: Week Two
For my Ohio State subscribers, check out Bulletpoints to see my full thoughts on the Buckeyes' 70-0 win over Grambling:
Colton Denning
1. This computer needs a reset
I can't remember a wonkier start to the season. We haven't had any truly shocking upsets –so don't let people do the, "IT FEELS LIKE 2007 IN HERE!" bit– but there've been so many odd results and storylines that it's like someone uploaded the season with a virus attached to it. I can't put my finger on exactly why that is, either.
The portal's probably the most obvious answer. The ability to morph your whole roster into something completely different in less than nine months adds a level of variance and randomness to these teams, especially in the first few weeks of the season. Whatever's causing it, I'm not sure I've ever seen it to this degree early in a season before.
Enjoy the rest of the season with a 2StripesCPD subscription 👇
2. There's no such thing as a bad week
Every time the general consensus is that the upcoming week of games will suck, it turns out to be the complete opposite. I'm not immune to that, either. I looked at week two and thought, "Boy, that's rough." But instead of a forgettable Saturday, we got:
- Mississippi State upsetting No. 12 Arizona State thanks to a last-minute TD
- USF walking into The Swamp and putting a critical hit on the Billy Napier era.
- An instant classic between Baylor and SMU that may save Dave Aranda while leaving SMU reeling.
- Kansas and Missouri doing justice to the first Border War in 14 years with a banger of a shootout.
- Army throwing Kansas State's season into further disarray, plus a host of other exciting games no one really had on their radar.
Repeat after me: There's never a bad week of college football.
