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!

     

R.R. defends Bell & Chandler at presser


Jmac

Recommended Posts

Per J.Person. "They where playing well before injuries". Take it for what it's worth. I thought Chandler had a chance to improve after camp but he hasn't and Bell is Bell. Maybe he should ask Cam about how well they have been playing.

Link to comment
Share on other sites

I don't get you guys. We have no backup tackles and can't afford to get a good one. Do you expect him to keep shitting on them in pressers? What is that going to achieve? It will do nothing but break the teams morale. You put a brave face on it and when you have options you move on.

Link to comment
Share on other sites

Wow. I don't know what to say. All I know is that as a manager, if I don't bold my team accountable, at some point I will be held accountable. I hope that holds true in this case as well.

You don't fire a staff member without an adequate replacement. That's bad management. Also you don't continually deride an employee for bad performance. None of us would enjoy working for a boss who is telling us everyday we suck.

Link to comment
Share on other sites

These isn"t pee wee league football. Grown men making mega bucks that should be held accountable. At least don't BS and try to hide the obvious and say they are playing well....how about maybe "room for improvememt?

Link to comment
Share on other sites

You don't fire a staff member without an adequate replacement. That's bad management. Also you don't continually deride an employee for bad performance. None of us would enjoy working for a boss who is telling us everyday we suck.

 

This isn't some office job. Even these UDFA's are paid hundreds of thousands of dollars to play this game. The "he's a nice guy though" reasoning for keeping clearly underperforming players around is a big part of why we've never had back to back winning seasons before.

Link to comment
Share on other sites

"KB needed to make that catch" - everyone flips out about calling him out.

"Bell and Chandler are being hampered by injuries and we have no back ups" - unacceptable to stand up for them.

 

Ron can only do so much with what he has... Dave can only get so many players at a time... Players can only be so good... Coaches can only teach so much. We are what we are.

Link to comment
Share on other sites

Someone mentioned lining the TEs up in the backfield on obvious pass situations. What about Chandler? He is supposed to be super athletic for his size and obviously isn't a stranger to position changes. Why not line him up back there for pass protection or even as a normal fullback? Other than screens we aren't using the backs a safety valves anyways.

Link to comment
Share on other sites

