<p>Can someone please gif the butt fumble? I would send $50 to the person who does it (not kidding).</p>
<p>“You made errors in your writing. The end.”</p>
<p>Again, they are only errors if they deviate from my intention of what they should be.</p>
<p>Definition of error:</p>
<p>er·ror (rr)
n.
- An act, assertion, or belief that unintentionally deviates from what is correct, right, or true.
- not unintentional.
- The condition of having incorrect or false knowledge.
- no false knowledge here.
- The act or an instance of deviating from an accepted code of behavior.
- not using professional standard or writing on an online forum is pretty acceptable behavior.
- A mistake.
- circular argument here
- Mathematics The difference between a computed or measured value and a true or theoretically correct value.
- irrelevant</p>
<p>[error</a> - definition of error by the Free Online Dictionary, Thesaurus and Encyclopedia.](<a href=“Error]error - definition of error]error by The Free Dictionary”>Error - definition of error by The Free Dictionary)</p>
<p>Again, keep trying.</p>
<p>I don’t make mistakes.</p>
<p>I agree with bearcats. The WRs have been open. By the way, you (bearcats) spelled “Jehu Chesson” with a capital J and capital C the first time and a lower case “j” and “c” the second time. Did the upper case letters in his name go from being capital to lower case?</p>
<p>I see another mistake (make it a two for one special).</p>
<p>^Again, since there is no intention to type his name up to the standard necessary in professional communication, there is no “mistake” or “error”</p>
<p>I got you this time with the above post.</p>
<p>^You mistakenly thought so.</p>
<p>No, just no.</p>
<p>You did NOT mean to type his name with upper case letters the first time and then use lowercase letters the second time. Don’t go there girlfriend! Don’t spit on my cupcake and call it frosting!</p>
<p>The definition of an error from dictionary.com</p>
<p>“a deviation from accuracy or correctness; a mistake, as in action or speech: His speech contained several factual errors.”</p>
<p>You wrote sentences that were not written “correctly.” Thus, you made errors. Errors are mistakes, As a result, you made mistakes.</p>
<p>But I did NOT mean to have his name typed with either upper or lower case. It is irrelevant to me in this setting, so there is no unintentional error.</p>
<p>Anyway this is getting pointless. The point is Gardner is not making mistake “from time to time”, he lacks the brain to take this team to its ceiling. Even at his best (against ND), he made the worst mistake EVER committed by a michigan QB and almost cost us the game.</p>
<p>Also, you did NOT spell his name correctly both times. Thus, you spelled his name incorrectly. That results in an error. An error is a mistake.</p>
<p>Boom goes the dynamite.</p>
<p>“But I did NOT mean to have his name typed with either upper or lower case. It is irrelevant to me in this setting, so there is no unintentional error.”</p>
<p>Look at the other definitions I have provided.</p>
<p>"You wrote sentences that were not written “correctly.” "</p>
<p>Again, they would be written “incorrectly” if this were intended for professional communication. However, my sentences are “correct” and “mistake-free” when comparing to my standard for online forum writing. Whether something is correct or not is always relative to a benchmark.</p>
<p>"Also, you did NOT spell his name correctly both times. Thus, you spelled his name incorrectly. That results in an error. An error is a mistake.</p>
<p>Boom goes the dynamite."</p>
<p>There is no dynamite. If I were using the word “analog” twice in a sentence, typing “analog” the first time, and “analogue” the second time, there would still be no mistakes/errors made. If things are independently correct when compared to a standard or a benchmark, the consistency is irrelevant.</p>
<p>I am going to sleep now. Let’s continue this tomorrow. In the mean time, $50 to the person who creates a gif of gardner’s butt fumble.</p>
<p>I got you this time:</p>
<p>You said:</p>
<p>“Again, they are only errors if they deviate from my intention of what they should be.”</p>
<p>“The “errors” you pointed out are not caused by poor reasoning, carelessness or insufficient knowledge, but rather an intention to not conform to the standards required in formal writing when commenting on a forum. “Mistake” implies erring intentionally.Try again.”
Today, 12:47 AM #17</p>
<p>Let me point out your mistake</p>
<p>“Mistake” implies erring intentionally.Try again."</p>
<p>Before, you said “they are only errors if they deviate from my intention”</p>
<p>A mistake implies erring unintentionally, not intentionally. You made a mistake.</p>
<p>Boom goes the dynamite.</p>
<p>I wish I didn’t make mistakes. I make several mistakes daily…many of them repeat offenses! 
But I am great at owning up to them. Socrates and I see eye to eye on that one. </p>
<p>Anyway, back to football. I am not overly concerned with Gardner. I think he is a good QB and he gives opposing defenses fits with his athletic ability. This is a QB with 9 games experience, so he will make poor decisions. Unfortunately, he has no tall, physical, reliable and talented WR to make him look good. Most great QBs need great WRs to make them look good. You will see how great our QBs play in 2016, when Drake Harris will have two years of experience and George Campbell one season of experience. And the OL is not giving him the kind of protection he needs…yet. Again, this is a young OL, with the exception of two starters, the remaining guys have no experience. All these problems will be fixed, but will they be fixed on time to salvage the season, or are we looking at another five-loss season.</p>
<p>^He also relies way too much on Gallon.</p>
<p>Anyway I really blame Gardner for this entire debacle. The defense is fine. The O-line needs work as well as the receivers. But Jesus Christ Devin just does not look comfortable out there and he becomes so timid. We won’t be able to squeak these wins out forever and one loss to a really bad team like Akron or UCONN is just gonna kill our season. Doesn’t seem like Morris is an option just yet unfortunately. Hopefully Devin gets it together.</p>
<p>Alexandre, my last post was directed to bearcats. He said he never made mistakes when I pointed that everyone makes mistakes. I said everyone makes mistakes because Devin Gardner has been making some lately.</p>
<p>Devin Gardner will get it together. Just remember how well he played against ND. Maybe he will just play good enough every game to win. It may not be sexy, but as long as Michigan wins, then that’s all that matters.</p>
<p>“Alexandre, my last post was directed to bearcats.”</p>
<p>I know 777Blue77.</p>
<p>I definitely agree that Devin is worth holding on to. If he does not do well this season, Morris can take over next year, once he is ready. Making Morris start now would be setting him up to fail. But I seriously doubt Gardner is going to continue to play poorly. I am fairly certain the team will improve as the season progresses.</p>
<p>The game was frustrating to watch!</p>
<p>In Gardner’s defense. Once Michigan got its act together at the end, they had 17 unanswered points. The two worst turnovers had nothing to do with Gardner…A punt return bounces off a freshman’s foot and is recovered by UConn or a ball falls out a pile of players and ends up being a touchdown for UConn. In one of Gardner’s long throws that was intercepted, a better receiver would have caught it or turned it into a pass interference…or at least prevented the interception. I didn’t really see this particular interception’s as Gardner’s fault. Gardner’s offense was constantly letting players through to try to sack him.</p>
<p>While it is nothing to brag about, it was an away game and there was improvement in over Akron, improvement in Toussaint, and improvement in Gardner. Michigan’s defense was not half-bad and likely saved the day.</p>
<p>They have two very much needed weeks to prepare for Minnesota. It is a home game. Last year when Gardner was QB they beat Minnesota at Minnesota.</p>
<p>We definitely can use the bye week. We have much to work on, particularly at OL.</p>