Post by eric on Oct 1, 2015 10:53:17 GMT -6
The rule:
A player can only be put as a Shooting Guard on the depth chart in three scenarios
1. A player is listed as a SG
2. A player is listed as a PG
3. A player is a SF or PF and has C+ or lower rebounding
If you wish to play a SF or PF out of position at SG and that player has a rebounding grade above C+, you must change that player's position in the software.
.
Why you should vote against this rule:
No one has provided any evidence that it will change anything.
The whipping boy / martyr for this change is Nick Fazekas.
Nick Fazekas has never made All-NBA, not even third team.
Nick Fazekas has won one championship, as the fourth best player on a team that was 17th in the league in rebounds per game.
And most importantly, nobody has demonstrated that removing Fazekas would have reduced the team's rebounds
The 3017 Clippers also had Greg Monroe with 13.2 RPG at A rebounding. Who's to say that swapping Fazekas for a C+ rebounding SG wouldn't have let Monroe get the 14.1 RPG he got with A- rebounding in 3010? It's really easy to steal rebounds from your own team, just look at Lance Stephenson IRL.
Ankly says the results of this rule are obvious. If they're so obvious, why can't he demonstrate them empirically?
Ankly says this is what the software intends. If it does, why doesn't it cap people playing at SG already?
Ankly says a lot of things, because he wants to distract you from the simple truth.
He has no idea what this rule will do. He has some guesses, and maybe they're good guesses, but I just don't think we should make rules based on guesswork.
A player can only be put as a Shooting Guard on the depth chart in three scenarios
1. A player is listed as a SG
2. A player is listed as a PG
3. A player is a SF or PF and has C+ or lower rebounding
If you wish to play a SF or PF out of position at SG and that player has a rebounding grade above C+, you must change that player's position in the software.
.
Why you should vote against this rule:
No one has provided any evidence that it will change anything.
The whipping boy / martyr for this change is Nick Fazekas.
Nick Fazekas has never made All-NBA, not even third team.
Nick Fazekas has won one championship, as the fourth best player on a team that was 17th in the league in rebounds per game.
And most importantly, nobody has demonstrated that removing Fazekas would have reduced the team's rebounds
The 3017 Clippers also had Greg Monroe with 13.2 RPG at A rebounding. Who's to say that swapping Fazekas for a C+ rebounding SG wouldn't have let Monroe get the 14.1 RPG he got with A- rebounding in 3010? It's really easy to steal rebounds from your own team, just look at Lance Stephenson IRL.
Ankly says the results of this rule are obvious. If they're so obvious, why can't he demonstrate them empirically?
Ankly says this is what the software intends. If it does, why doesn't it cap people playing at SG already?
Ankly says a lot of things, because he wants to distract you from the simple truth.
He has no idea what this rule will do. He has some guesses, and maybe they're good guesses, but I just don't think we should make rules based on guesswork.