Sunday, September 20

Cluck

So here's what we learned: Cougars can lay eggs.

I didn't watch the entire game. (It was too painful.) But it was clear that BYU was simply not ready to play, at least not to the same degree that Florida State was, particularly when FSU had the ball. They ran everywhere they wanted to, and BYU didn't stop them. After not allowing a play over 20 yards in either of the first two games, BYU continually hemorrhaged yards all over the field in big chunks. It was disappointing. But it provides a good opportunity to discuss an important aspect of college football: luck and timing.

I'd still bet on BYU to beat FSU. Through a 12 game season, a team is going to play poorly at some point. The key is getting those games to align with your crummiest opponents. I don't know how you can do that, but if you do, you get a special season. If BYU had played FSU last week, and Tulane this week, they might well be undefeated still. But they didn't and they aren't. BYU beat OU, and made their heisman winning QB look just ok. They made his backup look very mediocre. That backup threw 6 TDs against Tulsa this weekend as OU destroyed them 48-0 or whatever it was. If OU had played that game vs BYU and played their BYU game vs Tulsa, they would still be undefeated and ranked in the top 3 still. The point is, in college football you must be both good and lucky.

One more point: Chambers needs to get smacked upside the head, and hard. I'm tired of watching him (and anyone else) strut around on the field after an 8 yard completion, particularly when he's got 2 costly fumbles already this season. For the most part, no one should be strutting at all on a football field, but if you are going to do it, you'd better be darn sure that you are actually helping your team win. He did it last year, too, when his main role was #4 receiver and #2 punt returner. Now that he's been up graded to #3 receiver, he's still doing it. Someone (anyone) needs to pull him aside and let him know that he looks ridiculous.

Sunday, September 13

Stats

I was only able to watch about 1 quarter of the BYU game today. (The second quarter.) Tulane isn't exactly a terrific team or anything, but there were a couple of stats that jumped out at me from the game:
  • 0: Zero punts. On 10 offensive possessions BYU had 2 field goals, 6 touchdowns, an interception and a turn over on downs. That's pretty efficient football. (Of course, that took our best kicker out of the game, it seems. For the second game in a row, we had a kickoff out of bounds (how hard it is to keep it in bounds? the field is like 30 yards wide) and Payne missed a PAT.)
  • 6/9: Third down conversions. 67% is pretty darn good, but that isn't really the number that piqued my interest. The interesting number: 9. BYU only had 9 3rd downs all game long. 79 plays in the game and all but 67 of them were either 1st or 2nd down. It's a good thing when your offense doesn't need 3 tries to get a first down.
  • 16: Players that gained yardage for BYU. Sure, it helps that it was a blowout and everyone got in on the action, but on 26 completions no one caught more than 4 balls, and 45 runs were split up between 10 players with no one getting more than 12 carries. 9 players averaged 3.5 yards per carry or more.
Yeah, its true, playing a team like Tulane will always help you put up big stats, but it's still not every day you see numbers like these. (Note: I am not arguing that a team that has 9 players averaging 3.5+ yards per carry is somehow better than a team that has one back carry it 30 times. I'm mostly just interested in these stats as statistical anomolies.) But while we're here, lets compare some other teams on the winning ends of blowouts:

Florida (56-6 over Troy): 3 punts, 10/14 3rd downs, 6 players 3.5+ ypc
Oklahoma (64-0 over Idaho State): 4 punts, 4/13 3rd downs, 4 players 3.5+ ypc.
Cincinnati (70-3 over Southeast Missouri State): 4 punts, 7/12 3rd downs, 6 players 3.5+ ypc.

Ok, I'm done.

Monday, September 7

Eruptions

For labor day, we went to Bryce Canyon to do some hiking. Bryce is about 2 1/2 hours away, though we didn't really get a good estimate of how long it really takes. We were about 2 hours into the trip up there, when suddenly, from the back seat, there was an eruption. And then everything was covered in barf. (Anyone who might have come with us: be glad you didn't. We might have been tempted to carpool and then you would have been in the kill-zone.) Turns out the yogurt for breakfast did not agree with Julia at all. So, we got every parent's delight: wiping things down on the side of the road with wet-wipes. Once we were about cleaned up, a family was nice enough to stop and ask if we needed any help. There really wasn't much they could do for us, but we appreciated their willingness. Thank you family of strangers! (Though it would be a real long shot, we should have asked if they had any febreeze in their truck!)

