Play Fantasy Use your Fantasy skills to win Cash Prizes. Join or start a league today. Play Now
 
Tag:Jerome Harrison
Posted on: October 13, 2010 2:47 pm
Edited on: October 13, 2010 4:08 pm
 

Browns trade Harrison to Eagles for Bell

Posted by Will Brinson

It's been mentioned once or twice here that Jerome Harrison probably isn't Eric Mangini's favorite player -- that won't matter anymore Harrison has been traded from the Browns in exchange for running back Mike Bell, the Eagles announced on Wednesday.

The news, first reported by FOX's Jay Glazer, is surprising in that it's a straight RB-for-RB swap, but probably works out for both teams.

Harrison, who put up monster numbers at the end of last year, has been in Mangini's doghouse, so the deal makes sense for the Browns -- they add to their running back depth and get rid of a player the coaching staff either a) doesn't appreciate, b) considers a malcontent or c) both.

For the Eagles, it's a logical move as they improve the quality of their running backs overall by grabbing a better change-of-pace back for the suddenly-quite-physical LeSean McCoy.

For more NFL news, rumors and analysis, follow  @cbssportsnfl on Twitter and subscribe to our RSS Feed
Posted on: October 7, 2010 10:55 pm
 

Mangini swears he doesn't hate Jerome Harrison

Posted by Will Brinson

If you've watched a Browns game this year (and/or read anything I've written about Cleveland's running game), there's a distinct chance that you could think Jerome Harrison is currently holding Eric Mangini's family hostage in his basement, Breaking Bad style.

Now, frankly, Peyton Hillis has justified the carries he's been given for the past few weeks, so it's kind of hard to hate on Mangini's decision, but it's at least reasonable to wonder if he dislikes Harrison. Thankfully, someone asked, via Stephanie Storm at the Akron Beacon-Journalposed the old "Is Jerome Harrison in your doghouse?" question.

"No, not at all," Mangini said. "He'll probably have some opportunities this week and every week is different. No, that's not the case at all."

However, considering that most of Harrison's carries either don't exist or are in the worst possible field position imaginable, that's not necessarily a good thing.

And, according to Mangini, even though Harrison came out and publicly mentioned something sarcastic about his "role" in the offense, the two still haven't had "any talks or anything, but [Mangini] is always open to that."

So, to sum up, we've got a running back making public statements about not getting enough carries, followed by a coach who says said running back is not in the doghouse even though he'll probably get the "same" carries in the coming weeks -- regardless of the fact that he rushed for a season's worth of yardage in three games last year and the other running back on the roster is banged up -- and there is NOTHING WRONG WITH THIS SO STOP ASKING QUESTIONS.
Posted on: October 5, 2010 10:14 am
Edited on: October 5, 2010 6:41 pm
 

Top Ten With a Twist: Curse of Wally Pipp

P. Hillis has taken over the Cleveland running game (US Presswire).

Posted by Josh Katzowitz

We’re a quarter of the way into the season, and some players who were originally slated to be backups suddenly have emerged as starters. Maybe it was through an injury to the former starter. Maybe it was because the starter wasn’t as good as the team thought and the backup was better. Maybe it was because – and Wally Pipp could relate to this – somebody just needed an off-day.

In fairness to the old-time Yankees first baseman, who was replaced one day (permanently, it turned out) in 1925 by a guy named Lou Gehrig because Pipp had a headache, that story might not be true exactly. Instead, he might have been benched because manager Miller Huggins simply wanted to shake up the lineup. Either way, Gehrig played the next 2,130 games, and Pipp ended up in … Cincinnati (and apparently, he was also one of Sports Illustrated’s first writing hires, one of those cool but useless facts).

Anyway, there have been some impact players to emerge this season so far, simply because they, like Gehrig, were given that chance to shine. Some have won a starting position. Some are just holding it until the real starter returns. But they’re all making a (mostly good) impression. It sounds like the perfect Top Ten With a Twist list to me.

10. Lance Moore, WR/PR, Saints: The story of Moore’s career. A Saints starts gets injured. Moore steps in and makes plays. Remember in 2008 when Moore caught a team-high 79 passes for 928 yards and 10 touchdowns after Marques Colston was hurt? Obviously, when Reggie Bush returns from his broken leg, Moore will fade back into the background – maybe. But man, he looked electric against the Falcons (six catches, 149 yards, two touchdowns), and he’s become a big target for New Orleans when it’s in the red zone.

