Mishtakes… (Fandango’s Friday Flashback)

Yay, it is Friday again, and Fandango has just published his Friday Flashback post. The idea is that he picks a post from this day in a previous year, to give newer readers a better insight into what does and doesn’t make him tick.

I have always liked that idea, so shall also post my own reminiscence. As much as anything, it reminds me of where I was, where I am now, and how far I have come. Hopefully, you will find it entertaining along the way.

Just gonna go back a year today. I was still on Blogger at this time, but I had a WordPress account and was interacting with one or two bloggers.

I felt quite paranoid about my spelling mistakes, and felt that I should write something to try to explain it. Now, I take more of a “it is what it is” viewpoint. If somebody doesn’t “get” that, they’re the one with the problem, not me. If it is a blogger I’m friendly with, I’ll maybe nudge them a little in that direction, but won’t spend a lot of energy on it. I thought the same, myself, once.

It did make me think, though. What do I do when I see a typo on already-published posts? When nobody was reading the posts, it was a no-brainer, but with an audience, I’m more restricted. I settled on fixing spelling mistakes, maybe a tiny rework to add clarity, but once something is published, that’s pretty much it. If I think of some blinding new addition after that, tough. If a post contains typos that I don’t know about, that’s a pity, but I can’t in all good conscience allow something to stay wrong, not when I know about it.

There’s another reason for this, too – just that WP talks to search engines and so potentially our posts could be found by someone in months or even years. So at least if somebody does come across the post, it’ll be as presentable as possible.

But I bet that attitude is pretty much what we all say, no?

Mister Bump

…I’ve made a few, but then again…

I looked this morning at which of my posts have been most recently read by people, followed the link to the post itself. Almost immediately, I found a typo.

I do, of course, try not to make spelling mistakes in the first place. In fact, my spelling is good – very, very good – so if you see a typo it’ll most likely be a slip of my finger, or tapping the keyboard too lightly to register a stroke (happens a lot). I run my potential posts through a spellchecker, of course, (every little helps!) but I often find myself falling into the trap of running the spellchecker, re-reading something, deciding it can be better-worded, re-writing it (complete with typo) and not re-checking. Another favourite is writing a typo such that it spells a perfectly good word, albeit the wrong word. That’ll fool…

View original post 299 more words

Author: Mister Bump UK

Designed/developed IT systems for banks, but had a stroke in 2016, aged 48. Returned to developing from home, plus do some voluntary work. Married, with a grown-up, left-home daughter.

17 thoughts on “Mishtakes… (Fandango’s Friday Flashback)”

      1. I don’t know Pete. Maybe we did. I can never tell nowadays when posts come from. I get really confused because of the blindness. I get problems when someone is reblogging someone else, for instance, or responding to a challenge. I just can’t follow things any more. So folks will just have to put up with me lol.

        Liked by 1 person

          1. Lol Pete. We’ll see. I used to be able to see just a LITTLE bit in WP albeit very blurrily. Now, I can see NOTHING out of my right eye and my left one is almost the same. So panic stations now! Lol

            Liked by 1 person

            1. Google Translate will speak out its translations to you, so there’s not really any reason why thew WordPress Reader can’t do the same. I use the reader in Firefox, which does speak to me. It is probably 4-5x quicker than actually looking at the words.

              Liked by 1 person

              1. I know what you mean. I just can’t follow though. I don’t understand anything except straightforward posting. My brain can’t deal with it. Must be chemo fog!

                Liked by 1 person

  1. Ah typos, the bane of my online existence. I try to read my draft posts in “preview” mode before I publish them in order to catch typos and poorly constructed sentences or other mistakes. But the eye apparently sees what it expects to see, and so I read aloud not what’s actually on the page but what my brain tells me SHOULD be on the page. It’s only if I go back a few days, weeks, or months later and reread my published posts that my typos and mistakes make it past my brain’s filter and I can actually see them. Grrrr.

    Liked by 1 person

  2. I used to work as a graphic designer in a publishing company and we had a person whose job was to check the final draft of the articles. This was because it has been proven that if there’s a mistake (even an obvious one), and you don’t see it immediately, our eyes get used to it, and you won’t see it even after reading a 100 times. 🙂

    Liked by 1 person

    1. absolutely. I started off with a rule that I would never publish anything until at least the day after I wrote it, but obviously that is quite restrictive. Even checking something overnight was not foolproof. I’m more relaxed not – I get things wrong, but everybody does and this is just a blog.

      Liked by 1 person

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.