Showing posts with label google. Show all posts
Showing posts with label google. Show all posts

Wednesday, May 6, 2015

the end of the road

Veo al final de mi rudo camino, que yo fui el arquitecto de mi propio destino. 
I see at the end of my rough journey, that I've been the architect of my own destiny.
- Amado Nervo


I feel pretty comfortable driving in Mexico. Actually, I feel comfortable driving just about anywhere. And I'm almost always the driver. Rental cars don't bother me. I like getting to test drive different cars. Every time I've gone to the Yucatan to volunteer with Proyecto Itzaes, I've rented a car. And the only mishaps I've had have been regarding the actual renting of the car. No matter what time you arrive, the process of filling out the rental paperwork and getting to drive away in your newly rented car takes several hours. I don't exactly know why, but it just does.

This is how much Mexican country-side I typically drive through

But then, while driving through the Yucatan last month, my car rental luck ran out. A rock hit the car's windshield. And at the very most top part of the windshield, half on the plastic that seals the glass to the roof. But just low enough to embed itself at least partly in the glass. But just high enough that I didn't know that was the case. However, once the crack started to spread in a long line down the window, I realized exactly what had happened. In the five minutes it took us to get home the crack had successfully run the entire length of the windshield. And it was only getting longer. I panicked. I didn't know what to do. This had never happened to me before. Not even in the US. I once had a windshield bashed by some thugs with baseball bats in Potrero Hill. But never a rock in the windshield. I guess it was about time this finally happened to me.

I quickly tried to decide what should I do; get an estimate from a nearby mechanic and pay for the repair before the rental was due back? Or break down and call the rental car company, knowing it would be a long painful process. I knew I couldn't drive the car again, so I had to do something. I called the rental agency. They were so nice. Surprisingly nice. With amazing customer service. I had never experienced this before. I was still skeptical this would go off without a hitch, but the nearest car rental depot (not the one we originally rented from) would send a driver out to our home, bringing a replacement car for us. It sounded too good to be true. Especially because I had to head to a village for an appointment and wouldn't be home for a few hours. They assured me they would sent someone in a few hours. It would all work out.

When we go home from Dzemul, there it was; a brand new, identical but red (our first car was turquoise) rental car, along with two patiently waiting agents. Though I had arrived only five minutes past my scheduled time, it seemed like they had been waiting for quite a while. When I asked the rental agents the length of their wait they politely responded that they had been there for an hour. Yet they didn't seem restless. Perhaps they were enjoying the sun, sand, and ocean. Yes, they assured me, the windshield will need to be replaced. ¡Que mala suerte!

So there we were, new and improved rental car at our disposal. Which was convenient. Because we were planning to leave the beach, drive south a few hours to my favorite ruins (Uxmal), and many hours later arrive at Bacalar, situated just south of Playa del Carmen. On the other coast. It was about a six hour drive but we planned to make it into one long day of driving and sightseeing along the way. We set out very early in the morning.

And we were driving along just fine. Highway driving in Mexico is pretty self explanatory. The highways are nice and new, although mostly two lane. Since the speed limits are high (at least 110 kph), it's completely normal to pass slow moving vehicles. When the roads aren't curvy or dangerous. I'm a pro at passing cars on single lane Mexican highways. It takes a lot of patience, but you can always eventually pass.

Which is why I was very perplexed when I quickly came upon seven cars going slightly slower up ahead of me. They were clearly waiting to pass a slow moving van. Wow, I thought, they must have some serious patience to wait so long to pass. But in time, I knew, we would all make it safely past the slow moving vehicle. We had many many more hours to drive; we couldn't exactly afford to drive so slowly for a very long time.

