Live data from Hacker News

Why it’s so hard to catch your own typos (2014)

wired.com

1–10 of 44 posts

Re: Why it’s so hard to catch your own typos (2014)

#4
post #3

Slightly unrelated, but when I need to proof read something I listen to it being read aloud by TTS. It's immediately obvious when something doesn't sound right.

Reading it in reversed order, from the end to the start, word by word also helps to discover typos.

Re: Why it’s so hard to catch your own typos (2014)

#5
Because the solution is hidden behind "subscribe to wired to keep reading"!

I find reading the text back in a different font often helps, particularly switching from mono-spaced to variable or vice-versa, though I'm not sure why. Perhaps I remember the shape of the words as correct because that is what I just typed, and when all the words have a different shape I'm forced to think about it differently. It is why I often immediately spot a typo without even really looking after hitting "add comment" here, or flip down to look at the preview of a stack exchange post. The effect seems less pronounced when both texts are in view the whole time as with some markdown editors I've tried, which is why I think an unconscious "it looks like what I saw as I typed so is correct" thought is a factor.

Some time ago I tried having my posts read back to me via TTS but found the low quality voices and mispronunciations of actually correct phrases irritating enough to run any productivity gain. I should try that again, as I get the impression from posts here & elsewhere that freely available TTS options have improved significantly in recent years.

Re: Why it’s so hard to catch your own typos (2014)

#6
I do a lot of proof reading for my own and other people's papers and decks. When I started out I found I was incredibly hit and miss at spotting issues. I now have a few rules that help me catch (most of the) issues:

Start by finding somewhere quiet and reading the document out loud yourself, you will catch so many issues this way (though you still risk your mind filling in blanks or missing your common errors). Ideally this will be to someone else, they can help you find issues or question where things aren't clear - but even alone you will get value if you take your time.

As others have said, I then use a 'read aloud' tool such as the one in review in Word, sadly PowerPoint doesn't have the same tool.

Do a search for things you know get missed - one for us is double spaces and using a hyphen or minus sign - in place of a long dash —

Search for all common abbreviations and replace with the full word

Make sure there is a single date format throughout the deck

Check bolding, alignment and fonts

...

The list could go one, but I find that just concentrating on one thing at a time really helps - don't try to look at a whole page and find all the issues. And don't stop - make sure you keep reviewing as the final edits go in, the worst thing is someone pasting an update in from an email and messing with fonts/alignment etc. Just before you submit.

And give yourself time - maybe 20 percent of my time is spent writing a deck, 80 percent is spent editing, refining, validating and getting levels or approval.

The point of a great paper or deck is to be respectful of your audiences time. Make sure that you don't offer them the chance to get distracted by something - you want to keep their focus on delivering the answer you are looking for.

In the past I've seen so many meetings thrown as people get hung up on errors in the materials which eats into their confidence with the presenters - wasting time and focus.

Re: Why it’s so hard to catch your own typos (2014)

#7

Because the solution is hidden behind "subscribe to wired to keep reading"! I find reading the text back in a different font often helps, particularly switching from mono-spaced to variable or vice-versa, though I'm not sure why. Perhaps I remember the shape of the words as correct because that is what I just typed, and when all the words have a different shape I'm forced to think about it differently. It is why I of…

> the solution is hidden behind "subscribe to wired to keep reading"!

Archived copy: https://archive.today/ziE8c

Post reply on HN