So, we made it to Bryce and went on the Navaho/Peekaboo loops. 4.9 miles total. Not sure how long it took us, because we didn't reliably look at a clock the whole day. Anyway, the weather was nice, in the 70s, and there was often a breeze. Bryce is a fantastic place, because it has large, grand views, but you can also go hiking down through all of it and experience it up close, and away from crowds. We also learned that 4.5 miles is about my limit for toating Julia on my back. We'll see how the shoulder feels tomorrow.

We managed the trip back without any eruptions. Instead we got a 30 minute backup on the freeway from an accident.

Sunday, September 6


Wow. It's been 12 hours, and it's still sinking in. BYU beat #3 Oklahoma on a not-quite-neutral field. Wow.
  • BYUs defense was the best unit on the field througout pretty much the entire game. Better than either offense, and better than OUs defense.
  • Replacing 4 offensive linemen, having a top offensive player out with an injury and losing another important player to injury in the first half might might be a decent excuse for losing a game. But it's real hard to make that arguement when it applies to both teams. There simply isn't any ground to say that any one play was the game breaker. OU lost their starting QB. BYU turned the ball over 4 times. (The muffed punt was particularly eggregious.) Both teams got called for pass interference in the endzone. (The call against BYU was pretty iffy in my opinion.) Both teams picked up lots of penalties and did it in bad spots on occasion. (OU kept putting themselves in 3rd and long situations from their O-line, and BYU essentially put OUs final drive together for them with a kick out of bounds, a face mask and a late hit (if I remember that correctly)). In short, it looked like the first game of the season.
  • I found it particularly interesting that in the second half both teams moved the ball down to about the 5 yard line, ran a few plays, got a PI call in the end zone, started fresh at the 2 yard line, and then was called for a false start. BYU got a touchdown, OU didn't.
  • The final BYU drive of 16 plays, 78 yards and 8:44 was really impressive. I was most worried for our chances at the opening kickoff, and then again near the end of the 3rd quarter. In the 3rd quarter the OU O-line and D-line seemed to be wearing down BYU, which happens so often in big games. I feared BYU would run out of gas and a bigger, faster and more talented OU team would finally push by them and win pulling away. Instead, BYU ate up most of the 4th quarter on a great drive.
  • Speaking of drives, OUs 3 longest drives were 52, 43 and 35 yards. BYU put together drives of 78, 63 and 59 yards.

Thursday, September 3

Football

College football has started, and I'm watching Utah/USU online. Thank goodness for people streaming things! Unfortunately, the game is on the mountain. The mountain has been around for a number of years now, and for every one of those years, they've had the same flaw in their on-screen game clock. In the final minute of a quarter, the clock shows 39:04 when it ought to show 39.4. So I have to sit there watching the clock tick down: 39:04, 39:03, 39:02, 39:01, 39:00, 38:09, etc. I understand how the error could be made, but I don't understand how it can be allowed to stand for years, when it ought to be simple to fix. So, either no one at the station is paying enough attention to notice, or no one cares enough to display a time that makes sense, or maybe no one can figure out how to fix it.

Wednesday, September 2

Total Eclipse. Literally.

I find that I'm usually the last person in the world to catch on to the latest cool youtube video. The people dancing down the aisle at their wedding, yeah, I was dead last. 70-year-old grandmas had it in their facebook status before it worked its way to me. Apparently I live on an island or something. Anyway, the following video only has 3.6 million views on youtube, so at least 90% of the country hasn't seen it. (Whether any of that 90% reads my blog is, of course, another question.)

The idea here is that what you are seeing in music videos doesn't always correlate well with the lyrics. So, people have been creating 'literal versions' of music videos, where the lyrics have been adjusted to represent whatever you're watching. There are a whole lot of them on youtube, with a wide range of quality. The vocal talents of the re-recordings are severely lacking on some of the videos, and obviously some videos are better suited to the project to begin with. But here is the best one that I'm aware of out there. The lyrics are on the screen so you can sing along! Well, without futher ado (thanks for laboring through all that ado!) I present the literal version of Total Eclipse of the Heart.