|
|
|
|
|
by bubaflub
3446 days ago
|
|
Good catch! I read that paragraph the same way and I believe it is a typo. I've left a comment on the medium article asking the author to clarify that section. If you don't mind me asking, what is so off-putting about these types of mistakes? I'd like to do more personal and professional technical writing similar to this but I find it a bit daunting, especially when I consider that my audience could know much more about a subject than I do. Do you have any suggestions on how I could or should write articles that may contain errors so I don't upset readers? |
|
The problem for me is that my way of reading math stuff is to assume that whatever is said is being true and fit it into a growing mental model as I read. Many other students I know do that. Once you get into the flow of it this can get pretty fast without losing out on comprehension. When you come across mistakes, it leads to a speed bump, and you have to stop and re-collect your thoughts after this. This only happens to me for math and physics, not other kinds of technical writing, but it happens.
This doesn't turn me off an article, it's just super annoying.
Typos and stuff are fine, it's the "plausibly true" stuff that gets you. I suggest spending more time proofreading but not worrying more about it.