Welcome back to another year of "Good Call/Bad Call." If you're new to the column here's how things work; I comment on a few players from each major fantasy position, quarterback, running back, wide receiver and tight end. I pick out those that I think would be a ‘good call' for you to start this week, and those that I think are a ‘bad call.' I try and stay away from the top tier guys, because telling you to start Aaron Rodgers or Drew Brees would be like telling you to mercilessly ridicule the guy who drafts Aaron Hernandez this year and then yells, "Championship!" You're going to do it and not think twice about it. I also give a bit of fantasy football advice or commentary at the beginning of the article as well. I hope you enjoy it this season.
Since this is Week 1, your starting lineup shouldn't involve too much thought unless you did some risky drafting. When in doubt for Week 1, start your veterans. Start the guys with a proven track record. If your rookie sleeper is on your bench for a game it's no big deal, but having him throw a low single-digit performance because he fumbled under the pressure of the NFL lights isn't how you want to start your fantasy season. See how he does for a week or two before you get him in your starting lineup. Now on to the calls of the week.
Quarterbacks
If you're in a smaller league or have a top quarterback, start them and skip to the running backs' section. Now if you waited on a quarterback or are thinking about playing matchups with your two middle-of-the-road quarterbacks or you're in a really deep league then hopefully you have Alex Smith this week. Smith gets to test out his new team, new weapons, and new scheme with an easy matchup against Jacksonville. The Jaguars allowed Matt Schaub, Carson Palmer and Ryan Tannehill to all have 20-plus point games against them last year, and I don't see any offseason moves that have improved their defense enough to think that Smith won't have a nice game against them.
A matchup play you don't want to try this week is Andy Dalton against Chicago. The Bears defense was the fourth toughest for quarterbacks last year, and they've been consistently tough year in and year out. Look elsewhere for your starting quarterback this week. Dalton will have a tough time in Soldier Field. He's a bad call.
Sam Bradford's trip to Arizona is not one you're going to want any part of. Surprisingly, Arizona has done a good job stopping quarterbacks in recent years. Maybe because quarterbacks don't have to throw to beat the Cardinals or maybe because the Cardinals have some good defensive backs. Either way, they ranked as the second-toughest defense for quarterbacks last year. Bradford is not a good quarterback, and I'd sit him if you were going to start him for some reason.
Running Backs
A larger workload and an easy Week 1 matchup means you shouldn't be thinking twice about starting Lamar Miller this week. His trip to Cleveland should start his season out on the right foot. Cleveland was 26th against running backs in fantasy last year. The Browns change to a 4-3 might make things a little more difficult, but Miller should get plenty of chances to get you points.
Ahmad Bradshaw is another guy who's a good call for you to start this week. The knock on Bradshaw hasn't been what he can do when healthy; it's always if he can stay healthy. Going into the season he's 100 percent, and gets a good opening game against Oakland. The Raiders were the easiest team for running backs to rack up fantasy points against and the loss of leading tackler Philip Wheeler isn't going to help. Bradshaw should start out the season strong, and let's hope he makes it all the way through the game without hurting himself (fingers crossed, I own him).
I told you above to keep your rookies on your bench for Week 1, well if you were thinking of starting Eddie Lacy or Giovani Bernard, think again. Both of these rookies draw tough matchups in Week 1. Lacy and Green Bay travel to San Francisco, while Bernard and the Bengals head to Chicago. These two defenses were the second- and fifth-toughest defenses for running backs to go up against last year, and I don't expect much to change this year. They're both bad calls for you to start this week.
Wide Receivers
If you got T.Y. Hilton in your draft, you not only got a player I think is going to surprise a lot of people this year, you also got a guy you're going to want to start this week. Remember that nine-catch, 111-yard performance that made Brian Hartline a waiver wire wonder in Week 2 last year? That came against the Oakland Raiders. Who's Hilton playing this week? The Oakland Raiders. Expect big things this week and this year out of Hilton.
I expect the New York Giants-Dallas Cowboys to be a hard fought game. Don't expect the Cowboys to run away with it just because it's at Cowboys... oops I mean AT&T Stadium. After all, the Cowboys have just a 17-15 record in that building since it opened. A hard-fought game means a good balance of running and throwing, if the Cowboys had that balance, but we all know they're a pass-first team. I expect Dez Bryant and Jason Witten to have big games, and I also expect Miles Austin to have a good game, too. If you've got Austin, start him.
The Seattle secondary always seems to be tough. I've been saying this for the past couple of years, so don't be surprised if I'm telling you to sit your weaker receivers against Seattle. If you've got a stud, start him. Those guys will always find ways to get you points being the No. 1 targets on their team, but expect lower than usual numbers from them. This week that guy is Steve Smith. The Seahawks are stacked with talent in their secondary, so much so that they signed and cut Antoine Winfield this offseason who was a starter for the Vikings last year. If you can afford to sit Smith, do it. He's a bad call this week.
Tight Ends
A tight end that I seemed to always be grabbing this year in drafts was Brandon Pettigrew. He missed a couple of games last year, but in his two previous years he was a 70-plus catch, 700-plus yard tight end. Not bad for a guy who's average draft position was in the 13th round of 12-team drafts this year. Pettigrew gets a nice opening week matchup against Minnesota this week. He'll be running across the middle with Erin Henderson and Desmond Bishop covering him. Who? Yep, a guy who missed last year with an injury and a guy starting his first game at middle linebacker. As long as Pettigrew can stay away from Chad Greenway, he should have a good Week 1 stat line for you.
If you think you got a steal with Jordan Cameron in your draft this year, you probably did, but you're going to want to sit him this week. Cleveland plays Miami, and not only did Miami have the 10th-toughest defense versus tight ends last year, they went and signed a couple of really good linebackers in Dannell Ellerbe and Philip Wheeler. Add in rookie first-round pick Dion Jordan, who could be playing some standup linebacker, and Cameron won't be doing much this week. Note: When Cameron has a bad week this week and next, try and trade for him if you don't own him. Things get much easier after Week 2 with matchups against Minnesota, Cincinnati, Buffalo and Detroit, none of whom ranked higher than 15th against tight ends last year.
Another tight end that was showing up on some sleeper lists this year was Jermichael Finley. This week is not the week to check to see if you were right about his sleeper status. His matchup at San Francisco isn't a favorable one. You have to go all the way back to Week 3 of last season to find a team's No. 1 tight end that's playing in the league this year who scored double-digit fantasy points against the 49ers. This is not the week to start Finley. He's a bad call.
Good luck this week. May your starters stay healthy and I hope you make all the right calls.
Wow. Hate to be a Monday morning quarterback but I'd say Bad Call on the article. If you did the opposite of what was suggested, you probably did alright.
TE START - Pettigrew 6 yds 0 td SIT = Cameron 108 yds 1 td Finley 56 yds 1 td
That is some horrible advice, the SITS did better than the STARTS. With the exception of suggesting playing Witten (who had 2 tds), this guy got EVERYTHING wrong. Just proves my theory that any idiot can give as good FF advice as the "experts".
Good Call/Bad Call: Week 1 fantasysharks.comFri 9/6/13 7:00 AM 14 Comments
Comments
BroncosnationTue 9/10/13 4:21 PM
Yeah good call on Miller.....pfffffft
joe71101Tue 9/10/13 1:18 PM
dalton or manuel at qb flex
TouchdownBundyTue 9/10/13 7:31 PM
haven't checked the matchups but Dalton throws to A.J. Green and Manuel throws to.... umm.. Stevie Johnson. I'd go with the Red Rocket not the rook.
TouchdownBundyMon 9/9/13 3:26 PM
Wow. Hate to be a Monday morning quarterback but I'd say Bad Call on the article. If you did the opposite of what was suggested, you probably did alright.
QB START - Smith 173 yds 2 td SIT- Dalton 282 yds 2 td; Bradford 299 yds 2 td
RB START - Bradshaw 26 yds rush, 7 rec. 0 td; Miller 3 yds rush, 7 rec. 0 td SIT - Lacy 41 yds rush, 31 rec. 1 td Bernard 22 yds rush, 8 rec 0 td
WR START - Hilton 20 yds 0 td Bryant 22 yds 0 td Austin 72 yds 0 td SIT - Smith 51 yds 1 td
TE START - Pettigrew 6 yds 0 td SIT = Cameron 108 yds 1 td Finley 56 yds 1 td
That is some horrible advice, the SITS did better than the STARTS. With the exception of suggesting playing Witten (who had 2 tds), this guy got EVERYTHING wrong. Just proves my theory that any idiot can give as good FF advice as the "experts".
GerhardTue 9/10/13 1:27 PM
HAHAHAHA
ArtCall777Sat 9/7/13 11:08 PM
Lacy or Hilton at the flex?
DCommishSat 9/7/13 5:39 PM
Rb lamar miller or wr roddy white for my flex?
I already have mcCoy & spiller at rb's and julio jones, amendola and desean jackson at wr's
Badger_423Sun 9/8/13 8:34 AM
What do you have, a 6 team league? Jeeesh
GridironLegendTue 9/10/13 1:09 PM
White is out this week
lefties1Fri 9/6/13 6:59 PM
I have Morris, McCoy, and Miller...who do i start?
tdawgwhoaSat 9/7/13 1:05 AM
i'd say morris and mccoy.
lefties1Sat 9/7/13 4:26 AM
yeah that's what im thinkin...but ya never know miller could be the next muscle hamster...
guate4851Sat 9/7/13 3:06 PM
Schaub or Cutler?
cRoNiC98Sun 9/8/13 1:10 PM
cutler