None of the cars ahead of us were going particularly slowly, nor were they inching to pass the slowest car at the front of the line. I thought about it for a split second before heading on to pass the cars myself. There was no use in waiting, after all. Except that the roads through the Yucatan can be windy. So I wouldn't have enough time to pass all seven cars at once. I started passing them two at a time. I passed the first two cars. They seemed content to be where they were. Hmm, I thought, maybe they're driving in a line. I wonder why. I can't be sure, but it doesn't seem as if they are trying to pass the front car. So I quickly passed the next two cars, and then the next two cars. Eventually I was right behind the slow moving van. And that's when I saw it. The giant picture of the Virgin Mary staring right at me. It was posted conspicuously in the rear view window.

It looked like a regular covered truck to me

Because it was a hearse. Carrying a corpse to its final resting place. And we had placed ourselves prominently first in line at a funeral procession. I swallowed hard. Was what I had been doing wrong? Was I not supposed to weave in and out of a funeral procession? Was there some tell tell sign early on in this process that I had completely missed? Or did I not know what was going on until just that moment? And once I realized where I was, was it wrong to try to head out and pass the hearse? So I did just that. I waited for a clear view of oncoming traffic and sped over and passed the hearse. What else was I to do? They were going far and long; but they were also going slow. They didn't need me embedding myself in their mourning processional.

So we drove on. And on and on and on. We were going to take Highway 184 from Uxmal to the Caribbean coast. Highway 184 would meet up with Highway 307, the main road from Cancun all the way down to Belize. We'd hit into 307, turn right, and drive a few miles down the coast to Bacalar. We'd been driving for hours, but we started passing the signs telling us that 307 was just ahead.

According to Google Maps, Highway 184 bisects Highway 307

Which it probably was. But we'll never know for sure. Because we never merged onto Highway 307. We never go that far. Instead, we drove on Highway 184 until the road just ended. That's right, the highway just stopped. So we stopped. And then we looked around. There were people coming towards us on foot. They were walking over with suitcases and backpacks. They were getting into taxis. They were driving away, the only direction the road went - back to where we had just come from.

I found a narrow place to turn around. And then attempted to ask a taxi driver for directions. He and his friends laughed as us. The road didn't intersect with the coastal road, at least not yet. The road would be built, someday. I couldn't believe it. The maps/gps indicated we could drive right on through. Except that we could see right in front of us; there was no actual road. Only a parking lot. The taxi driver drew us a map; we'd have to backtrack for a while, then turn off and pass through three villages before finally hitting 307, south of where we were. But we would hit it eventually. In only a few hours time.

So then I asked about the people coming towards us, from what appeared to be the other, coastal side. No one could answer me. Apparently there was an airport some place nearby. But that didn't explain the cars and people I could see ahead of us, driving inland from the coast to meet us. Except we wouldn't meet. Because there is a strip of highway missing. That just hadn't been built. Instead of continuing on the way we had planned, we had made it to the very end of the road. So we turned around, drove back back, turned off at a random desvio, and ended up in paradise. Because that's what happens in Mexico. Paradise is always just one wrong turn away.

Bacalar

Sunday, February 8, 2015

charcot marie foot

"Symptoms, then are in reality nothing but the cry from suffering organs"
-Dr. Jean Martin Charcot


Ever since I can remember I've suffered from mid-sleep charlie horses. If you're not familiar with the term, I get cramps in my calves while I'm asleep. Yes, I said while I'm asleep. In complete and total pain is a very jarring way to wake up.

So you can imagine my surprise when, halfway through my very first marathon, both my calves started actively cramping. Calf and foot cramps, until that point, had been reserved for laying down and/or sleeping. But instead I found myself running (for over two hours) through the active cramping in my lower legs. When I finally finished the race, medics put ice bags on my calves. While that helped relieve the pain a bit, removing the ice resulted in two of the worst cramps of my life; charlie horses so painful I dropped to the ground, screaming and swearing uncontrollably and scaring the medics who had circled around me and my family. All I could think was, "I haven't had a calf cramp this bad since I was fifteen years old." And I probably hadn't.


Running a marathon (and smiling) while my legs are actively cramping

