Additionally, I know in the science profession good writing means more money. Research papers go through an intense peer review process. If you have poor writing skills, your papers will not be approved, you wont be published, you want receive grant money, and you’re less likely to move up in the industry.
]]>I think in your last question, the reason why people make significantly less for poorer writing in legal is because they often work with a contingency fee (typically 40%)–that is, they make money if you make money on the case. It makes sense–if they’re poor writers and speakers, they win less cases in court and therefore make less money.
]]>“Grammarly is a must-have
writing app that makes sure everything you type
is clear, effective, and mistake-free.”
Seems awfully convenient doesn’t it? Almost as if it goes hand in hand with the article right above it. While I do applaud Grammarly for a clever marketing plan, it is important to take everything you read with a grain of salt. Although everything present in the article lines up with one’s own sense of common sense, I believe it is important to look deeper into the matter and draw one’s own conclusions.
]]>However, I’m certain that the methodology behind this research involved only mechanical errors that are detectable by a machine. Such errors don’t by any means imply that the communication is ineffective. On the contrary, bending and breaking grammar rules can sometimes result in much more concise communication that’s still good enough at completely and precisely conveying what it needs to. A developer who perfectly follows prescriptivist grammar rules when writing the internal documentation of a class is going to end up causing everyone who reads that documentation for the rest of history to waste several extra minutes reading through unnecessary mechanical stuff.
My point is that even when we talk about “errors” we must consider the purpose and audience of the writing, and take a more descriptivist and flexible stance towards grammar if appropriate for the situation.
]]>