"He's a hard worker, and he watched me and Tim (Hardaway Jr.) and Nik (Stauksas) put work in to become (first-round picks), and I'm just happy he's getting better," Burke said. "It's great for the program, too. It shows what type of program the University of Michigan is and the direction it continues to go in."
I don't have it in front of me but in the section written by the professor at Colorado, it says "pour" over instead of "pore." Poor form! (See what I did there?)
Whatever, the book is awesome regardless.
there are a few: I called Earle Bruce "Bruce Earle," and there are a couple errors in my zone read article. Problem is that I go through every piece and by the time it's time for a final proof I know the piece so well that I hardly see most of the words. Working on a better process for next year.
Seriously, I will. I had to quit engineering and major in Econ because I was too good at English. And it's not just a way for me to get my grubby little mitts on a free advance copy of HTTV: 2009 (although it is).
For my privacy, my new username is "non-Oriental non-Andrew"
Brian's an engineer graduate; cut him some slack. There's a good reason why the engineering school lets you take Engin 100 and 101 instead of intro English classes that LSA students take. HTTV 2008 was great read; keep up the good work Brian.
I wrote for the Daily for awhile. (I was small-time; I only covered minor sports). One thing they used to tell us was to read the stories backwards (i.e., last paragraph, then next-to-last paragraph, etc.) during proofreading. That way you don't get distracted by the content as much and errors are supposed to be more noticeable.
Hat, the same can be said for spellchecking if you don't have a spellcheck program handy (you know, if you ever find yourself editing after a plane crash in Siberia or something) only you literally read the piece backwards word by word. It completely removes the context and lets you focus on the words themselves.