Greg C.
14 years ago

There was a time when 100% of Jackson's yardage this year came on a single run.

"Nonstopdrivel" wrote:



And man, was he ever awful back then. Thankfully, he got better and better with each carry, until that 71 yarder ruined his season.
blank
Pack93z
14 years ago
Jackson's real value is in pass protection and receiving, IMO if I may.

He is a very solid pass blocking back.. probably underrated.
"The oranges are dry; the apples are mealy; and the papayas... I don't know what's going on with the papayas!"
macbob
14 years ago

As a 3rd down blocker/receiver, I'd rate him above Grant and Starks at this time. But as the primary (1st/2nd down) running back, I'd have to rank him (carrying the ball) below Grant and probably Starks, though I want to see Starks do it in more than one game.

Jackson's run 136 times for 527 yds. He got 13% of those yards (71) on one play against Washington. With that one run he's averaging less than 4 yds per carry, and if you subtract that one run out he's averaging less than 3.4 yds per carry.

"Greg C." wrote:



Take out Grand or AP big runs and see where they lie.

"Stevetarded" wrote:



Yeah, I agree--take out anybody's successful plays, and the rest of their plays don't look nearly as good. But it was one run. The entire rest of the season hasn't looked so good.

I'm not bashing Jackson. Just giving my opinion. As a runner, I haven't been impressed with him and would rate him 3rd and would go with Grant or Starks first. As a receiver, I'd want Jackson.

"macbob" wrote:



Exactly, I hate that argument when it relates to a small sample size (like only 1 game) but compared to an entire seasons worth of plays IMO it's valid. When 13% of a starting running backs yards for the ENTIRE SEASON come off of 1 run that is very bad.

"PackFanWithTwins" wrote:



What's so bad about 13%? That statistic means nothing. Where do people come up with this stuff?

Why is it so hard for people to understand that long runs are a GOOD thing? Long runs are what really force defenses to honor the running game. One of Jackson's biggest shortcomings is that he doesn't break ENOUGH long runs, yet people continually use his longest run (his BEST run) in order to discredit him. I don't get it.

"macbob" wrote:



Greg-that was my point. It was 1 run. In 12 games. Other than that, pedestrian production.

Nothing special other than 1 stinking run. When you say he doesn't break enough runs, you're saying the same thing.
musccy
14 years ago

You shouldn't cherry pick the stats that you want to remove from a players' resume to fabricate an argument. But at the same time, we all know that Bjack provides very little threat to pop appreciable gains with any regularity (relative to NFL RB standards) and the 13% stat is an illustration of that.

"Greg C." wrote:



It is, huh? Then how do you explain the following: If Brandon Jackson had tripped and fallen at the line of scrimmage instead of gaining 71 yards on that play, his percentage of yards on his longest run of the season would be considerably LESS than 13%. So you're saying that would make him a better runner?

Stats are great when they actually mean something, but when people start pulling stuff out of their asses (in this case, percentage of total yards gained on the longest carry of the season), stats do nothing but muddy the waters.

"musccy" wrote:



No, but his seasonal average would drop from 3.9 to 3.4. So does a 3.9 avg make him a good back now?

IMO, Bjack seems slow, doesn't 'fall forward,' and can't seem to break through to the 2nd level of the defense with any consistency to give you the perception that he can break it open on any given play. I felt the complete opposite with Starks, but subjective 'intuitions' and observations about a player can even muddier than a manipulated statistic. To me, the 3.4 avg is more indicative of the threat that Bjack provides than the 3.9 avg.
macbob
14 years ago

You shouldn't cherry pick the stats that you want to remove from a players' resume to fabricate an argument. But at the same time, we all know that Bjack provides very little threat to pop appreciable gains with any regularity (relative to NFL RB standards) and the 13% stat is an illustration of that.

"Greg C." wrote:



It is, huh? Then how do you explain the following: If Brandon Jackson had tripped and fallen at the line of scrimmage instead of gaining 71 yards on that play, his percentage of yards on his longest run of the season would be considerably LESS than 13%. So you're saying that would make him a better runner?

Stats are great when they actually mean something, but when people start pulling stuff out of their asses (in this case, percentage of total yards gained on the longest carry of the season), stats do nothing but muddy the waters.

"musccy" wrote:



I understand that you don't like the fact that I tried to back up my opinion with a stat. Sorry it torked you off. I retract the 13%.

Now, back to the discussion, other than 1 stinking long run, Jackson hasn't done a whole lot as a runner this year through the 1st 12 games. Is that better?
Greg C.
14 years ago