9. Max Hall, QB, Cardinals: Look, we all know Derek Anderson isn’t a very good quarterback. But I didn’t think he would have a chance to lose his job this early. Hall, meanwhile, was a 2010 undrafted free agent (seriously, how poor is Anderson to lose to an undrafted free agent?). Not that Hall was great when he replaced Anderson on Sunday, because he wasn’t, but he might be Arizona’s best option at this point. Coach Ken Whisenhunt, meanwhile, isn’t talking. “I think we're going to go without [a quarterback) this week,” he joked Monday. “I think we're going to go with all Wildcat."

8. BenJarvus Green-Ellis, RB, Patriots: He averaged about eight carries per game his rookie year in 2008, but with Kevin Faulk lost for the season – and Fred Taylor unavailable for the Miami game Monday – Green-Ellis (47 carries this year for 215 yards) has already nearly doubled his attempts from last year. He had his breakout in Week 3 against Buffalo when he carried the ball 16 times for 98 yards and a score, and vs. the Dolphins, he was impressive with a 16-carry, 78-yard, one-touchdown performance.

7. Shaun Hill, QB, Lions:
The reason Hill is so low on this list is because there’s no way he’ll take the job from Matthew Stafford. But still, how impressive has Hill looked the past few weeks? After Stafford went out with the shoulder injury in Week 1, Hill was terrible. But the past three weeks, he’s completed 61.9 percent of his passes for five touchdowns and six interceptions (he’s also averaging 301 passing yards per game), and he really impressed me in Detroit’s two-point loss to Green Bay.

6. Bruce Gradkowski, QB, Raiders: It didn’t take long for Raiders coach Tom Cable to figure out that, in order to save his job, he’d take his chances with Gradkowski instead of Jason Campbell. This is not to say Gradkowski is an elite quarterback, because that’s a laughable notion. But he played well at times when he was in Tampa Bay after Chris Simms ruptured his spleen in 2006 (Gradkowski failed to win the starting job in 2007). For now, though, Gradkowski is entrenched as Cable’s guy. As long as Cable is around.

5. Koa Misi, LB, Dolphins: Ikaika Alama-Francis was supposed to be the starter, but the night before the season opener, he caught some kind of illness and he’s been recovering ever since, losing 15-20 pounds in the process. Misi, the team’s second round Draft pick this year, has taken over his starting spot with consistent play and a smooth transition to the pro game. It was originally thought that Misi’s main objective would be as a situational pass-rusher – he was, after all, a defensive end in college – but he’s proven his worth as an every-down back with two sacks and a fumble recovery TD. In the meantime, he’s also Wally Pipp’d Alama-Francis.

4. Taylor Mays, S, 49ers: Mays so Wally Pipp’d former starter Michael Lewis that San Francisco released Lewis Monday, the day after Mays’ huge game against Atlanta. Mays had taken Lewis’ starting job already, and it sounds like Lewis asked for his release, but still, that’s pretty impressive for a rookie. Mays, in case you didn’t see it, had a phenomenal touchdown (both feet down!) after a punt block to give San Francisco a 14-0 lead. He also made 11 tackles.



3. John Carney, K, Saints: Carney, who will turn 65 later this year (I’m kidding, he’s 46), has returned once again to the NFL, and after making three kicks this past week, you have to wonder how much longer Garrett Hartley will stay on the roster – or why he’s on the roster at all at this point. Obviously, Carney isn’t the future kicker in this organization, and maybe the Saints are keeping Hartley around, because they’re hoping he can overcome what’s been a terrible start to the season for him. Otherwise, he’d already have been Pipp’d.

2. Ryan Torain, RB, Redskins:
Torain and Clinton Portis have split carries, but it seems that if this was the 100-meter dash at the Olympics, Torain would be Usain Bolt and Portis would be the other seven guys. Meaning Torain is pulling away and eventually will take Portis’ starting role. It could happen this week actually as Portis hurt his groin Sunday. Let me also briefly mention San Diego’s Mike Tolbert, who replaced first-round pick Ryan Mathews when he was injured and rushed for 255 combined yards the past three games (including a 100-yard performance Sunday when Mathews was in the game). But coach Norv Turner says he’s committed to keeping Mathews as the starter, so Tolbert doesn’t fit on this list all that well.

