4 ms·

> They're vs Their and similar normally denote uneducated native English speaker. in germany only grammar nazi's would actually hate such things. they are too

by merb 10y ago

> They're vs Their and similar normally denote uneducated native English speaker. in germany only grammar nazi's would actually hate such things. they are too common, to say that only uneducated people do it. people who write code and distribute code to the whole world are not writers, there is no need for "perfect" grammar and typos. i mean in my first application i've written quanity instead of quantity (inside the code), somehow it slipped in a lot of places, but i think many many people who will read the code would still understand it. as long as the user interface is checked, i think it's okay if the readme/documentation has typos or grammar mistakes (on open source projects). the most important thing is, is that people understand each other/understand what it's all about. which is just fine for nidium.

franciscop 10y ago
Really? I have seen it in many "comment sites" but rarely see it in technical documentation and blog posts. And I don't hate that at all! I'm just pointing out that someone who makes these kind of mistake is probably native and that a large number of these typos indicate that: - The writer didn't do proofreading (or did it but is not aware of the mistake). - It's made by a single person with no one else to check on the documentation. Now while they are not technically a display of low code quality, they are normally indicative of low attention to detail and lonely programming, which is not the optimal situation for high code quality. For people using English as the second language I'm a lot more forgiving since they and their coworkers might not even know how to properly express some things due to translation issues (and not due to lack of proofreading/lonely programming). In my experience when I'm doing proofreading of my own libraries I also catch ambiguous sentences, lacking documentation or examples and many other things that could be improved upon.

by merb 10y ago

franciscop 10y ago

Really? I have seen it in many "comment sites" but rarely see it in technical documentation and blog posts. And I don't hate that at all! I'm just pointing out that someone who makes these kind of mistake is probably native and that a large number of these typos indicate that: - The writer didn't do proofreading (or did it but is not aware of the mistake). - It's made by a single person with no one else to check on the documentation. Now while they are not technically a display of low code quality, they are normally indicative of low attention to detail and lonely programming, which is not the optimal situation for high code quality. For people using English as the second language I'm a lot more forgiving since they and their coworkers might not even know how to properly express some things due to translation issues (and not due to lack of proofreading/lonely programming). In my experience when I'm doing proofreading of my own libraries I also catch ambiguous sentences, lacking documentation or examples and many other things that could be improved upon.