As a 3rd down blocker/receiver, I'd rate him above Grant and Starks at this time. But as the primary (1st/2nd down) running back, I'd have to rank him (carrying the ball) below Grant and probably Starks, though I want to see Starks do it in more than one game.

Jackson's run 136 times for 527 yds. He got 13% of those yards (71) on one play against Washington. With that one run he's averaging less than 4 yds per carry, and if you subtract that one run out he's averaging less than 3.4 yds per carry.

"macbob" wrote:



Take out Grand or AP big runs and see where they lie.

"Greg C." wrote:



Yeah, I agree--take out anybody's successful plays, and the rest of their plays don't look nearly as good. But it was one run. The entire rest of the season hasn't looked so good.

I'm not bashing Jackson. Just giving my opinion. As a runner, I haven't been impressed with him and would rate him 3rd and would go with Grant or Starks first. As a receiver, I'd want Jackson.

"Stevetarded" wrote:



Exactly, I hate that argument when it relates to a small sample size (like only 1 game) but compared to an entire seasons worth of plays IMO it's valid. When 13% of a starting running backs yards for the ENTIRE SEASON come off of 1 run that is very bad.

"macbob" wrote:



What's so bad about 13%? That statistic means nothing. Where do people come up with this stuff?

Why is it so hard for people to understand that long runs are a GOOD thing? Long runs are what really force defenses to honor the running game. One of Jackson's biggest shortcomings is that he doesn't break ENOUGH long runs, yet people continually use his longest run (his BEST run) in order to discredit him. I don't get it.

"PackFanWithTwins" wrote:



Greg-that was my point. It was 1 run. In 12 games. Other than that, pedestrian production.

Nothing special other than 1 stinking run. When you say he doesn't break enough runs, you're saying the same thing.

"macbob" wrote:



I agree with you 100%. I don't think Jackson has been a very good #1 back. My reply was directed at Stevetarded. My point was that if you are arguing that an RB is not very good, it is nonsense to manipulate the numbers in such a way that you try to turn his longest carry into a liability.
blank
macbob
14 years ago

As a 3rd down blocker/receiver, I'd rate him above Grant and Starks at this time. But as the primary (1st/2nd down) running back, I'd have to rank him (carrying the ball) below Grant and probably Starks, though I want to see Starks do it in more than one game.

Jackson's run 136 times for 527 yds. He got 13% of those yards (71) on one play against Washington. With that one run he's averaging less than 4 yds per carry, and if you subtract that one run out he's averaging less than 3.4 yds per carry.

"Greg C." wrote:



Take out Grand or AP big runs and see where they lie.

"macbob" wrote:



Yeah, I agree--take out anybody's successful plays, and the rest of their plays don't look nearly as good. But it was one run. The entire rest of the season hasn't looked so good.

I'm not bashing Jackson. Just giving my opinion. As a runner, I haven't been impressed with him and would rate him 3rd and would go with Grant or Starks first. As a receiver, I'd want Jackson.

"Greg C." wrote:



Exactly, I hate that argument when it relates to a small sample size (like only 1 game) but compared to an entire seasons worth of plays IMO it's valid. When 13% of a starting running backs yards for the ENTIRE SEASON come off of 1 run that is very bad.

"Stevetarded" wrote:



What's so bad about 13%? That statistic means nothing. Where do people come up with this stuff?

Why is it so hard for people to understand that long runs are a GOOD thing? Long runs are what really force defenses to honor the running game. One of Jackson's biggest shortcomings is that he doesn't break ENOUGH long runs, yet people continually use his longest run (his BEST run) in order to discredit him. I don't get it.

"macbob" wrote:



Greg-that was my point. It was 1 run. In 12 games. Other than that, pedestrian production.

Nothing special other than 1 stinking run. When you say he doesn't break enough runs, you're saying the same thing.

"PackFanWithTwins" wrote:



I agree with you 100%. I don't think Jackson has been a very good #1 back. My reply was directed at Stevetarded. My point was that if you are arguing that an RB is not very good, it is nonsense to manipulate the numbers in such a way that you try to turn his longest carry into a liability.

"macbob" wrote:



Unfortunately, I was the one who started the 13% nonsense. The point which I was trying to make (obviously poorly) was that outside of that one run, he hadn't done a lot.
Greg C.
14 years ago