If you've never suffered from a calf cramp (or in my case, many many calf cramps), you are lucky. They are painful. I'm never sure when they'll start, I do not know how best to ease them, and I absolutely do not know how to prevent them.

I wasn't the only person in my household with this mysterious midnight pain. My brother also suffered from mid-sleep calf cramps (and was the one who first used the term "Charley horse" and taught me its meaning). Most of my memories of Dave's calf cramps were during his high school years. Despite being two and a half years younger than Dave, we would both suffer leg pain at the same time, often during the same night. While I would always choose to instantly grab my leg (or legs) and try to massage out the cramp, Dave chose another treatment; he'd try to stomp them out. Dave would suddenly jump out of bed and start stomping down on his leg. Once he was satisfied he'd gotten the cramp out, he'd fall right back onto his bed and into sleep. The number of times I woke up to the sound of Dave stomping his leg are too numerous to count. It was a typical occurrence in our home.


And clearly I still continue to get these cramps. What's interesting to me it that there is very little known about WHY I get searing pain in my calf muscles that wake me up. I have been told about any number of possible causes of my distress, but none of them make any sense. Everyone seems to offer up an unsolicited solutions to this problem. First up, lack of potassium. Sorry friends, but I am absolutely 100% not potassium deficient. It's not the culprit. Trust me; I have my potassium level checked every six months (an unrelated concern). More potassium will not eliminate my cramps; I could eat all the bananas in the world and not get better.


The suggestion that dehydration is to blame for my charlie horses is much more believable. I don't drink enough. I try, especially with all the running I do. But I am always thirsty, most especially in the middle of the night. So I drink a lot. And I pee a lot. And I drink a lot more. But I never feel hydrated.

During my post-marathon calf cramp fit, my mom offered up some life changing information; calf and foot cramping is a symptom of Charcot Marie Tooth disease. Charcot Marie Tooth (CMT) comprises a group of disorders passed down through families that affect the nerves outside the brain and spine; aka the peripheral nerves. I know, it's an odd name for a foot disease (actually it's foot and hand). But it's named after the three doctors (Charcot, Marie, and Tooth) who discovered it. Several members of my family suffer from CMTX, the x-linked form of the disease.

After the marathon I had truly reached my breaking point. My feet had been hurting so bad for so long I had to finally see a podiatrist. Four days later I had the official diagnosis; I have Charcot Marie Tooth. I wish I could say I'm not devastated. But I am. Why else would I have avoided the podiatrist for twenty years? Up until last week I had still hoped I'd hear, "new shoes will fix your chronic foot pain." But they won't. Foot pain is a part of me. Most of the people close to me know my feet hurt every single day. Some days I run with the pain. Other days I run through the pain. But most of the time, I run despite the pain.

Packing for a marathon includes lots of 2nd skin bandages

So what does this mean for a (now official) marathoner? Of course I had to ask my doctor about the running. Would I have to give it up? The short answer is no. With lots of orthotics. And maybe surgery. But first orthotics, lots and lots of orthotics. And new shoes. And stretches. And special exercises. And the frozen water bottle under the foot trick that I promise alleviates plantar fasciitis.

Many people prefer to keep their CMT on the down low. In their defense, the symptoms can become very dehabilitating, especially for men. But I'm putting it out there; I am a marathon runner with CMT. Because I want you to know. And to understand. If we're out walking together, I'd like you to slow down. And when we're out on a hike, the pain might become so unbearable for me we have to either stop for a while or immediately turn back. But the pain won't stop me. I will continue to go out and run. And maybe even hike once and a while. And maybe, just maybe, someday I'll run another marathon. After all, "few things in life match the thrill of a marathon." (Fred Lebow, runner and founder of the NYC Marathon). Mr. Lebow, I completely agree.

I'm already thinking about my next marathon...

Friday, October 17, 2014

homework

"To steal ideas from one person is plagiarism; to steal from many is research.”
― Steven Wright