1. Peyton Hillis, RB, Browns: It was supposed to be Montario Hardesty and Jerome Harrison running the ball in Cleveland. Hillis – who was traded from Denver in the Brady Quinn deal this past offseason – was supposed to be just an afterthought. Baltimore’s Terrell Suggs had never heard of the guy until he ripped off 180 total yards (144 on the ground, the most Baltimore has allowed in five years) against the Ravens. With Hardesty out with a season-ending injury and with Harrison failing to make an impression on the Cleveland coaching staff, Hillis has taken advantage, tying the league high with four touchdowns and averaging 4.9 yards per carry. Like Gehrig, it appears that Hillis has no future plans to give up his starting spot.

For more NFL news, rumors and analysis, follow @cbssportsnfl on Twitter and subscribe to our RSS Feed .


Posted on: September 28, 2010 2:52 pm
Edited on: September 28, 2010 4:19 pm
 

Dey Took Er Jobs: Wither Trent Edwards?

Dey Took Er Jobs takes a look at the various job controversies around the league. If you don't get the title, you don't watch enough South Park .

Posted by Will Brinson


The Buffalo Bills, probably the most quarterback-desperate team in the NFL over the past 10 or so years, made the surprising decision to cut Trent Edwards yesterday. He is jobless and homeless right now, but -- thank goodness for that Stanford education! -- certainly not unemployable.

Still, don't feel that sorry for him. After all, by 4:00 PM EST today, when the NFL process all the waiver claims on Edwards , he's going to have a new job and it will likely be in a place that is less like Buffalo potentially more productive for his future.

That's the beauty of getting kicked out of Buffalo: the grass is always greener, even once you've been on the other side for 10 years. Of course, if you're Edwards, you have to be disappointed that the gig didn't work out -- after all, he was drafted by the Bills out of Stanford and given plenty of opportunities to win the starting job and resurrect the franchise. Clearly, that didn't happen.

So knowing that he'll end up somewhere, the question becomes "Where does he get his second chance?"

According to the NFL, the teams with the worst record this year will have priority on waiver claims, and assuming that multiple teams with the same record make a claim on Edwards, a tie will be broken "based on current strength-of-schedule of the involved clubs or by lot if a tie still exists."

Let's say that all the 0-3 teams make a claim as well as the Vikings, Seahawks and Jets. The order would be thus: 49ers/Browns (7-2 opponent record), Lions/Bills (6-3), Panthers (5-4), Jaguars (4-5), Vikings (4-5), Jets (6-3) and Seahawks (2-7).

According to Jason LaCanfora , though, "no winless teams" made a claim on Edwards, thereby eliminating six teams from consideration and wasting about 15 minutes of my time, primarily because I'm horribly bad at math.

Out of those teams, the 49ers are most surprising (see below), but, considering that LaCanfora has a knack for being correct and also happens to work for a media outlet owned by the organization who takes the waiver claims in from the teams, it seems that one fo the 26 other squads will be going after the former team captain in Buffalo.

The Vikings haven't been rumored insofar as I can tell but they still make sense, especially if you buy into the theory that Brett Favre might get hurt. (Oh, and the theory that everyone's scared of having to put Tavaris Jackson into the game.)

The Jets are considered a team that would be heavily interested in having Edwards on board -- but probably only to steal secrets from the Bills in anticipation of their upcoming ... HAHAHAHA, sorry. Okay, actually because they'd prefer to have someone more lively than Mark Brunell to step in if Mark Sanchez is injured or falters.

And the Seahawks make absolute sense because Edwards is a cheap third option when should Matt Hasselbeck suffer an injury and they realize that Charlie Whitehurst isn't cut out to run their offense.

***
Why the Niners didn't make a claim is beyond me -- they're a team who needs to find an offensive identity, having been continually perplexed by the inconsistency of Alex Smith, who looked to have "arrived" during a close loss to the Saints in Week 2, only to have "checked out for the duration" against the Kansas City Chiefs on Sunday. Oh, and they're the only 0-3 team,

Edwards would provide them an option that's not David Carr to either push or replace Alex Smith. And look, Mike Singletary just fired his offensive coordinator only a few days after publicly defending him and acting outraged that anyone would question whether Raye knew what he was doing (um, he didn't, duh).

