Sharp Cheddar 12.02.13

The crew is back from a turkey induced coma to discuss the trauma of being mauled by Lions. We also sing some Sarah McLachlan a cappella. Seriously.

Sharp Cheddar 11.26.13

Brian, Joe, and I discuss the emptiness of tying in the NFL, issue some paddles, and reflect for a moment of thanks.

Mike McCarthy: "Scott Tolzien will start against the New York Giants"

The Packers had just lost their second consecutive home game, falling 27-13 to the Eagles, as coach Mike McCarthy began his post game presser. "I'll tell you right now, Scott Tolzien will start against the New York Giants, so we'll answer that question right here." When prodded, he firmly iterated, "I'm the head coach. I've made that decision."
    Seneca Wallace got virtually all of the practice reps this week with the number one offense, but suffered a groin injury on the first series in Sunday's game. In relief of Wallace, former Badger Scott Tolzien did his best not to shrink in the face of adversity. He completed an impressive 24 of 39 pass attempts (62%) for 280 yards and a touchdown. He did throw two picks, one of which was objectively his fault.
    But this performance must be put into context. Consider that Scott Tolzien was was only activated from the practice squad this past Wednesday. It stands to reason that Tolzien was running on poise, rather than playbook proficiency. In that regard, he was a pleasant surprise. That in mind, McCarthy's insistence is perhaps justified. Tolzien answered the bell objectively stronger than did Seneca Wallace last week, when he faced almost literally an identical set of circumstances.
    The injury bug has forced Ted Thompson's hand, and we'll soon see if free agent QB Matt Flynn—the Packers kicked his tires this week—gets the nod from a medical standpoint. But the immediate future appears to be Tolzien's time.  Wallace's availability is still unclear.

Emergency Pack

In a small metal cupboard hanging on the wall, behind a thin, glass door sits quarterback Matt Flynn. A tiny hammer dangles in wait. Bold, municipal helvetica reads, "IN CASE OF EMERGENCY, BREAK GLASS."
     Internet trolls and sports radio junkies alike are clamoring for the Packers to re-sign their former backup. But it's not just the typical windbaggery of a certain blowhard bunch crying for GM Ted Thompson to "do something!" Flynn is available. The team did meet with him this past week, worked him out, and most certainly quizzed him on his recollection of the playbook.
     Matt Flynn is well traveled since leaving the Packers for starting money, failing to stick in Seattle, Oakland, and Buffalo. It has been reported that he has tendonitis in his throwing elbow. If true, it's no wonder Flynn, known more for football acumen than arm strength, has been ineffective. But passing two physicals in recent months—in Oakland and Buffalo—does bode well for his diagnosis.
     Thus, the Packers are taking a peek. While the team will always fall back on the adage of doing due diligence, taking a mid-season look at a quarterback is an eyebrow-raiser from a staff known widely for their steady-as-she-goes approach.
     The front office won't act, however, unless they don't like what they see this Sunday from current backup, Seneca Wallace. The ball is literally now in Seneca's court. Notwithstanding his Uncle-Rico-esque delivery and lack of physical stature, if Wallace can prove he has the moves and meddle to competently pilot the Pack to an above-.500 record in Rodgers' absence, Flynn will remain a teamless specter. If Wallace baulks or, worse yet, sustains an injury, it is likely that Scott Tolzien would get an opportunity, and that the team would then reach out to Flynn as a possible next man up.

My take? I believe Seneca Wallace is within the top half of backups in the league in two critical categories: experience and poise. He's seen a lot of NFL football. The key for Wallace is to be Alex Smith. Be smart, efficient, consistent. After watching his play against the Bears last Monday, I can't say I feel confident in Seneca's arm strength. The ball is coming out of his hand with considerably less mustard than receivers are used to seeing in Green Bay, which could lead to interceptions. Too many costly turnovers and the dominos with fall. It'll be Tolzien-time and Flynn's agent will get a call. But hopefully, like many of the bridges in Green Bay, the team won't get to cross it.

Sharp Cheddar 9.24.13

This week I had the pleasure of chatting with both Brian and Joe about all things Packers. The tough loss to Cincy, McCarthy's abysmal clutch 4th quarter resume, and Vontaze Burfict's fascination with Ryan Taylor's reproductive health.

Washington Rust-skins Buried 38-20 by Pack

The atmosphere at Lambeau Field was electric. Ionized by 7,500 brand new seats and lit aglow by well over 80,000 total attendees, the Packers struck early and often in what amounted to a route of Washington to the tune of 38-20. Gobs of passing yards, stout defense, and a surprise 100+ yard rusher made this game an all around positive. Let's focus on a few keys.

RB James Starks. Photo: CBS.com

