Riggo's Rag
FanSided

Three takeaways from the Redskins loss to the Jets

By Jacob Camenker

LANDOVER, MD - NOVEMBER 17: Derrius Guice #29 of the Washington Football Team runs with the ball against James Burgess #58 of the New York Jets in the first half at FedExField on November 17, 2019 in Landover, Maryland. (Photo by Patrick McDermott/Getty Images)
LANDOVER, MD - NOVEMBER 17: Derrius Guice #29 of the Washington Football Team runs with the ball against James Burgess #58 of the New York Jets in the first half at FedExField on November 17, 2019 in Landover, Maryland. (Photo by Patrick McDermott/Getty Images) /
facebooktwitterreddit
Prev
3 of 4
Next
LANDOVER, MD – NOVEMBER 17: Dwayne Haskins #7 of the Washington Redskins looks to pass against the New York Jets during the first half at FedExField on November 17, 2019 in Landover, Maryland. (Photo by Scott Taetsch/Getty Images)
LANDOVER, MD – NOVEMBER 17: Dwayne Haskins #7 of the Washington Redskins looks to pass against the New York Jets during the first half at FedExField on November 17, 2019 in Landover, Maryland. (Photo by Scott Taetsch/Getty Images) /

2. Dwayne Haskins has a long way to go

Haskins had two weeks to prepare himself for his second start. He was squaring off with a weak secondary. It seemed that he would have an advantage, or he would at least have a chance to have a solid start in his first home start.

Instead, he struggled for the most part. He couldn’t get anything going in the first half. He misfired on a number of throws and showed off some of the mechanical flaws that made teams wary of selecting him early in the draft. In short, he looked like he wasn’t ready to play at the NFL level.

Now, it should be noted that the Redskins knew this when they took him. And it’s also part of the reason that they wanted to mostly give him a redshirt season this year. Still, the fact that Haskins wasn’t able to improve between starts against a strong Bills stop unit and the weak one of the Jets is disappointing.

More from Commanders News

That said, Haskins did have some bright spots in the game. He had a beautiful downfield strike to McLaurin that was called back due to holding on Brandon Scherff. He moved better in the pocket this week as well, but that didn’t exactly result in fewer sacks (he still took six). Some will argue that he was a bit better than his last start, as he improved as the game went along. But it’s important to note that his stats (19-of-35 for 214 yards, 2 TDs, 1 INT) were padded in garbage time.

Overall, what we learned about Haskins in this start was this. Haskins has a long way to go. He is going to need a lot of time to develop at the NFL level, so the rest of this year is going to be a learning experience.

Hopefully, he’ll show some growth. But if he doesn’t, the Redskins will continue to have questions at the quarterback position entering the 2020 offseason.

Home/Commanders News