Forum: Author Hangout

Wording & gramar errors

rustyken 🚫

I've been working on a story for several months. Since my writing is being done with multiple stops and starts, I've frequently been rereading what has been written. A part of this is driven by a negative review I received after publishing a book that had been on SOL for several years. While I likely won't publish it as a book, I do intend to put it up on SOL when it is complete.

The reason for my note is that some of the errors I've found are shocking. Shocking to the point, that I don't believe I created them. So is it possible that I bumped the keyboard and autocorrect created the error. Recently I've had issues with having my fingers in the correct position on the keyboard. That can lead to some interesting text.

So the purpose of this note is to vent a bit. Thanks for listening. ;-)

Replies: The Outsider Dinsdale Dominions Son jimq2 Grey Wolf

The Outsider 🚫

@rustyken

Unfortunately, as I'm sure you know, even decades later, you or others will continue to find errors...

"How the HELL did I miss THAT?"

Replies: tendertouch

tendertouch 🚫

@The Outsider

"How the HELL did I miss THAT?"

Gremlins. As soon as a part of the story is out of sight, they come along and replace 'their' with 'there', remove 'not' in odd places, 'whose' become 'who's', etc... Nope, no way I missed that!

Dinsdale 🚫

@rustyken

Like the "gramar" in the title of this thread?

I was looking for an ancient Forum thread a couple of days ago, one of the contributions in that thread was from me and I was surprised to see an obvious - and uncorrected - error in there from all those years ago.
Luckily I can't find the thread now.

Replies: awnlee jawking

awnlee jawking 🚫

@Dinsdale

Like the "gramar" in the title of this thread?

Is a gramar error when you impregnate your granny?

AJ

Dominions Son 🚫

@rustyken

ou know, even decades later, you or others will continue to find errors...

"How the HELL did I miss THAT?"

I work in IT. I look at code that I wrote 5-10 years ago and think what idiot wrote that, oh that was me. :)

I also had an experience in college, where I spent several days looking for a missing ; in a C++ program. I couldn't find it and I was getting frustrated. I set it aside for a few days, not even thinking about it and as soon as I opened it back up, the spot missing the ; was staring me in the face.

Two possibilities:
1. Perspective, at the time you wrote it, you knew what you intended to write and when you look at it, you mind fills in what you expect rather than what's there. Set it aside long enough for your intentions to fade and your mind no longer covers the errors with your expectations.

2. An increase in skill. If it's been long enough, perhaps your writing skills have improved and the errors standing out to you in what you wrote before are a reflection of that.

Replies: tendertouch TheDarkKnight

tendertouch 🚫

@Dominions Son

I work in IT. I look at code that I wrote 5-10 years ago and think what idiot wrote that, oh that was me. :)

I think every programmer can relate. Not long before I retired I needed to revisit some code I wrote 25 years earlier. Cringe! Though I doubt anything I ever wrote was as bad as some of the things I saw that were written by engineers pretending to be developers — a 3,500 line long switch statement that was the key to an already complex engineering problem?

1. Perspective, at the time you wrote it, you knew what you intended to write and when you look at it, you mind fills in what you expect rather than what's there. Set it aside long enough for your intentions to fade and your mind no longer covers the errors with your expectations.

The part about setting it aside long enough is key here. DAMHIKT.

-tendertouch

TheDarkKnight 🚫

@Dominions Son

I work in IT. I look at code that I wrote 5-10 years ago and think what idiot wrote that, oh that was me. :)

One of the first things I learned in my career in computers is that it's easier to find errors in other programmers code than it is your own. I don't think its an ego thing, just a blind spot, maybe caused by cognitive dissonance.

Whatever the cause, the same thing happens when we are writing. I usually go through 3-4 drafts before I post something, but later on I often find things I missed.

Replies: Dominions Son

Dominions Son 🚫

@TheDarkKnight

I don't think its an ego thing, just a blind spot

That's was my point. The human mind is prone to seeing what it expects rather than what is. It's easier to see what is when you don't have expectations for what should be.

jimq2 🚫

@rustyken

At least you were doing your programming on a keyboard. I was programming punchboards to sort punchcards.

Grey Wolf 🚫

@rustyken

I'm highly sympathetic to this topic :)

My current editing cycle is:
1) Write it
2) No sooner than a few months later (with rare exceptions), read and edit.
3) Send it to my editors (one at a time)
4) Once all editors have looked at it, shelve it again as much as possible.
5) Just before publishing, reread again, carefully making updates.
6) Fix the (fortunately, relatively few) reader-spotted issues, if any.

That last pass makes a surprisingly big difference, considering I've read the whole thing at least three times before that.

The exceptions to the model have to do with last-minute additions. Sometimes things pop up and have to go in, and those get less coverage by nature.

Reply to topic

Forum: Author Hangout

Wording & gramar errors

WARNING! ADULT CONTENT...