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.

With respect, I have to disagree. In all forms of communication, I believe it's important to take a few moments out to think about what you're about to say, or review what you have just written before you say it or click on the send/post button. If you care about others understanding your meaning. And especially if you're expecting some sort of feedback. If you don't care, or you are just plain lazy, then you go ahead and blurt out whatever pops into your head. And of course we see this all the time. I see it every day in my workplace. Whole email threads (an informal communication medium) that go backwards and forwards and around in circles - and waste everybody's time - simply because the person who started it all didn't bother to take a few moments to read what he was about to say to ensure it actually made some sense.

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.
Yes, I accept this. And I'll admit that perhaps I was generalising a bit. Of course, everybody makes accidental typos and spelling mistakes. Hell, I even found a typo in the Owl book the other day (which - being the pedant that I am - I will naturally report :D). The distinction I make is between accidental and deliberate sloppiness - and I do believe it's fairly easy to spot the difference.
For informal documents, it is time that must be taken from other, more important activities.

I understand your point here, but I question its validity. Lets take PM posts as an example. Why do we have a preview button? How long does it take to quickly preview your post before you create it to check that it actually says what you want it to say and is reasonably coherent? And how much of everybody's time (including your own) do you save if you discover that it's nonsensical (and correct it) before posting?

cheers,
Darren :)

Update: Fixed spelling mistake. heh..thanks YuckFoo

In reply to Re^6: Maintainer looking for a module by McDarren
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.