Archived

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


  • PMH4OWPW7JD2TDGWZKTOYL2T3E.jpg

  • Topics

  • Posts

    • In the past 7 years we wouldn’t have had to TBH. We would have been better off realizing we lost Cam, Luke and many others. It was time to do an actual rebuild and save the cap space so we could keep our “good” (huddle consensus) draft picks like extending Trey Smith and Creed Humphrey instead of having cap space to burn since the long snapper and TMJ didn’t work out. Also, have enough cap space to keep some offensive weapons like CMC and Moore because we don’t have to trade up for a QB or didn’t have to “recover” picks lost in poo trades. One other note here is that, the consensus huddle would have jumped at the chance to get two 1sts and a 2nd for Burns. That alone would have been the best FA/trade move made in the history of the Panthers. It is 100% indisputable fact that a huddle consensus GM, from 2018 to 2024, would have done way better and we’d have a playoff contender right now. Maybe not a SB/NFC winning team but likely the best team in the NFC South rather than a hey we lost close games to the teams in the SB even though our D set a single season points allowed record.
    • https://philpeople.org/profiles/coinbase-wallet-support-how-do-i-connect-to-coinbase-support-faqs-support-guide https://philpeople.org/profiles/coinbase-wallet-support-how-do-i-connect-to-coinbase-support-faqs-support-guide https://philpeople.org/profiles/coinbase-wallet-support-how-do-i-connect-to-coinbase-support-faqs-support-guide https://philpeople.org/profiles/coinbase-wallet-support-how-do-i-connect-to-coinbase-support-faqs-support-guide
    • 🛠️☎️How Do I Contact QB Error Support Number?   For assistance with QuickBooks Error you can contact their support team at 1.833.677.8666 or 1.833*677*8666 𝐨𝐫 1.833.6INTUIT. They are available to help with any questions or issues you may have regarding enterprise solutions and complex business needs.   ➡𝐅𝐨𝐫 𝐡𝐞𝐥𝐩 𝐰𝐢𝐭𝐡 𝐐𝐮𝐢𝐜𝐤𝐁𝐨𝐨𝐤𝐬 Error Support, 𝐫𝐞𝐚𝐜𝐡 𝐨𝐮𝐭 𝐭𝐨 𝐨𝐮𝐫 𝐬𝐮𝐩𝐩𝐨𝐫𝐭 𝐭𝐞𝐚𝐦 𝐚𝐧𝐲𝐭𝐢𝐦𝐞 𝐚𝐭 (1.833.677.8666) or (1.833.677.8666). 𝐖𝐞'𝐫𝐞 𝐚𝐯𝐚𝐢𝐥𝐚𝐛𝐥𝐞 𝟸𝟺/𝟽 𝐭𝐨 𝐚𝐬𝐬𝐢𝐬𝐭 𝐰𝐢𝐭𝐡 𝐢𝐧𝐬𝐭𝐚𝐥𝐥𝐚𝐭𝐢𝐨𝐧, 𝐬𝐞𝐭𝐮𝐩, 𝐚𝐧𝐝 𝐭𝐫𝐨𝐮𝐛𝐥𝐞𝐬𝐡𝐨𝐨𝐭𝐢𝐧𝐠.   ➡𝐅𝐨𝐫 𝐡𝐞𝐥𝐩 𝐰𝐢𝐭𝐡 𝐐𝐮𝐢𝐜𝐤𝐁𝐨𝐨𝐤𝐬 Error, 𝐫𝐞𝐚𝐜𝐡 𝐨𝐮𝐭 𝐭𝐨 𝐨𝐮𝐫 𝐬𝐮𝐩𝐩𝐨𝐫𝐭 𝐭𝐞𝐚𝐦 𝐚𝐧𝐲𝐭𝐢𝐦𝐞 𝐚𝐭 1.833.677.8666 or 1.833*677*8666 𝐨𝐫 1.833.6INTUIT. 𝐖𝐞’𝐫𝐞 𝐚𝐯𝐚𝐢𝐥𝐚𝐛𝐥𝐞 𝟸𝟼/𝟽 𝐭𝐨 𝐚𝐬𝐬𝐢𝐬𝐭 𝐰𝐢𝐭𝐡 𝐢𝐧𝐬𝐭𝐚𝐥𝐥𝐚𝐭𝐢𝐨𝐧, 𝐬𝐞𝐭𝐮𝐩, 𝐚𝐧𝐝 𝐭𝐫𝐨𝐮𝐛𝐥𝐞𝐬𝐡𝐨𝐨𝐭𝐢𝐧𝐠.   https://odoedev.powerappsportals.us/en-US/forums/chd-discussion/a5bcaa42-56f0-ef11-a4de-001dd806be05 https://odoedev.powerappsportals.us/en-US/forums/chd-discussion/a5bcaa42-56f0-ef11-a4de-001dd806be05 https://odoedev.powerappsportals.us/en-US/forums/chd-discussion/a5bcaa42-56f0-ef11-a4de-001dd806be05 https://odoedev.powerappsportals.us/en-US/forums/chd-discussion/a5bcaa42-56f0-ef11-a4de-001dd806be05 https://odoedev.powerappsportals.us/en-US/forums/chd-discussion/a5bcaa42-56f0-ef11-a4de-001dd806be05 https://odoedev.powerappsportals.us/en-US/forums/chd-discussion/a5bcaa42-56f0-ef11-a4de-001dd806be05 https://odoedev.powerappsportals.us/en-US/forums/chd-discussion/a5bcaa42-56f0-ef11-a4de-001dd806be05 https://odoedev.powerappsportals.us/en-US/forums/chd-discussion/a5bcaa42-56f0-ef11-a4de-001dd806be05
×
×
  • Create New...