I make typos all the time as well, on stuff I am just writing off the cuff like a forum or chat message. But when it comes to something important, don't you check it over dozens of times? hundreds of times? A mere missing semicolon will make your code not compile. How could you let a superficial typo go uncorrected once you see it? How could you not see it when it's in the most obvious spot?
It suggests a certain lack of diligence; like you didn't proofread your work. What about the person that should have proofread it as a second opinion? Did this really follow a rigorous academic process at all? <- That's the first impression when the presentation is sloppy.
Comments
I make typos all the time as well, on stuff I am just writing off the cuff like a forum or chat message. But when it comes to something important, don't you check it over dozens of times? hundreds of times? A mere missing semicolon will make your code not compile. How could you let a superficial typo go uncorrected once you see it? How could you not see it when it's in the most obvious spot?
It suggests a certain lack of diligence; like you didn't proofread your work. What about the person that should have proofread it as a second opinion? Did this really follow a rigorous academic process at all? <- That's the first impression when the presentation is sloppy.