3 ms·
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 shoul
by vanusa 5y ago
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're saying about the ratio of 'a' to 'e' makes no sense at all.
And on this front:
Unless you’re writing user documentation
I don't know what planet you live on -- but on my planet, good engineers write "user documentation" (in the sense of READMEs, docstrings, etc) and participate in mailing lists, do conference presentations, etc, all the time. And yes, while nobody is 100 percent perfect, consistently making a large number of gaffes (or more to the point: conveying an attitude that these things just don't matter; or that you're so hot that they shouldn't matter for you) in these contexts -- particularly when there there is plenty of time available to edit and review -- is definitely seen as a red flag, both in and outside the company.
For any company you'd want to work for, that is.
- skinkestek 5y agoWell. These days I think I work at the best team I ever worked on and it seems I'm in the top two in spelling, it is almost as if the rest if the team is mildly dyslexic or doesn't care. But they are nice to work with, smart and they make good code. I'll take them 49 times out of 50 over some perfect in code and writing but nasty in person ex colleagues. Even if I really really really need a specialist on hight performance <whatever it was, I can't add a dead giveaway here> I'd still try to look elsewhere first. Edit: ... and those two ex colleagues? Their code was good but it wasn't perfect either.
- vanusa 5y agoAm 100 percent with you there - nice and basically decent to work with always trumps the willful disregard for these basic qualities. No matter how skilled they are, or their accomplishments.
- kortilla 5y ago> But sorry - what you're saying about the ratio of 'a' to 'e' makes no sense at all. 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?