Plus, they could've claimed Edwards and Singletary could have done the whole "just for depth" and "Alex is our starter" dance, only to put him in the game after Smith's second interception in the first quarter against the Falcons in Week 4.

***
The Cleveland Browns decision not to pursue Edwards isn't as odd, I suppose, although Jake Delhomme hasn't looked great when he's been healthy, and while Seneca Wallace is a Mike Holmgren favorite, outside of tossing a bomb past an out-of-place Eric Berry, he hasn't been that great (370 yards, two TDs and a pick in two games).

But the decision not to spend a roster spot on adding a potentially gimpy donkey to their stable of already ugly horses is understandable, except that unless Delhomme can stay healthy, Cleveland's one bad break away from putting McCoy under center and really slapping a postage stamp to the season.

***
An argument could be made that the Panthers need to at least make a run at Edwards as well, but he's really nothing more than Matt Moore sans familiarity with the team and coaching staff.

The bigger problem for Carolina might be that John Fox already regrets his blatantly panicked decision to put Jimmy Clausen under center after an 0-2 start that only got uglier in a home loss to Cincinnati.

The good news is that the Saints -- as shown by Atlanta plowing through them in the Bayou -- are vulnerable against the run, and if there's one thing the Panthers should do well, it's pound the rock. They haven't been great about it thus far, but that's because they're staring down stacked boxes on nearly every play as teams refuse to respect whoever's under center.

That could change this weekend -- weather won't be a factor (see: three fumbles by Jim-Jim), and if Clausen can take his progression blinders off, quit staring down his receiver every play, the Panthers could be primed for a "where did that come from oh right it's the matchup" upset. You heard it here first.

***
The Jaguars would actually be an ideal situation, at least for Edwards. He'd face relatively limited competition -- by all accounts, Jack Del Rio wants to replace David Garrard in the starting lineup, he just doesn't have the bodies to do it after Luke McCown went down with an injury ... immediately after replacing David Garrard .

And let's face it, that offensive line has been putrid thus far; putting Todd Bouman, who is either 18 or 45 years old and who has backed up big names like Kyle Boller, Jamie Martin, Gus Frerotte and Quinn Gray en route to being signed by the Jaguars FOUR DIFFERENT TIMES , won't end well.

***
The notion that Ben Roethlisberger might not start when he returns from suspension following the Steelers' bye in Week 5 has been tossed around in the media. Like, kind of a lot.

And Charlie Batch has been very good in replacing Ben, at least, you know, relative to what everyone expected from Charlie Freaking Batch. But let's not lose our minds just because we (read: you) kind of want to see Roethlisberger punished by karma and riding the pine. He's by far and away the best quarterback option for Pittsburgh, and Mike Tomlin is going to start him as soon as he's allowed to.

If the Steelers happen to be undefeated at that point in time, well, watch out NFL.

***
Quickly ...

- Peyton Hillis didn't just put the whole "Eric Mangini hates  Jerome Harrison" conspiracy theory to bed, he shoved about 15 Ambien in its mouth and then wrapped it in a Snuggie.

- Thomas Jones and Jamaal Charles, as much as I'd like to think so, aren't in a battle for a job. They're just two running backs with different style co-existing in a system that just so happens to make one of them less valuable. And the less valuable guy just happens to be Charles, who's more talented.

- The only awesome thing about drafting Kevin Kolb in fantasy leagues is that you had to pick up Michael Vick. That's worked out quite well.

- I really thought that Chan Gailey was trying to showcase Marshawn Lynch to increase his trade value. And even if he was, in the process, Lynch has just become the best running back in Buffalo (once again).

- Kevin Smith returns this week and Jahvid Best is injured ... it shouldn't matter, but that's what Wally Pip probably said too.

- Yeah, I'm really pumped about the "Garrett Hartley versus John Carney" lede in this column next week too, thanks for asking.

Posted on: September 26, 2010 11:42 am
Edited on: September 26, 2010 12:51 pm
 

AFC inactives, Week 3

Posted by Josh Katzowitz

First, those who are active: Texans WR Andre Johnson, who had been questionable with an ankle injury; Patriots LB Brandon Spikes, who was a late add Saturday to New England’s injury report but was listed as probable; WR Joshua Cribbs, who hurt his ankle at practice Wednesday; and Baltimore CB Cary Williams, who has finished serving his two-game suspension for violating the league's personal conduct policy.