I recently began applying for jobs, and I've gotten pretty good at it. I have gone through all the motions, from meeting with a career counselor, to networking myself through everyone I know (and may know) thanks to LinkedIn. I have applied for too many jobs to count, but I'm getting responses. Over the past four weeks I have averaged four interviews every week. I'm talking about all kinds of interviews, from informational to in-person.

This is a very time consuming process, mostly because each interaction requires scheduling, research, and time. I take each interview pretty seriously. Until I don't. Because, inevitably, something in the process will rub me the wrong way. No longer being interested in the position, not being able to come to a consensus on salary, or not wanting to work with the staff are all very solid reasons not to take a job. I have used all these reasons to withdraw my candidacy from consideration. But I have also come across one more reason to run away from any given job opportunity. And that is when I'm given too much homework.

I know it has been a few years since I've set out to seek full time employment, but since when has it been okay for employers to take advantage of candidates? I am actually shocked at the amount of work I have been asked to complete throughout various stages of interviewing.

https://jobmob.co.il/blog/funny-ikea-job-interview-cartoon/

Two recent instances have stuck in my craw. The first was an interview granted with a wonderful educational organization. Before I even spoke to anyone about this position, I was sent a letter (in the mail) with two items. One was a parking pass for my scheduled interview date and time. And the second was a request to give a one-hour presentation to a board of representatives at the organization. The presentation topic? A complete proposal for a multi-year $250,000 grant, based on the type of programming the organization runs. But I didn't know what type of programs the organization runs. It's not apparent on their non-existent website. I hadn't even spoken with anyone at the organization about the position, let alone what would be beneficial to it. I was extremely frustrated.

But that's not what upset me the most. The most ridiculous part of this assignment was for me to do the work for the organization. If I were to write an incredible multi-year grant proposal under any other circumstances, I would be appropriately compensated. Actually, I have been compensated for this type of work for over ten years now. I am not going to give away my secret grant-writing formula for free, no matter how much I want the job. In the end, I called the organization, left a voice-mail, and bowed out of the interview process. Mostly because I don't want to write grants full time, so it's clearly not the right position nor the best fit organization for me. But also because I was not going to do the work they inappropriately asked of me.


 http://www.snotm.com/2011/05/69-never-work-for-free.html

The second homework assignment I received recently was to plan an event for an organization I had been currently interviewing with. I understand the idea of raising the expectations for a candidate in a second round of interviews. But asking me to present my complete event proposal for an event that will be happening early next year is just an absolute abuse of power. Again, asking for all my ideas and taking them to plan an event is not an ethical way to work. It's not how I work. And I wouldn't work for an organization that treated others this way.


http://www.statusant.com/

What is acceptable is the following: arrive at said interview with a few concrete ideas to discuss, Then, the organization hires me, and I complete said ideas. Sounds like a pretty awesome plan. On the other hand, for me to present to the organization's entire staff for over an hour, lay out how I'd secure each vendor and contact each vendor for an upcoming event is the very definition of work. Again, I'd expect to be compensated. This is true event planning/consulting work. And it is usually accompanied by a large amount of monetary compensation. 

In the end, I wanted the position at this second organization, so I did the work. I presented my event plan, complete with budget templates and event checklists. But the truth is that my heart wasn't in the proposal. No longer did I hope for a job offer at this organization. The idea of free labor is what I expected to provide over twelve years ago when I was an intern. A decade later, I've got two degrees and a world of experience. 



http://filmmakeriq.com/2012/04/do-not-work-for-free-for-exposure-the-wrap/


Let me make sure I am clear about one thing: I am not saying every time I use my skill set, I should be compensated. I'm not saying that at all. Anyone who knows me knows that I use my knowledge, experience, and passion for good. I am currently writing grants, raising money, designing websites, planning events, and even training a student on the grant-writing process, all for free. I am a volunteer. I am happy to help. But there is a very distinct line for me between being a volunteer and being taken advantage of. When I'm working, there is the expectation of monetary compensation. When I am volunteering, I receive a reward of the non-monetary kind. And that works for me. But I'm not talking about the volunteer part of my life. I'm talking about my livelihood, the money I use to pay my rent, and eat, and pay the internet bill so I can afford to post this blog online.



