And The Winner Is...

Drumroll please! The winner of my first blog giveaway is....

We interrupt our regularly scheduled programming to bring you this very important message.
(You didn't really think I was just gonna blurt it out, did you? Silly goose.)

I wanted to clue you all in a little on why I did the giveaway and how I selected a winner. I know you probably don't care, but I'm telling you anyway.

The first and most obvious reason is that I'd hoped to get more followers for my blog. Shameless, right? But it actually did work. I went from having one follower to having six. And I didn't even make following my blog a requirement for entry into the giveaway, as so many other bloggers do. Ok, sure, I may lose five of you after I make the announcement of who won the Starbucks Gift Card, but I appreciate you stopping in, nonetheless.

The second reason I did it was... well, there really wasn't a second reason. Driving traffic to the site was about it. Pitiful? Yes. Effective? Somewhat.

Now, as to how I selected a winner, there was only one way to be fair, since many of the entrants were friends of mine.

A huge shout out to all of you, by the way, for putting up with my constant tweets and status updates about the giveaway; so glad none of you unfriended me, though I sure would understand if you'd blocked me from your news feed for a few days. It's okay to turn my news feed back on now. Really. I promise. Please?

Back to how I picked a winner (and how all winners of future giveaways will be selected!)

Each comment was assigned a number in sequential order as it was posted and provided it was within the timeframe specified. Once I had all the entries, I headed over to RANDOM.ORG and used their awesome Random Number Generator. You just put in your starting and ending numbers and it will pick a random number for you.

In this case, it selected number 13. Yes, lucky number 13.

And now, back to our regularly scheduled programming

Making the winner of the $25 Starbucks Gift Card...

The envelope please....

AztecConsulting! Congratulations!
I will be contacting you shortly for information on how to collect your winnings.

To the rest of you who didn't win this time, be not discouraged, there will be more giveaways.

Thank you so much for participating, and for sharing your awesome Starbucks drinks with me; I will definitely be ordering some, ok, most, of these at some point in my future.

Here's to a caffeinated weekend!

Share

Typos, Bad Grammar and Other Such Horrors

By day, my profession is that of a software quality assurance analyst. To non-techie folks this likely sounds way fancier than what it really is. In plain English, I test websites and software programs. Part of my job also involves proof reading the copy on said websites and programs. Yes, I actually get paid for this.

So you can imagine my chagrin, neigh, my sheer horror, when I publish mistakes on my own website! I do my best to proof read each post before publishing it, but inevitably I will miss a typo here and there and before I know it, voila, it's out there, flapping in the wind, for all the world to see. It's not pretty. These things never are.

We won't even start on my grammar. I use far too many commas, inserting them willy-nilly throughout the posts, much like a slight pause in a conversation. My liberal spattering of bold and italicized text is borderline abusive. Run on sentences? Brutal. Oh, wait! We weren't going to do this. Let's move on, shall we?

Now normal folks, like you, (I told you it was bad!) reading this are probably wondering, "Why in tarnation is this woman going on about her typos and laughable grammar?!"

I'm getting to that. Patience, grasshopper.

Today at the office, I was telling someone about the giveaway I'm having this week right here on this blog. Wanted to give my new co-worker a chance to win some yummy java. Ok, fine. Maybe it was a bit of shameless self promotion and even a teeny bit of brown-nosing, but hey, what's wrong with trying to play nice with the co-workers?! Hmph. I make no apologies for my actions. Deal with it.

My point is, said co-worker was quick to point out a big, fat typo on a previous post. Ugh.
I think he forgot that I'm the QA person, and he's the developer. Which means? Anyone? Anyone? Bueller?

Yep. I'll be the one testing his code. MWAHAHAHA ! (I know. Not a word. But it really should be, 'mmmmkay?)

Here's to typos, bad grammar, and other such horrors!

UPDATE: Shortly after posting this, a friend on Facebook kindly pointed out that I'd misspelled "grammar" all over this post! (Hanging my head in shame.)
I have since corrected this nasty snafu. Thank you for playing my game.

Share