Tyson Jackson, Chiefs, DE: This is the second week in a row Jackson has been out, dealing with a knee injury suffered in the first game of the season. This isn’t terrible news for Kansas City. Although he was the No. 3 overall pick last season, Jackson has done next to nothing on the field thus far.

Adam Jones, Bengals, CB: He’s been better than expected this season, but his shoulder is banged up. Expect second-year CB Morgan Trent to get much more playing time as the third CB.

Antwan Odom, Bengals, DE: He was supposed to play today as he appeals his four-game suspension for violating the performance enhancing drug policy. But he’s not on the 45-man gameday roster with a wrist injury.

Jerome Harrison, Browns, RB:
This probably won't phase coach Eric Mangini much, because, for some reason, he doesn't like seeing Harrison, who's got a thigh injury, on the field. But now that Peyton Hillis and James Davis will get the carries, it's hard not to see Cleveland struggle in the running game.

Jake Delhomme, Browns, QB:
This was expected. But it's still important nonetheless. Especially since that means Seneca Wallace will get another start.

Brian Robiskie, Browns, WR: With three important pieces of Cleveland's offense out of today's game, it could get ugly today vs. Baltimore.

Terrence Cody, Ravens, NT:
Even though he practiced all week and wasn't on the injury list, Baltimore still decided to deactivate the rookie.

For more NFL news, rumors and analysis, follow @cbssportsnfl on Twitter and subscribe to our RSS Feed .
Posted on: September 21, 2010 12:48 am
Edited on: September 22, 2010 9:47 am
 

Dey Took Er Jobs: Quarterbacks droppin like flies

Posted by Will Brinson



Dey Took Er Jobs takes a look at the various job controversies around the league. If you don't get the title, you don't watch enough South Park .

Up until Kevin Kolb's concussion, it sure seemed like the only quarterback controversies we'd see this season would be on a bunch of crummy teams. Now, the Eagles could still end up stinking, but it sure doesn't look ilke that will be Michael Vick's fault -- through one-and-a-half games, he's been absolutely dominant on the offensive end, prompting pundits to point out that he may finally be maturing into the quarterback everyone wanted him to be in Atlanta.

So, yes, he will be making a LOT of money this time next year, thanks for asking. Because, as we'll detail shortly, there are plenty of teams in the NFL that could use a potential Pro Bowler who can rush for 100 and throw for 250 all in the same game.

But, having said all that, it's necessary to understand that Michael Vick won't be starting for the Eagles and there is no "technical" quarterback controversy.

For now.

Kevin Kolb will get the nod this weekend against the Jaguars who, fortunately for him, appear to be vulnerable through the air, sitting at 29th overall against the pass (an even 300 yards per game allowed).

Also fortunate for him is the game being played in Jacksonville, as far away from the only people who believe there's a debate about who to start under center (that would be the ever wonderful Philadelphia fans) for the 'Guls.

One good game from Kolb and we all go back to not freaking out about Vick starting, watching him perform well in spot action, and debating about who'll overpay him this offseason.

Well, at least until Kolb's next bad game anyway.

The same can't be said for a number of other quarterbacks in the NFL, though.

****

Matt Moore, for instance, may never see the field as a Panther again. That depends solely on how Jimmy Clausen plays this Sunday.

Admittedly (I use that word because I'm a Panthers fan who also dislikes Notre Dame and therefor find myself consistently conflicted about Clausen), the team has looked better offensively during the short stretches that Clausen's played.

He's young and he seems like he might be a bit of a bag, but at least he doesn't try to do his best David Carr impersonation by hanging in the pocket for as long as humanly possible before making ill-advised decisions.

Which, you might have noticed, is what Moore's been doing.

Oddly, it never made sense that John Fox wouldn't bother using Clausen unless the Panthers season was completely down the drain; he seems destined to leave Charlotte regardless of the outcome for 2010. But the early move to the rookie presents an interesting situation -- if the Panthers reel off a slew of victories and make a run (they're not winning their division or making the playoffs, but they can at least try), maybe it gives Jerry Richardson some hope that Foxy can coach up the young franchise quarterback and give him reason to offer the long time coach a deal.

