Whenever I look at job resumes (which I have to do from time to time), I usually immediately bin anything that is poorly written or poorly presented - and this includes poor spelling.

Of course. So have I, but to fail to discriminate between a formal document like a job application, and an informal communication like a posts on PM, Usenet or irc does no one good service.

... and another native English speaker who is just being plain lazy.

There are many reasons why a person, such as myself, may be prone to misspelling words. To blithely attribute them all to laziness, is itself a form of laziness. A failure to look (or care) more deeply.

Spell checkers can help, but they are far from infallible with the propensity of English to have so many homonyms. They also require time to use. Time well spent upon formal documents, though it is no substitute for proof reading by someone with the appropriate skills. For informal documents, it is time that must be taken from other, more important activities.

Some of the most capable programmers, including a few high level monks, produce excellent code but very poor documentation for it. Technical writing is a skill all its own, and the best technical writers are rarely programmers.

Your association of poor spelling with "sloppiness and laziness", probably says more about you, those those you diminish and reject on the basis of it.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^5: Maintainer looking for a module by BrowserUk
in thread Maintainer looking for a module by pileofrogs

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.