When I wrote The Friday Five last week, I asked for suggestions on how I could make the column better, and I was presented with a few great ideas that I'm going to implement moving forward. The first one I'm going to utilize is the suggestion made by Vagus, which involves me doing a follow-up piece on what went right and/or wrong with my predictions.
Normally this would be a combination of "what went wrong" followed by a section of "I told you so" that would allow me to gloat about my infinite wisdom, but honestly I don't have that much to "tell you so" about after this week's game, so that section's going to be a little short this week. With that being said, I'm primarily going to cover how off-base some of my predictions were, and if you're so inclined to find out how wrong I was, feel free to join me after the jump.
(Note: This was also a suggestion from Vagus, as you all know the Grammar Nazi in me would never come up with something so grotesque on my own. But, I kinda like it, so I'm going to stick with it, for now.)
I'm sure you know what the "mostliest wrongliest" of this week is going to be, but in the spirit of fairness I will still own up to what I said that was so far off base.
When talking about Cam Newton's possible performance against the Cardinals, I said the following:
What to expect: Simply put -- a rookie QB in his first career start. There will be growing pains, and this week will be no exception. Cam's going to struggle with consistency, as every rookie QB does. I don't think he will be as horrendous as the QB play we saw in 2010, but I'm also not getting my hopes up that he's going to be Aaron Rodgers out there.
Okay, you don't have to be a brain surgeon to figure out how wrong I was on this one. I will admit that never in my wildest dreams did I think that Cam Newton would be as...as dynamic as he was on Sunday. He was absolutely scintillating out there against the Cardinals, and I have never been happier to be so wrong in my life.
However, in my defense, he wasn't Aaron Rodgers on Sunday. He was better than Aaron Rodgers. And Drew Brees. And every other QB in the league not named Tom Brady. And I loved it. (And you know you did too.)
Not Too Far Off
There were a few predictions I made that were wrong and still deserve to be mentioned, even though they weren't that far off base.
First, I said the DT's would be abused all afternoon. Even though they weren't spectacular, they weren't beaten as bad as I said they would be, and like my horrible Cam Newton prediction above, I'm glad that I was wrong on this one. We still need help at the DT position simply because we can't rely on three people at that position all season long, but the three guys we had did fairly well throughout the game.
Second, I predicted that Armanti Edwards would step up and take the #2 WR position. Well, he didn't do that, but someone else did. Brandon LaFell stepped up in a big way on Sunday, grabbing 4 receptions for 70 yards in an impressive effort.
Finally, I predicted that Jon Beason would force a turnover. Unfortunately, Beason wasn't able to do that, and even more unfortunately he was lost for the season when he blew his Achilles chasing down former Panthers TE Jeff King on a blown coverage that led to the Cardinals' second touchdown of the day.
I Told You So
Admittedly this one is a stretch, but I have to gloat about something. I predicted the Panthers would lose 31-24. While the final score was 28-21, the Panthers still lost by a touchdown (which I predicted), and if you listened to last week's recording of CSR Radio, I also said that Patrick Peterson would beat us with a punt return for a touchdown. Okay, I'll admit -- I was halfway joking when I said that, but it still happened. (I have to take all the opportunities to gloat that I can get, because honestly I'm not going to be able to fill the "I told you so" section of this recap very often, so cut me some slack here.)
Well, there you have it folks. I think I did pretty good for my first time using the old crystal ball. Hopefully next week I won't be so far off base with my predictions though, because I'll admit that I enjoyed typing the "I told you so" section the most of the three.
Be sure to stay tuned on Friday for this weeks' edition of The Friday Five, and be on the lookout next Tuesday for The Friday Five Recap, where I hopefully have more gloating to do.