You shouldn't cherry pick the stats that you want to remove from a players' resume to fabricate an argument. But at the same time, we all know that Bjack provides very little threat to pop appreciable gains with any regularity (relative to NFL RB standards) and the 13% stat is an illustration of that.

"musccy" wrote:



It is, huh? Then how do you explain the following: If Brandon Jackson had tripped and fallen at the line of scrimmage instead of gaining 71 yards on that play, his percentage of yards on his longest run of the season would be considerably LESS than 13%. So you're saying that would make him a better runner?

Stats are great when they actually mean something, but when people start pulling stuff out of their asses (in this case, percentage of total yards gained on the longest carry of the season), stats do nothing but muddy the waters.

"Greg C." wrote:



No, but his seasonal average would drop from 3.9 to 3.4. So does a 3.9 avg make him a good back now?

IMO, Bjack seems slow, doesn't 'fall forward,' and can't seem to break through to the 2nd level of the defense with any consistency to give you the perception that he can break it open on any given play. I felt the complete opposite with Starks, but subjective 'intuitions' and observations about a player can even muddier than a manipulated statistic. To me, the 3.4 avg is more indicative of the threat that Bjack provides than the 3.9 avg.

"musccy" wrote:



Okay, I get it now. If your intuition tells you that a player is not as good as his stats suggest, you can just change the stat to a number that is more to your liking.

My intution tells me that James Starks is the best RB ever, so I am going to take away his 17 shortest carries and save the 16 yarder. Therefore, James Starks has a 16 yard average and is the best RB in the history of the league.

But wait--this also means that 100% of his yardage came on his longest run of the season. So he is simultaneously the WORST RB in the history of the league. This is so confusing!

Seriously, I think the problem here is that people assume that they can't make their point without some kind of stat, no matter how bogus, to back them up. But that's not the case. There's nothing wrong with saying that Brandon Jackson, in spite of his respectable YPC, has not been a very good RB for us, and a better player probably would've gained more yards. You don't have to cook the books to make your point.
blank
Greg C.
14 years ago

Unfortunately, I was the one who started the 13% nonsense. The point which I was trying to make (obviously poorly) was that outside of that one run, he hadn't done a lot.

"macbob" wrote:



Okay, gotcha. I will call off the dogs. Sorry if I was a bit harsh. I think I've made my point several times over by now, so I will try to let it go.
blank
Pack93z
14 years ago
The simple point in this case is that the 71 yarder is an abnormality to the rest of his body of work.. and being duly noted.

