Thursday, September 1, 2011

Stacey v. Technology: Google Maps

Of all things I learn quickly, one of the few is technology.  I don't often lose battles with computer issues unless the computer crashes entirely.

Husband bought us new Androids last fall.  Very exciting times for us as we were both upgrading from standard flip phones.  It didn't take too long for me to adjust to the touch screen and figure out which apps would be most useful for my every day life.  I was a proud owner of a smart phone, and I knew how to operate it. 

One of my favorite apps on my smart phone is Google Maps.  I get lost in parking lots so having the navigation system integrated into my phone was a godsend.  I try not to rely on it more than I need to and have even gotten into the habit lately of just reading the directions in my driveway and trying to find my way to my destination with as least interference from Google Maps as possible.  It's been fun.

Today I had to travel a ways south.  I knew it wouldn't be a tough drive.  Annoying because of traffic and never-ending construction that goes on in Cleveland, but nothing crazy.  I pull up Google Maps: 1 HR. 03 MIN. it is telling me.  Off I go.  I end up seeing a ridiculous back-up on 271N while I'm headed down 271S.  I thought to myself, Man, sucks to be those people.  I hear on the radio that there was a car fire and one lane was closed.  Ick.  I continue on and successfully only use Google Maps when I get closer because I was driving through streets of houses while looking for an office building, which is very misleading.  Google Maps clearly pointed me in the right direction, which I was actually on, and I was early, as always.  I love Google Maps.

I have a one-hour long deposition that goes well.  I go back to my car, and just to be safe I check trusty old Google Maps for my route home: 1 HR. 34 MIN.  Are you out of your mind, Google Maps?, I think.  Why in the world would I be sent on a route 30 minutes longer than the original route?  Insanity.  So I just head back the way I came.  Easy enough, right?  I am sitting at a stop light and update my map.   Only 1 HR. 24 MIN. to go.  I check and it seems the route is the same I came.  I mean, there is NO WAY the car fire mess is still an issue.  It had been a solid two and a half hours since I passed it, and much more time since it actually happened!!  No.  Google Maps is on crack.

I continue on my way.  I am headed 8N and I pass 77N.  I think for a split second that I know how to get home via 77N, maybe I should just jump on 77N.  No, no.  Google Maps always picks the shortest route.  Even if it was the car fire mess, I would just keep updating my map because it could just be slow and behind the times.

All of a sudden, as soon as I start to merge onto 271N.  BRAKES.  Nothing but brake lights.  I have nowhere to turn!  Nowhere to go but foward.  Dammit.  There must be traffic or an accident.  It's now been about three hours since I initially passed the back-up from before. 

So now I am the a-hole creeping into the left lane because the right lanes keep ending because, like, 16 freeways merge onto 271N at this point.  We're going a whopping 10 mph at best.  I'm fiddling on Facebook and cursing Google Maps for sending me this way.  I decide to update my route with no freeways!  Genius!!  1 HR. 56 MIN.  Seriously??  I've been travelling for 45 minutes already and I'd have another two hours if I took the next exit?  Screw that. 

Then I started people-watching.  Some guy is weaving back and forth in one lane.  Weird-o.  Must have been trying to see what the hold-up was.  Good luck, buddy.  Then he swerves back and forth for a little longer and just shoots into the shoulder lane!  Really?!  And I thought I was being a dick!  Whatever.  I see another car, then a motorcycle drive down the shoulder to pass the time.

I finally get to the hold-up.  Car fire?  No.  SEMI-TRUCK FIRE.  How did they mix up a car and a SEMI?!   

When I finally got home, I checked to see how long it took to return.

1 HR. 34 MIN.

Stacey: 0 v. Technology: 1

No comments:

Post a Comment