The Running Game: If one had said during the preseason that James Starks, not Eddie Lacy, would be the savior to rid the Packers of the stigma of going 44 straight games without a 100+ yard rusher—The last was Brandon Jackson (seriously) on October 10, 2010 (seriously) to this same Washington football club (seriously)—one might have been labeled insane. Yet it happened. Everyone saw it. On his first carry—a 10 yard gallop— rookie Eddie Lacy was struck hard on the helmet by safety Brandon Meriweather, and forced to exit with a concussion. That would be his only carry. The next man up was James Starks, a guy who quietly took precedence over running back Alex Green in training camp, ultimately winning Green's roster spot. Starks hasn't been a household name for many fans since his 2010 breakout performance and subsequent struggles to stay healthy, but it's clear the coaching staff saw enough in the tall running back to warrant a job. Score one for the coaching staff. On Sunday, Starks was decisive. He was elusive. He cut well and made guys miss, carrying the ball 20 times and rushing for 132 yards. Starks also notched something the team has been sorely lacking, a "big play run" on a 32 yard touchdown scamper.

QB Aaron Rodgers. Photo: NFL.com

Up in The Air: It's been communal wisdom among Green Bay fans that if only the Packers could mount a formidable rushing attack, quarterback Aaron Rodgers would have a field day. Well, with RB James Starks gobbling up an average of 6.6 yards per carry, Washington's already suspect safety group was forced to respect the run. What happened next has become so commonplace in Green Bay, that one almost forgets to highlight its significance. Aaron Rodgers was surgical, completing 34 of 42 passes for 480 yards, 4 touchdowns and no interceptions. The yardage tied a franchise record set, funny enough, by former backup Matt Flynn. On the strength of Rodgers' arm, Green Bay saw 18 of its 28 first downs come via the pass. While they were only 4-10 on 3rd down conversions, the ratio of 28 first downs to just 10 third downs means that the offense was humming efficiently, already a well-oiled machine just two games into the season. Rodgers has 7 touchdowns and 1 interception through those two games.

S Shields. Photo: Roemerphotoblog.com

Sam Shields Was All Over The Place: At some point between defensive snaps in the third quarter, I scribbled the following exclamation in my notebook: "Sam Shields is all over the place!" And indeed he was. The young cornerback was involved on seemingly every clutch stop. Shields led the team with 8 tackles—5 of them solo— and made three pass breakups in textbook fashion, closing on receivers with perfect timing and playing the ball rather than the receiver. Lacking the quality and quantity of receiver that San Francisco enjoys, Washington's wideouts were contained when it mattered against Sam Shields and fellow corner Tramon Williams. They surrendered yardage late, but this secondary was much improved from last week's flop, and Sam Shields was a key cog in that improvement.

More From The Daily Dope Sheet:

See how our pregame keys shook out relative to Sunday's route over Washington

DDS Podcast: First ever podcast! Talking the 49ers loss, Clay's clothesline, and out-of-market fans.

Should Ryan Longwell Be Welcomed Back?

Ryan Longwell kicked for the
Packers for nine years, and holds
multiple franchise records

This week, amid a fierce kicking competition between Mason Crosby and Giorggio Tavecchio, a third kicker was welcomed into Lambeau. Former Packer and holder of virtually all significant franchise kicking records, Ryan Longwell, announced his intention to retire as a Packer. Longwell kicked for the team for nine seasons, and had a golden toe to be sure. Here's a short list of his accomplishments:

• Most made FG's in Packers history: 226
• All time Packers leading scorer: 1054 points

It's relatively common these days for players to sign one-day contracts to retire with their preferred team. But in a game of rivalries, tough love, and hard and fast rules, it could be seen as an empty ceremonial gesture— a bit "warm and fuzzy." 

First, a history lesson: The first player ever to sign a one-day contract was Roger Craig. The phenom 49er ball carrier plowed through the NFC West from 1983 through 1990, then went on to play a year with the Raiders and two with the Vikings. He stated a desire to retire as a 49er, the club where he saw the bulk of his success, and where he set many records which still stand today. Signing a one-day contract allowed him to achieve just that, where he was welcomed back into the fold with open arms. 

Since then, it's become common place for players to do this. As teams become more brand oriented, it also benefits them to rewrite history in the most favorable light for their flag. But shouldn't there be a statute of limitations? A point after which it becomes downright silly to sign a one-day contract?  

Ryan Longwell was an excellent kicker for the Packers for nine seasons. But he then went on to be an excellent kicker for the division-rival Vikings for six more years. After that, he signed with his hometown Seahawks for a playoff run in which they'd lost their kicker to injury. In short, when Longwell left Green Bay, his career was only 56% complete. The average career length in the NFL is said to be about 3 years. Longwell played twice that long and then some for the Vikings and Seahawks. After almost doubling his career length with these other team after Green Bay, is there a spot in Lambeau for Ryan Longwell? Should there be?

I'm soliciting your comments here. Should there be a statute of limitations? If so, how long is it? And do franchise accomplishments outweigh it? Discuss!