Although you probably can't tell it from this blog, I write for a living. Every writer though, professional or not, has certain issues that trip them up. This is especially true of things you don't use a lot.
For me, the majority of my writing is for online documentation. Online documentation should be composed of simple sentences. People scan and skim online help, they don't read it, so complex sentences cause people to miss valuable information.
Because of that, I rarely use semicolons or colons. I'm out of practice. Today I'm writing a document analysing the structure of the online help documents at salesforce.com. I had a long sentence that I thought was perfect for a semicolon.
Most tables are part of the body content; the exceptions, in our case, are access and edition tables, which are closely associated with headings.
I wasn't sure, though. So, I typed "semicolon usage" into Google and shazam! up came Semicolon Usage which reassured me that I was using the semicolon properly.
Granted, I could have used my handbook, but I'm sitting at a great little cafe in Berkeley called Le Bateau Ivre (the drunken boat), and it's a ten minute bike ride back to my handbook. I'd rather rewrite the sentence than do that, but thanks to some kind soul and Northwest Vista College, I don't have to do that.
Although my blog gets hardly any visits, I'm sure one of my 5 (on a good day) readers will send me an email saying, "Nope, that's the wrong way to use a semicolon". That's what you get for posting something like this, right? I actually welcome comments like that, but if you are the one that sends that email, please tell me how to fix it, don't just tell me that it's wrong.