Jump to content

  • Welcome!

    Register and log in easily with Twitter or Google accounts!

    Or simply create a new Huddle account. 

    Members receive fewer ads , access our dark theme, and the ability to join the discussion!

     

Has Gettleman finally made a big gaffe?

xtheronx

By xtheronx,
in Carolina Panthers

Recommended Posts

xtheronx Newbie

xtheronx

Posted
Posted

Great article by Newton

http://m.espn.go.com/general/blogs/blogpost?blogname=carolina-panthers&id=5428

"General manager Dave Gettleman has made some questionable decisions in the first week of free agency.

Let's go back to January, two days after the Carolina Panthers finished a 12-4 season, to when Dave Gettleman assessed his first year as an NFL general manager.

"The gaffes I made this year didn’t hurt us too much,'' he said.

A reporter: "Gaffes?''

Gettleman responded with a laugh and a Ric Flair-like "Wooo!," followed by a moment of awkward silence, followed by "let's say I didn't make any big ones.''

Back to the present. Gettleman appears to have made several gaffes a week into his second venture into free agency. Whether one or more turn into big ones remains to be seen. Whether they'll ultimately be called gafffes also remains to be seen because we're a long way from the final snapshot of this team.

But for the sake of evaluation, let's take a look at what could be called the gaffes of the past week:"

Link to comment
Share on other sites
MDPanthersFan Newbie

MDPanthersFan

Posted
Posted

All emotional ties the fans have, whether actually cutting Smith was one or not, to me, isnt as big of a "gaffe" as the timing of it was... why do it when you have no backup plan or replacement already hammered down; why not wait until a vet/replacement receiver is signed and on the books before cutting him (at that point could easily designate him as a June 1st)... there is no way any of the receivers on the active roster can be deemed as replacements for Smith, not even his low production numbers from last season (although his yards were down, he made MANY big time catches).

Aside from that, I tying so much money into Hardy may end up being one. Before flaming me for saying it, think of what could have been done with that cap hit; that could have essentially signed a vet OT and WR. The ravens signed Monroe to a contract averaging 7.5mil a season while Nicks took a deal worth 3.5mil and Ginn something very similar. That isnt to say they would have necessarily signed with Carolina, but the numbers don't lie, two quality players are better than one. Plus, there are a few vet DEnds out there that could have played a single season spot while finding/developing Hardy's spot; worse case you spend a 1st round in 2015 to replacement. As great of a player that Hardy is, he is replaceable.

Link to comment
Share on other sites
IGSaint Newbie

IGSaint

Posted
Posted

Our bread and butter is our pass rush. We couldn't afford to lose Hardy, especially now.

My guess is The Huddle secretly misses Hurney.

This is what it feels like to me. If people are comfortable overpaying mediocre players why did hurney even leave? 

Link to comment
Share on other sites
Ruff Newbie

Ruff

Posted
Posted

Our bread and butter is our pass rush. We couldn't afford to lose Hardy, especially now.

My guess is The Huddle secretly misses Hurney.

Pass rush is generally created from the inside out in a 43 defense. We have the talent on the inside to free up the guys on the outside. At least, enough to where we don't have to spend 60% of our cap space on that position.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • PMH4OWPW7JD2TDGWZKTOYL2T3E.jpg

  • Topics

  • Posts

    • PanthersATL
      NFL admits the TMac catch should not have been overturned

      By PanthersATL · Posted

      They said there wasn't clear evidence to warrant the overturn.  How would it have made a difference at that point in the game?   https://www.nbcsports.com/nfl/profootballtalk/rumor-mill/news/nfl-privately-admitted-to-erroneous-reversal-of-catch-by-panthers
    • Khyber53
      WWE pay per view and programming thread

      By Khyber53 · Posted

      Me, I'm sick of WWE channel hopping their PLEs and shows. Netflix now with Raw. USA still has Smackdown but you can't get it with Roku if you don't also have cable. Then they went from all the PLEs on Peacock to ESPN+ which required upgrading your Disney+ package. Then they frikkin' move Saturday Night Main Event with John Cena's retirement match back over to frikkin' Peacock, which we'd just cancelled two months prior because no PLEs there anymore. And there are fewer, but longer matches and its the same danged stories again and again. Rematch after rematch after rematch between PLEs. Fewer matches, fewer wrestlers, more promos (of lesser quality) and less action.  It just seems like it's all fillers and re-runs. I'm tired of Cody Rhodes. I'm tired of Jey Uso. I'm tired of the two Brons. Shuffle the deck a bit guys, this game's getting stale.
    • CPantherKing
      Going for it instead of leading by two scores in the 4th

      By CPantherKing · Posted

      Chuba was 3 yards behind the 3 gap. He was lined up weak offset I. It was a 33 dive. Chuba needed to power through off of Ekwonu's block and slip off into the 5 gap where the Tremble had the lane sealed and Rick pulled the LB out of the 5 gap. Here's a visual if you need proof. Chuba did a jump cut laterally to the 2 gap on the right side with unblocked defenders crashing down and went airborne.   This is a 33 dive that should have been slipped off the block into the 5 gap. Chuba lacked vision, but you can see Rico and Bryce staring at the intended running lane sealed off by Tremble and Ekwonu. He should have read Ekwonu's block. The blocking and misdirection is NOT set up for the right side. The play worked. Chuba failed to execute on this play. Trust who you want to, but I wouldn't suggest you argue with the video. Anyone telling you this was drawn up to go right with the blocking did not analyze it. They are correct it should have been a called dive, and it was a called dive.  This was a weak offset I bringing Tremble in motion from the right to the left.
×
×
  • Create New...