Plus, it's not an all or nothing job interview homework mentality I'm holding. For instance, I am not against skill set exercises. One company asked me to complete a data merge and collate said data, drawing conclusions based on the data. This exercise took 20 minutes and I was happy to do it. Apparently my Excel skills passed the test, because I was asked to come in for a second interview. Score!

But what surprised me about this data collation activity was the simplicity of the exercise. Granted, I needed to use equations across multiple spreadsheets, but in the event that I wasn't sure how to do this, I could have always used Google. It is common practice for most people I know; if you don't know something, or need to fix something, or have a general question about how anything works, you get on your computer (or phone, or tablet) and Google it. Then you have your answer. I suppose a better test of my skills as a potential employee would have been to ask me, "if we asked you to create pivot tables in an Excel document and you don't know how, what would you do?" I could quickly answer, "I'd Google the question and teach myself the answer." There you go. Clearly I can learn anything I don't know how to do. I am industrious. I will make an awesome employee.

I have used this tactic before. Haven't we all? During a phone interview I actually said I knew how to create pivot tables. The night before I went in to the in-person interview, knowing I'd have to speak specifically on the pivot table topic, possibly even tested on it, I taught myself pivot tables. I know how to use the internet, a skill which will, no doubt, help me secure my next full time gig. In the meantime, just don't ask me to solve your company's issues for free. You'll have to hire me first.

Here is Forbes Magazine's approach to job interview homework: http://www.forbes.com/sites/dailymuse/2014/05/29/what-every-job-seeker-should-know-about-work-assignments-during-the-interview-process/

Tuesday, July 1, 2014

anonymous


I have been applying for jobs. And before every job interview, whether initial phone conversation or in-person, I do some company research. In the past, this has typically involved looking at the company's website, reading more in depth about the job opening/qualifications, and taking a cursory glance at the staff member listing.
But recently I have begun to take my interview preparations one step further: I search out the person I am interviewing with. I not only Google the person, find him or her on the company webpage, and check out a LinkedIn profile, but I really look into the person. I find my interviewer on Facebook, read any article written about him or her, search for press releases, and even Google image search for head-shots. I like to know who I'm going to be speaking (and possibly working) with. I have gone so far in my due diligence that once I actually predicted a director would be leaving the company (I was interviewing to be her replacement) to go on to graduate school. When I mentioned this in the interview, she said I was the second person to make that connection. I guess my behavior is pretty normal.




Which is the main point my internet research is beginning to make clear; I will find out about you. When I worked at my former company, I would search for the current addresses of individual donors who had recently moved. Nine times out of ten, I would find the donor's new address, along with how much she paid for her house, the names of her children, and the city she was born in. I know that sounds creepy, but it was all just to send out an annual appeal letter to the correct address. I did develop a reputation among my co-workers for being able to find anyone, though. But that's because it's easy to be found.
And it is now the norm. I remember interviewing roommates years ago. I'd search out each candidate on social media sites. The same thing was true with someone I was going on a date with, or even with simple acquaintances. I now try to limit my internet stalking for job interviews, as I cannot confidently enter into the interview unprepared. But we all know that being given access to someone's complete and legal name is a free pass to search out the person via Google.




I used to think that it was possible and easy to live off the grid. If you don't want someone to find you, stay off the internet; don't join any social media sites and don't give your name to articles/quotations that may be published about you. While I welcome comments on my blog posts, beware of publishing anything with your full name. You never know what I might (and will) find about you.

