aefenglommung (aefenglommung) wrote,
aefenglommung
aefenglommung

That's my story and I'm sticking to it

Earlier today, while typing a response on Facebook, my fingers seem to have produced the word "poor" when I intended them to produce "pour." Now, I make mistakes all the time in spelling, which aggravate me no end. I am one of those who edit their posts and replies as much as they can. But "poor" for "pour" strikes me as something I may have been assisted to by a word processing program. After all, "poor" takes three fingers to type, and requires one weak finger to type the "o" twice in succession. That feels completely different from typing "pour," which takes four fingers, and which flows nicely. I think it would be easier to type "pour" for "poor," all things considered.

Maybe my typing is just degenerating, but I see myself correcting a lot of repeated letters, failed capitalization, and other stuff that comes from a clumsy typing touch. I've been touch typing since I was 14 or 15, though. My handwriting is certainly deteriorating -- to the point where I can't read it myself sometimes if it gets cold -- but my typing shouldn't be that much affected. I suspect I'm being assisted to goof up.
Subscribe

  • Remember to feed your gorilla

    It's been a very busy year. Church-wise, we've been drinking from a firehose over in the GMC. But the new Conference is launched and functioning. My…

  • The Christmas Monster

    Sorry, no Krampus here. When I refer to the Christmas Monster, I'm referring to the overwhelming nature of Christmas, which exhausts and oppresses…

  • Thinking About Ordination Standards

    The Global Methodist Church has several different paths to qualify for ordination as a deacon, then elder. The standard path most mainline churches…

  • Post a new comment

    Error

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 0 comments