Symphonious

Living in a state of accord.

Greg, Im Well Aware of When Its Appropriate To Use An Apostrophe

This blog is a very informal place for me – I write what I want, when I want, how I want. Thats why I have a blog. Recently, Greg Black took issue with my (admittedly fairly regular) misuse of the apostrophe. I am actually quite familiar with the rules of when to use an apostrophe and when not to, however since this is informal writing, I tend not to proof read me comments and also tend to think much faster than my fingers type. If this were formal writing not only would I proof read my comments to ensure that apostrophe’s were used in the correctly locations but also rewrite those long sentences with many sub-sentences in brackets (I have a bad habit of doing that – it matches my though patterns), and of course the over use of dash’s to tack on additional points. I would probably even go so far as using paragraph’s to delimit separate points instead of using them whenever I feel like some white space is required. Heck, I might even run a speeling checker over it. Its also worth responding to Gregs comment:
Just as we programmers have to learn to spell correctly when we write C or perversions such as Perl or Java, we should also be able to manage to write English correctly.
Actually, I learnt to spell incorrectly when I started programming and have been spelling “colour” as “color” ever since. My writing now naturally comes out as an odd mix of Australian and American spelling’s unless I’m consciously thinking about what context I’m writing it in (I work for a US company so correspondence with customers and documentation should use US spelling’s but I also write for Australian audience’s outside of work). More importantly though, as a professional programmer the most important skill I’ve developed is the ability to read other peoples code even when its horrendous. Most languages will allow a certain amount of leeway on their syntax even if its a really bad idea to actually take advantage of it (similarly, the human brain is perfectly capable of reading a sentence that incorrectly uses apostrophe’s even if its not the best way to write it). When all is said and done though whats important is that the message Im trying to communicate gets to the people Im trying to communicate it to. Since this blog isnt actually trying to communicate with anyone – merely to serve as a dumping grounds for my thoughts and give my fingers something to do while Im talking to myself – its pretty hard to fail in that aim. However, I will try to pay a little more attention to when I use apostrophes, as Ive quite clearly done in this entry. Oh, and if you really want to teach me about punctuation, why not buy me the shirt.
  • DrBacchus says:

    I thought the purpose of an apostrophe was to warn the reader, hey, look out, here come’s an s! (Everything I know, I learned from Dave Barry.)

    September 7, 2004 at 8:18 pm
  • grunties says:

    That’s pretty much the argument I used at my last job interview when the interviewer commented on my calling variables ‘v-bibbles’.

    April 30, 2009 at 3:59 pm
  • Adrian Sutton says:

    hmmm, there’s a line and I think v-bibbles is well and truly on the wrong side of it. :P

    April 30, 2009 at 4:02 pm
  • Schmoo says:

    The trouble with this kind of thing is that it causes a double-take. Your sentence “ensure that apostrophe’s were used”, for example, I read as “ensure that apostrophe is were used, errr, ensure that apostrophes were used”. I barely notice the first couple, but after a few repetitions it becomes distracting – I’ve learned that it’s going to be present throughout, and I’m keeping an eye out for it in order to avoid the double-take. It breaks the flow of concentration – it’s a barrier to your ideas entering my head.

    It’s on a tiny scale, granted – it’s not the same as reading an entire article written in TXTSPK, for instance, but the principle of it niggles me while I’m reading. It’s like trying to read a book in an uncomfortable chair – you can concentrate all you like, but you just don’t quite connect with the material in the same way.

    The bottom line is that you’re making me put in extra effort to read something, in order to save yourself extra effort in writing it… You want it to be read, and I want to read it, so why skimp on the effort?

    PS: I think Grunties was taking the mickey – he’s the colleague who sent me this link (…and he’s out of the office for a while so I can’t check his intentions). But, if I know him, he was drawing your attention to the line you mention and suggesting that it was in the wrong place. Straight answers are a bit of a rarity around here :)

    May 1, 2009 at 11:44 am
  • Adrian Sutton says:

    Indeed, this whole post is very tongue in cheek. There’s a big difference between the occasional mistake and an article that deliberately breaks the rules at every opportunity like this one. In fact, rereading this after so long left me cringing. The original article that prompted this and the recent one that caused me to link to it again had just a single misused apostrophe in well over a page of text. Complaining about that kind of error rate is really just being pedantic. Explaining the grammatical rule when it was clearly used correctly in a number of places, starts to border on just plain rude.

    I don’t actually blog so other people can read it – I blog because it’s a great way for me to think through a topic. As such, my top priority is to focus on the thoughts, not the expression of them. That leads to a few grammatical errors, but the rambling, unstructured content it creates is actually a much bigger problem for readers.

    As for Grunties, I was hoping that he was taking the mickey, but if you read all the comments on this blog you probably wouldn’t be completely sure either. There are some strange folk out there….

    May 1, 2009 at 12:25 pm

Your email address will not be published. Required fields are marked *

*