I just found out that "off the grid" no longer means what I thought it did; "off grid" now refers to the millions of people living locally. Off Grid is one, among many, such website that includes various bloggers giving tips on how to live locally. Except in the state of Florida, where living off grid illegal. All homes must now be connected to a utility grid. This means all residents must be connected to a system and pay into this system. No more hiding in a cabin the woods, or not having a physical address to receive mail and bills. Everyone leaves a footprint. And there are millions of us on the other end, tracking it.

Not to scare you. I only use my internet stalking powers for good. To get to know you before meeting you and trying to convince you to hire/date/live with me. This is completely normal behavior; and actually, almost to be expected. Almost.


So while there is a fine line between cyber-stalking and conducting research, every single job search website lists researching your interviewers by finding bios and social network links as a "must do." Idealist, Monster, and Indeed specifically recommend, "You may find bio pages or press releases that give you insight into their most visible activities at the company. Then look to LinkedIn or do a general Web search to get some more background information about them." That looks like a green light to continue preparing myself in this fashion for upcoming interviews. But perhaps I'll put my default to research everyone mentality aside. And let real life people show me who they are.

To read more about acceptable job interview preparations, check out: http://career-advice.monster.com/job-interview/interview-preparation/interview-company-research/article.aspx


Monday, May 5, 2014

only the locals know



Get a bicycle. You will certainly not regret it, if you live. 
~ Mark Twain 
 Taming the Bicycle. 1884

I'm back in my city of San Francisco and I'm hitting the road again. In true San Franciscan style, I'll be cruising the Avenues on my bicycle. San Francisco weather makes bike riding a fun, yet chilly, activity. I always have to layer up, especially if I plan to bike home after sun down.

This winter/spring has been brutal for California farming, if not perfect for bike commuters such as my beau. It has rained once during the past three months. We Californians are in a drought. A serious, serious drought. So much so that I ask the skies for rain on a daily basis. But every morning, when I look out the window and see the shining sun, I can't help but think, "another sunny day? Oh well, I may as well take advantage of the weather."

So I hop on my bike. But before I can actually go anywhere new, I check the internet. For some suggested bike route options. I typically grab my handy smartphone, open Google Maps, and enter in where I want to go (this activity is reserved for distant locations outside my typical biking comfort zone). I hit bike route and voilà, I am given the suggested route. So, I head off. I love bike rides across town.

Except that I almost never follow the suggested bike route. I find that it is never the best/easiest/quickest/safest/flattest route. So why even look it up at all, if I'm going to learn to navigate the streets myself? Force of habit, I suppose. I do rely heavily on Google Maps for driving directions. But whatever bike route Google Maps does tell me to take is not the one I end up taking. 

When it comes to navigating the streets of San Francisco, regular bike riders know best. I can honestly say I know the best routes. I knew the wiggle long before I even had a smartphone. I am glad the city has taken to painting in green bike lanes and arrows to help novices learn the flat routes throughout the city, but even they don't always get it right.

Almost every time I ride my bike through San Francisco I notice the sharrows. Sharrows are exactly what they sound like; they are "share arrows" meant to let cars know that they must share the lane with bicycles. Sharrows also alert bikers that they can and should use this street (as opposed to the major thorough-way one block to the left or right of each particularly painted street). I feel safer on sharrow or bike lane marked streets. But more often than not, I don't choose to take these streets.


Cars are notified to share the road with bicyclists

Because sharrowed streets are not necessarily flat streets. Or through streets. There is simply always a better route or street to take. Thank you City of San Francisco for painting arrows on blacktop, but your arrows are useless. Or at least should and will be ignored by us locals. I rely on what I know about the city and its streets to get me from start to finish, every single time. I go where the locals know to go, and I choose every street I take based on experience on these streets; not by any map, painted arrows, or bike lane. I know where to go because I have been there before. 

Some day I hope our friends at Google think to ask us, "what is the bike route you'd take from ocean beach to the ballpark. Or from Pacific Heights to the Embarcadero" and then edit their mapping software to reflect these best routes. Until then, we bike riders already know the best way to go. So we hop on our bikes and head across town.