And now I've discovered that vim spell check skips words with leading markdown symbols like `*randical`. I'll have to dig into that more.
Update: pasting the web page to Google Docs found a few more typos. I fixed those, too. Usually I print and read to find typos, maybe I skipped that this time. Good reminder to do that and the Gdocs review. Really: thanks for the reminder, regardless of the sassiness. :-)
I really am sorry for being a troll and writing the kind of comment that bums me out on a regular basis. This seems like a good post and a good discussion.
It can just be frustrating for those of us that have a hard time getting traction when we post projects etc on sites like HN. It can manifest into petty toxic behavior especially in comment sections.
In the words of Paul Doherty... "I'll do better next time."
Taking a quick look, for me it seems that (Neo)Vim spell check skips anything in italics or bold. No highlights whatsoever anywhere in that region. Definitely not something you want to realize _after_ publishing articles!
Edit: Considering the comment about using :syn off, seems like this is probably a conflict of some kind with the way Vim actually italicizes/bolds things in terminals that support it, now.
‘aspell -c text.md’
Also, I found that `:syn off` gets vim to spell check within markdown formatting.
Some are burnt out and unable to focus.
Some have dyslexia and are trying harder than you'll ever know to proof read.
If someone is burnt out, the attitude is typically the tell regardless of care. It's deliberately sloppy.
One of the best engineers I ever worked with had dyslexia and by God if his class names weren't the funniest things I've ever seen, but they were consistent and the structure and documentation was thoughtful.
Unfortunately, over 12 years, I had two spelling mistakes slip through my hours of editing and proofreading. Some people absolutely eviscerated me for it. I mean, how could I not know how to spell X word? I must be a moron! In my opinion, these "simple-to-catch" errors are not always simple-to-catch when the writer knows what it is supposed to say and they are trying to proofread their own work.
That said, it proves you're right -- people do think less of you when you make such a mistake. I think we should all strive to cut people a little more slack, at least on Slack.
Like when someone misspells radical candor in the second sentence of a blog post about mentoring.
Seriously though, everybody makes mistakes but when I do slip up like this I don't expect people to engage with what I'm writing. And I do think proof reading is an incredibly important skill for new and experienced software engineers.
[edit] I just noticed the author is a staff engineer at MongoDB. He can misspell whatever he wants. I recant my sassiness.