Of course, Foxy might tell him to get bent and it won't matter. But that's another story for another day.

****

Buffalo's "controversy" is only "controversial" in that it involves multiple quarterbacks -- anyone who didn't think that Ryan Fitzpatrick and Trent Edwards were going be taking turns as the official Bills hide-a-mole all season along hasn't followed that team closely enough.

Really, the only surprise is that Chan Gailey decided to make a move this quickly. Or is it that he waited this long? I can never tell with that team.

****

Vince Young and Kerry Collins have been taking turns swapping jobs for as long as Reggie Bush has been immorally gripping a Heisman trophy. However, all indications from Jeff Fisher are that VY is still the QB and Collins' cup o' joe on Sunday was merely because of the Steelers defense and how poorly it matches up with Young's game.

(Aside: Pittsburgh's just good, y'all. People are going to have to start profusely apologizing to Peter King in February if Troy Polamalu stays healthy. Unless those same people drafted Ryan Mathews on their fantasy teams anyway.)

That doesn't mean that Vinsanity is free of getting the hook in the future though; he simply has to keep his head together moving forward, and not be the reason why the Titans beat themselves. That's entirely possible, although games against the Giants, Denver and Dallas aren't exactly that first week freebie Young got against the Raiders.

****

Oakland is now a "controversy free zone." Or something -- Tom Cable doesn't want to talk about whether Bruce Gradkowski is going to start, he just wants to know why JaMarcus Russell is wearing a Jason Campbell mask and still on his roster.

It's really outstanding just how horrible Oakland has made Campbell; not that he was Jim Plunkett (well, he wasn't Plunkett to anyone that has a modicum of sanity remaining anyway) before, but it sure seemed like he could be a shade above mediocre and manage to help the Raiders make a run. So much for that though -- Campbell's been 30 of 52 for a TD and two INTs so far in the season, good enough for a stinker of a 61.9 QB rating.

Gradkowski isn't exactly Plunkett either, but at least he's not Curtis Painter. Although, in hindsight, maybe Painter's job would be a lot less difficult if he just got traded to Oakland and had the opportunity to back up someone who's not Peyton Manning.

****

David Garrard is our final quarterback who got benched in Week 2 for poor play. Fortunately, he was able to pull a Judge Smails on Luke McCown's hamstring just before the backup led the Jaguars to their second score of the day, allowing Garrard to sneak in and toss a potentially job-saving TD.

The removal of Garrard in a painful blowout to San Diego is interesting, if only because he'd looked so stout in Week 1 while the Jags were dismantling the Broncos. Oh, and because everyone spent all preseason demanding that Jack Del Rio infuse controversial concern into the depth chart, only to have him firmly reject the notion that Garrard might lose his job.

It's safe to say that Garrard is safe to play … for now. But if the Jags keep sink further behind the leaders of what appears to be a very difficult division, people could get panicky.

****


Jamaal Charles and Jerome Harrison have to have kidnapped the children of their respective coaches (Todd Haley and Eric Mangini). There's no other explanation for why they see so few touches despite being so clearly the better backs on their team.

And I hear you, Chiefs fans who say "HEY SHUT IT, WE'RE 2-0, HALEY RULEZ!1" Also those of you who say, "Excuse me, Mr. Brinson, but Charles really doesn't do that much damage with his carries" -- I hear you too. But the thing is, and this is the thing: why not, you know, actually utilize Charles? Not that he should get the rock 30 times a game in between the tackles -- that would be silly. But a screen or two perhaps? That's not so much to ask, right?

As for Harrison, he has fumbled plenty and he has seen some shoddy rushing behind a Browns offensive line that only seems concerned about getting to the golf course; it just seems like Mangini keeps putting him in worst-possible scenarios, like getting three straight carries while being backed up against his own end zone. Don't worry, though, Peyton Hillis is there to not punch it into the end zone!

But, hey, maybe Haley and Mangini just really appreciate having two running backs that can handle the rock. It's not a problem like with quarterbacks.

Unless you're in Philly, of course. Then it's a "beautiful thing".

Well, at least until that first next bad game from Kevin Kolb.
Posted on: September 16, 2010 10:16 pm
Edited on: September 16, 2010 11:34 pm
 

So, what's the deal with Jerome Harrison?

J. Harrison only got nine carries last week against Tampa Bay (Getty). Posted by Josh Katzowitz

