Earlier quoted context omitted.
> That's what resumes used to be, after all -- a kind of a take-home test where you really do have enough time (and perfect knowledge) to get everything 100 percent right. The only thing this filters for is people who have been looking for a job for a long time and/or are people focused on presentation instead of content, good luck with that. We’ve hired incredible engineers across that have had typos and major resum…
Giving them a spell check is about as useful as measuring the ratio of times the letter ‘a’ appears relative to ‘e’. I'll leave the matter of whether one should be expect resumes to be at least reasonably correct (in terms of spelling and grammar) or not - or what the threshold for "reasonably" should be on this front - to the side for now. It's obviously a question of taste, to a certain degree. But sorry - what you…
Sorry I confused you. Let me be clear, it’s not relevant at all to job performance. I would take someone with terrible spelling and punctuation who actually writes documentation over someone who writes half as much because they are obsessing over details like that.
> in the sense of READMEs, docstrings, et
These are generally for other developers. Developers do not get confused when they see “NodeJs” instead of “Node.js”. Do you know what point you were trying to make?
> is definitely seen as a red flag, both in and outside the company.
> For any company you'd want to work for, that is.
Not sure what kind of company you’re talking about, but it’s definitely not a tech company. Maybe Wall Street or something a little slower paced?