Carter looking for growth
by Andy Little
The stage has been set for Drew Carter. The Carolina Panthers parted ways with starting wide receiver Keyshawn Johnson in part because they wanted to get younger at the position. They drafted Dwayne Jarrett in the second round to potentially replace what Johnson leaves behind, but Jarrett will first have to make the coaching staff take their eyes off Carter for the spot opposite Steve Smith.
Carter is going into his fourth year on the team in a good position. He now has a lot of experience in this system and with starting QB Jake Delhomme. Last season he was supposed to share the third wide receiver position with Keary Colbert depending on the play called but ended up getting most of the time there. He had 28 catches for 357 yards receiving last year and signed a one year contract worth $1.3 million for the upcoming season. He is also going into this season in great shape after a hard offseason conditioning program.
“It’s good to get back into it. We just finished a hard offseason program. I love this. I love practicing and this is what you work hard for and train for. This is the fun part,” said Carter after a hard morning workout.
Carter has the kind of attitude the coaching staff wants. He is willing to do whatever is asked of him and is positive. While not a leader in the sense that Jake Delhomme or Steve Smith is, he is well liked and ready to take a greater role in this offense. New offensive coordinator Jeff Davidson will play a big part in deciding what role he has this season, and Carter is already a fan.
“We have a lot of different formations and different things. A lot of the language is the same but he’s (Davidson) coming in with his own style. It’s a good adjustment,” said Carter.
If Carter keeps working hard in this offense, then he could find himself adjusting well to a solid starting wide receiver opposite Steve Smith on opening day.
Comments
This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.