Perfectly encapsulated in the Cleveland Plain Dealer’s Tony Grossi’s lede in his story this evening is what Will was saying earlier today.

Writes Grossi: “Sometimes it seems like the Browns lose Jerome Harrison's number.”

Writes Will Brinson: … “He's (apparently) done something evil to Eric Mangini's family, because there's no other way to explain how a guy who put up a season's worth of rushing yards in the last three games of 2009 is still splitting carries with fumble-machine Peyton Hillis and only getting carries when the team is backed into its own end zone.”

It’s actually hard to believe Harrison didn’t play more last Sunday. So, let’s try to figure this out logically. Why didn’t the Browns give Harrison more than nine carries last week? After all, Harrison averaged more than five yards a carry, and the Browns were winning most of the game. What’s the problem?

My theories:

Maybe it’s because Harrison isn’t known as a great pass blocker. Maybe it’s because the three teams he dominated last year for a combined 561 yards finished No. 31 (Kansas City), No. 29 (Oakland) and No. 19 (Jacksonville) in the NFL in run defense. Maybe it’s because the week before he started that unreal three-game stretch, he gained nine yards on seven carries against Pittsburgh – the third-best running defense in the league. Plus, he’s small (5-foot-9, 205 pounds).

All of those are possibilities, I suppose.

But the man the team took in the second round of the 2010 Draft, Montario Hardesty, who blew out his knee in the preseason, was known to have knee problems coming out of Tennessee, and Peyton Hillis only had 13 carries last year and was known as a short-yardage back. Harrison has more experience – and more success – than either of those players. So, yeah, it makes all the sense in the world that Hillis started instead of Harrison.

I’m just kidding about that. Despite all I wrote in the two paragraphs above this one, I have no idea why the Browns didn’t give Harrison more carries Sunday. I’m not sure I can figure out this one logically, because it doesn’t seem like a logical move (I’m sure it’s logical to the Browns coaches, though).

Now, the Browns will face Kansas City. You know what happened last time Cleveland played the Chiefs? Harrison rushed for 286 yards and three touchdowns on 34 carries. Which means he’ll probably get 10 carries Sunday. 

And since I began this post with Grossi’s lede, I’ll leave with you his kicker as well.

Coincidentally, the only player in the NFL who had more rushing yards than Harrison over the last month of the season last year was Jamaal Charles of the Chiefs. Charles finished with 1,120 yards in 10 starts; Harrison had 862 in seven.

And look what the Chiefs did. They went out and signed veteran rusher Thomas Jones as a free agent. When the Chiefs took the field for their first play on offense Monday night against San Diego, Charles was on the bench.

"Lets you know it happens everywhere, huh?" Harrison said.


For more NFL news, rumors and analysis, follow @cbssportsnfl on Twitter and subscribe to our RSS Feed .


Posted on: September 15, 2010 9:01 am
 

Report: Delhomme in a walking boot right now

Posted by Will Brinson

Jake Delhomme's performance against Tampa Bay was one of the more disappointing items of the first NFL weekend. Perhaps his head was still ringing from the Ndamukong Suh "tackle" during the preseason.

The more likely cause is a first half ankle injury which he fought through , and which now, according to Tony Grossi of the Cleveland Plain-Dealer , has him in a walking boot.

Grossi's source also believes that Seneca Wallace will get the "bulk of reps" with the first team Wednesday in anticipation for Delhomme not being able to start against the Chiefs on Sunday.

Or, at the very least, being listed as questionable on the team's Week 2 injury report, which Delhomme probably will.

If Delhomme can't go against the Chiefs, that should mean a healthy dose of Jerome Harrison ... er, well, it should . But he's (apparently) done something evil to Eric Mangini's family, because there's no other way to explain how a guy who put up a season's worth of rushing yards in the last three games of 2009 is still splitting carries with fumble-machine Peyton Hillis and only getting carries when the team is backed into its own end zone.

That's an entirely different rant to rumble off on; the point here is that there's a decent chance Delhomme might not play on Sunday, depending on the severity of the ankle injury.

For more NFL news, rumors and analysis, follow @cbssportsnfl on Twitter and subscribe to our RSS Feed .
 
 
 
 
The views expressed in this blog are solely those of the author and do not reflect the views of CBS Sports or CBSSports.com