Posts Tagged ‘Twitter’

Livetweeting a Road Trip and a Snowy Weekend Away

This weekend, I decided last minute to join my parents on their trip to Mammoth. Evan was out of town in Washington, DC, and I didn’t have much planned, so Friday afternoon, I packed a back and my parents came to pick me up.

The drive was particularly long. My dad put on a 3-hour “Climate War” radio program. There was a huge backup on the 405 and the 5 — it took us two hours to reach the 14 from my place when it usually takes closer to 30 minutes. And once we were done listing about how the world will devolve into utter anarchy and nuclear winter, the remainder of the drive was filled with a mix of Peter Paul and Mary, Bette Middler and driving 40 miles through a snow storm with chains on.

Well, to pass the time and document the experience, I was on Twitter. Some of the highlights:

Oh man, The Rose is on. Don’t want to admit it but I’m compelled to sing along “some say love…”

Apparently iphone predictive text doesn’t want to hear kum ba ya either. Its first option: kim bad ya

“Five hundred miles, five hundred miles…” now this song is speaking to me

Now this song is baffling: “Stewball was a racehorse… He never drank water, he only drank wine”!?

Goodnight Irene? How’d this make it on? Seems random. Do think they’re telling us to hurry up, get there and get to bed.

So much snow coming at us we’ve got a warp speed effect going on. Ridiculous speed!

We finally arrived after about 8 hours — it normally takes 5. There were many more updates, but you can visit Twitter to read the rest. Sorry about the spelling — I learned that the iPhone predictive text changes things without me realizing a lot, and I’m also apparently sloppy about checking my updates on my phone.

Saturday we went skiing/snowboarding, though the top of the mountain was entirely in a cloud. We only did one run up top before deciding it was too stressful to navigate the white-out, so we spent the rest of the day on the lower half of the mountain, enjoying the deep, new snow. We didn’t stay out too long because it started getting windy and the snow hitting our faces was getting painful, so we headed back in, climbing back up to the condo behind the Austriahof — always a fun little adventure at the end of the day.

That night we went to Nevados for a delicious dinner. The bread was nice and hot, I got a yummy pasta and vegetable dish, and we shared a deconstructed tiramisu in a chocolate cup for dessert. That was the best part. I couldn’t even snap a picture before my dad had started taking it apart.

Today was sunnier, but a lot windier. I didn’t head up to the mountain, and my parents only stayed out for a couple of hours in the morning. Thankfully, the drive home was a lot easier than the drive up, and it only took 5 hours to get back to my place.

I didn’t mean for this to become the all Mammoth all the time blog, but be warned: I’m heading up next weekend, too. I’ll try to post about some other things, too. I promise.

Weekly Reading: Tech, Tech, Tech, Chocolate!

I’m back from Florida and have plenty to share. I’ll be putting up the pictures and posting about the trip soon, but for now I have lots of new stories out on these fair interwebs. Not presented in the order the headline would lead you to believe, let’s start with dessert…

First, there’s my SpoiledinLA Holiday Gift Guide Review of Madame Chocolat, which you already got a little preview of.

Then there are two AllBusiness articles: one on web browsing tricks to help you speed up your surfing, and another on whether a netbook is right for you.

And then there’s a piece I did for Entrepreneur.com about the unwritten rules of social networking. I interviewed Joel Postman of Socialized PR about The Unwritten Rules of Social Networking, from how to interact with clients to the best strategies for growing a strong following. We also discussed whether to hire a community manager and how to balance your personal and professional identities. Thanks, Tomdog, for sharing one of your social networking blunders, and thanks to everyone else who shared their social media horror stories via Twitter and LinkedIn, too.

Weekly Reading… and We’re Off!

We’re coming to the end of our last full day in London, and it’s been action-packed right up until the end. Evan’s been busy finishing up Hellboy II — go see it in the U.S. July 11 and in the UK August 20 (or July 13 at Somerset House) — and I’ve been busy redesigning the Write-Communications site (with help from a great Revolution theme and lots of WordPress plugins), doing work for Workology and still trying to get a bit of writing done.

The weekly list:

On our trip we should be making occasional updates to Twitter (me/Evan), Facebook, this blog and Evan’s photo site, so stay tuned. Now off to do some more packing — we head to Egypt tomorrow!

Technical Problems Are No Fun

This is more a little rant about problems I had yesterday than what’s going on today, but I don’t know if anything has really been resolved, especially with my biggest issue: My keyboard keeps randomly freezing. The problem doesn’t seem to be tied to any specific program I’m running, and the more I research it, the more it seems to be an issue with Leopard, which I installed last week. I’m hoping for a fix soon because it’s really quite a pain to have the whole keyboard freeze up and not know when it’ll return. At least the touch pad still works when the keyboard is out.

I was also having some issues with Google Reader yesterday. I was trying to clean up some feeds I don’t need anymore, but it kept giving me errors midway through the cleanup process. I was so annoyed, I even downloaded a different feed reader, Sage, but found it lacked some of the GR functions I really like. So today it was back to GR and thankfully my cleanup worked. Back to business as usual, though even with my big cleanup I still have 1000+ unread items. Thank goodness for the “mark all as read” button.

And on top of all this, I also had some Twitter issues. I made a few posts that just never showed up. My internet was working just fine, so I don’t know what the problem was. Seems to be fine today, though.