Your Pain Is Our Pleasure

We proofread your Google Docs or Microsoft Word files within 24 hours. We hate grammatical errors with passion. Learn More

 

justinforce

Joined: February 10, 2010  (email not validated)
Comments posted: 5
Votes received: 13

No user description provided.

Questions Submitted

Recent Comments

Coming from a science/engineering background, I think that it's very clear if you write it out "point twenty-five percent."

justinforce March 4, 2010, 9:58am

13 votes    Permalink    Report Abuse

You know, after reading this:
http://www.worldwidewords.org/articles/herring.htm

I feel pretty comfortable using "red herring" to describe unintentional deception. Given its roots--"neither fish, nor flesh, nor good red herring"...meaning something that was nondescript or neither one thing nor another--and its modern accepted usage, I think it works fine for my purposes.

justinforce February 26, 2010, 7:12am

0 vote    Permalink    Report Abuse

The documentation is meant for internal use by fluent (but not always native) English speakers in Southern California.

So far, the page is still called "Red Herrings." Red herring is currently used around the office in this context, but I had reservations about using it in our documentation in that context when I read that it implies intent.

justinforce February 26, 2010, 7:05am

0 vote    Permalink    Report Abuse

Thank you all for your responses. I'm liking "will o' the wisp" and maybe "chasing your tail."

justinforce February 22, 2010, 2:10pm

0 vote    Permalink    Report Abuse

From what I've read, a red herring does imply intentional deception, such as in a play, making it seem to the audience that one character is the villain to distract them from figuring out the actual antagonist.

I'll describe the exact situation.

I work in IT. We're creating a wiki page full of these instances of false leads for troubleshooting. For instance, our admin was trying to find the cause of a reported error in his logs because a web service wasn't running. It turns out that the error has always occurred and had nothing to do with the web service. We wrote it down so that it won't happen again.

justinforce February 10, 2010, 8:41am

0 vote    Permalink    Report Abuse