At least how I read it.
"The oranges are dry; the apples are mealy; and the papayas... I don't know what's going on with the papayas!"
Fan Shout
Zero2Cool (7h) : If the exploit is not fixed, we'll see tons of "50 top free agents, 50 perfect NFL team fits: We picked where each should sign in March" lo
Zero2Cool (7h) : Issue should be solved, database cleaned and held strong working / meeting. Boom!
Zero2Cool (8h) : It should be halted now.
Mucky Tundra (8h) : usually spambots are trying to get traffic to shady websites filled with spyware; the two links being spammed were to the Packers website
Mucky Tundra (8h) : you know when you put it that way combined with the links it was spamming (to the official Packers website)
Zero2Cool (8h) : Yep. You can do that with holding down ENTER on a command in Console of browser
Mucky Tundra (8h) : even with the rapid fire posts?
Zero2Cool (8h) : I'm not certain it's a bot.
Mucky Tundra (8h) : I've got to go to work soon which is a pity because I'm enthralled by this battle between the bot and Zero
Zero2Cool (8h) : Yeah, I see what that did. Kind of funny.
Mucky Tundra (8h) : now it's a link to Wes Hodkiezwicz mailbag
Mucky Tundra (8h) : Now they're back with another topic
Mucky Tundra (8h) : oh lol
Zero2Cool (8h) : I have a script that purges them now.
Zero2Cool (8h) : 118 Topics with Message.
Mucky Tundra (8h) : what's 118 (besides a number)?
Zero2Cool (8h) : They got 118 slapped in there.
Mucky Tundra (8h) : that's why it confused the hell out of me
Zero2Cool (8h) : Yeah, but this is taking a headline and slapping it into the Packers Talk
Mucky Tundra (8h) : Wasnt there a time guests could post in the help forum?
Zero2Cool (8h) : lol good question, kind of impressed!
Mucky Tundra (8h) : So how is a guest posting?
Mucky Tundra (8h) : Tell them its an emergency
Zero2Cool (8h) : Working. Meetings.
Mucky Tundra (8h) : Lots of fun; the spam goes back 4 or 5 pages by this point
Mucky Tundra (8h) : I thought you'd look for yourself and put 2 and 2 together lol. I overestimated ya ;)
Mucky Tundra (8h) : I thought Guests couldnt post?
Zero2Cool (8h) : And gosh that's gonna be fun to clean up! hahaa
Zero2Cool (8h) : Oh. Why not just say that then? Geez.
Mucky Tundra (8h) : check the main forum, seems a spam bot is running amok
Zero2Cool (8h) : What?
Mucky Tundra (8h) : Is the Packers online game "Packers Predict" now available for 2024? I can't tell
Zero2Cool (17-Feb) : Bengals planning to Franchise Tag Tamaurice Higgins
Zero2Cool (14-Feb) : Packers are hiring Luke Getsy as senior offensive assistant.
Martha Careful (12-Feb) : I would love to have them both, esp. Crosby, but either might be too expensive.
Zero2Cool (12-Feb) : Keisean Nixon is trying to get Maxx Crosby and Davante Adams lol
Mucky Tundra (11-Feb) : Yeah where did it go?
packerfanoutwest (11-Feb) : or did you resctrict access to that topic?
packerfanoutwest (11-Feb) : why did you remove the Playoff topic?
Zero2Cool (10-Feb) : Tua’s old DC won a Super Bowl Year 1 with Tua’s former backup
Mucky Tundra (10-Feb) : *winning MVP
Mucky Tundra (10-Feb) : Funny observation I've heard: Carson Wentz was on the sideline for both Eagles Super Bowl wins w/guys supposed to be his back up winning
Zero2Cool (10-Feb) : NFL thought it would get more attention week preceding Super Bowl.
Zero2Cool (10-Feb) : Yes, the Pro Bowl. It was played Sunday before Super Bowl from 2010-2022
packerfanoutwest (10-Feb) : pro bowl
Zero2Cool (10-Feb) : From 2010 to 2022, it was played on the Sunday before the Super Bowl
Zero2Cool (10-Feb) : They moved it to the BYE week before Super Bowl several years ago.
packerfanoutwest (10-Feb) : it was always after the SB.....
beast (10-Feb) : Though I stop following pro bowl years ago
beast (10-Feb) : I thought the pro game was before the Super Bowl?
Please sign in to use Fan Shout
2024 Packers Schedule
Friday, Sep 6 @ 7:15 PM
Eagles
Sunday, Sep 15 @ 12:00 PM
COLTS
Sunday, Sep 22 @ 12:00 PM
Titans
Sunday, Sep 29 @ 12:00 PM
VIKINGS
Sunday, Oct 6 @ 3:25 PM
Rams
Sunday, Oct 13 @ 12:00 PM
CARDINALS
Sunday, Oct 20 @ 12:00 PM
TEXANS
Sunday, Oct 27 @ 12:00 PM
Jaguars
Sunday, Nov 3 @ 3:25 PM
LIONS
Sunday, Nov 17 @ 12:00 PM
Bears
Sunday, Nov 24 @ 3:25 PM
49ERS
Thursday, Nov 28 @ 7:20 PM
DOLPHINS
Thursday, Dec 5 @ 7:15 PM
Lions
Sunday, Dec 15 @ 7:20 PM
Seahawks
Monday, Dec 23 @ 7:15 PM
SAINTS
Sunday, Dec 29 @ 3:25 PM
Vikings
Sunday, Jan 5 @ 12:00 PM
BEARS
Sunday, Jan 12 @ 3:30 PM
Eagles
Recent Topics
10h / Green Bay Packers Talk / Zero2Cool

14h / Green Bay Packers Talk / Zero2Cool

16h / Green Bay Packers Talk / Zero2Cool

16h / Green Bay Packers Talk / Zero2Cool

16-Feb / Around The NFL / beast

16-Feb / Green Bay Packers Talk / beast

16-Feb / Green Bay Packers Talk / Zero2Cool

15-Feb / Around The NFL / beast

15-Feb / Green Bay Packers Talk / Zero2Cool

14-Feb / Green Bay Packers Talk / TheKanataThrilla

14-Feb / Green Bay Packers Talk / beast

13-Feb / Random Babble / Mucky Tundra

10-Feb / Featured Content / Zero2Cool

10-Feb / Green Bay Packers Talk / Zero2Cool

9-Feb / Green Bay Packers Talk / bboystyle

Headlines
Copyright © 2006 - 2025 PackersHome.com™. All Rights Reserved.