We've explored the strange decision-making people assume Chad Henne employs when throwing to people not named Braylon in this space already, but at least the assertion that losing an awesome wide receiver negatively affected Henne's performance made some sort of sense on the surface. It was wrong, but if you didn't watch the games it wasn't a totally insane opinion to hold.
Not so the latest round of speculation on the Hennebrain, which focuses on how Mike Hart's return instantly turned Chad Henne from a guy who couldn't hit Weis E. Coyote's ego into Tom Brady. Matt Zemek says so:
It was like Linus finally getting back his blanket: Chad Henne, with Mike Hart once again, finally felt (at least for long stretches of play, if not the whole game) like last year's quarterback.Tom Orr says so:
Chad Henne’s struggles against Notre Dame and Wisconsin may have had a lot more to do with the absence of a running back than anything else.This often passes for analysis in sports journalism: take the most obvious difference and claim that it's the reason for whatever happens, no matter how fanciful your connection is. Again it posits something in the Hennebrain like so:
if (RBs.Hart == healthy)That's total fantasy. The real reason Henne.Don'tSuck() got called? They fixed a bug:
"It was something with my release and body weight and my drop(back), and we fixed that," he [Henne] said. "It probably took about 15 minutes."That's common sense.