WillUrquhart.com

I've stopped posting here, using WillUrquhart.com now.

Blue Ridge Parkway Journal Chapter 1 and 2: The Back-Story, "Hills are Good!"

In the summer of 2011, I will be riding from Front Royal, VA to Asheville, NC along the Skyline Drive and Blue Ridge Parkway. Periodically, I will be posting new chapters of a journal detailing the trip. I have no goals beyond keeping a detailed, personal account of my first, long, self-contained bike tour. This is the first installment.

Chapter 1: The Back-Story

It was one year and a few months ago that I bought a bike for the first time in about a decade. I had barely ridden one since getting a drivers license, but I had put on weight, something new and unusual for me. All my life, my metabolism tore through even the most ridiculous of diets. I could have lived off of dipped bacon in mayonaise for days without putting on a pound. But alas, the mix of a weakening metabolism and a less-active life (partly due to changes in work) had left me more out of shape than ever before. I was 25 and for the first time in my life, had to consider what I eat and how much exercise I get.

I started working out and jogging. I hated jogging. I had always hated it, but over a decade of smoking had done a number on my lungs. I could jog, and I could keep it up enough to get a good workout, but I hated it. I am not sure what it was, but something reminded me of young days riding bikes all over the city, on trails in the mountains, and along the C&O Canal. I decided I would get a bike again.

The store had one bike that was right for me. A Rocky Ridge, Marin mountain bike. This was the type of bike I could easily ride around town but was rugged enough for even the toughest of trails.

I rode the Canal as much as I could that fall. I would not even ride the streets out of fear that I was not in good enough shape to handle the hills in DC. The canal, however, is flat, gorgeous, and full of memories. On my first trip I relocated the former rope-swing, the tree having been cut down years ago when a girl hurt herself there. I almost rode past it, not noticing the SUV sized trunk jutting out towards the water, overgrown with smaller plants.

Once I felt my lungs and legs gradually getting back in shape, managing the ride better and better, I decided to try riding from my house rather than driving to the drop point on the canal. It is only one mile and very easy going there, but coming back is basically all uphill. I remembered that being one of the more difficult hills of my childhood, and one I walked up plenty of times. I had to take two breaks on my frist attempt to ride up the hill (my first attempt since getting the Marin that is). The next time, one break. From then on, I have yet to need a break on that hill. Looking back, that moment is where I would say I turned a stone and actually began to get back into shape.

By the time fall was coming to an end, I felt comfortable riding the four or five miles to the office up some long hills. When spring came around, now 2010, I was eager to put some miles beneath me. April presented me with a great opportunity to do just that as I was planning a drive across the country to meet my best friend at his place in LA, then off to Vegas for his bachelor party! VEGAS BABY!

This was my first cross-country drive. I have long been well-traveled, but at this point in my life, the furthest west I had driven was Missouri. I planned a route that took me along the southern part of the country while heading out west, and up along the north while coming back home. The majority of the trip was spent on roads I had never driven and states I had yet to visit. I think I hit 19 states total, 11 or so for the first time.

Like anyone would, who spends as much time online as I do, I started googling. "Cross-country driving tips", "guides for driving across the US", and so on. Planning the trip was exhilarating, dreaming out routes and adventures along the way! I decided my "themes" of the trip (a tip from one of the many search results) would be twofold: 1) New. As in new states, new sights, new people. 2) Biking. My bike would come along for the ride, hanging proudly off the back of my explorer, and I would try to ride it as often as possible. In my googling, ironically not for the biking sections of the trip, I would first learn the term "Bike Touring", which I will talk about later on.

When I arrived in Little Rock, the first stop of the trip, I tried to stay at a hotel near the places I wanted to see so that I could just ride all over. A mix-up with the address left me a little too far outside of town for that, so I drove into town in the morning, parked, and took out the bike. I rode to the Clinton Library, the Heifer International Headquarters which is one of the greenest buildings in the world, and took a ride along a bike path by the river. I immediately approved of my biking theme. Biking around a city provides the tourist with a more comprehensive memory of the streets, the buildings, and the natural environment surrounding him or her than one would find driving around. One gets a better picture of the distance of blocks, the hills, the wind, and the people.

From there it was a mad dash to the Grand Canyon, after stopping to pay respects at the Oklahoma City Bombing Memorial the day before the anniversary and one night to sleep in Albuquerque. It was an amazing drive that took my breath away. I will never forget the feeling while sitting on my cooler, eating a chicken salad burrito in the parking lot of a gas station in what seemed like the middle of nowhere, Texas, surrounded by nothing but wind, desert, and an occasional passing car.

Roughly half an hour after leaving Albuquerque, I realized that I had forgotten to fill up on gas. I had about 70 miles until empty, enough to make it back if needed. But backtracking when you are trying to make it to the Grand Canyon before sunset sucks. I whipped out my new Droid, pulled up the Where app and searched for gas stations. It brought up two, one behind me in Albuquerque, and one in a town called Canoncito that I had never heard of before. I decided to risk it, taking an exit 10 miles ahead with no sign to indicate a gas station and nothing but desert and hills in sight. Five, six, seven miles off the highway, steadily getting close to the point where I need to turn around if I want to make it back to Albuquerque.

There it is! "Yes!" I shout aloud to myself. Canoncito's Gas. I go in to pay, no credit card slots on the old gas pumps. I told the owner of my close call with an almost empty tank. As it would turn out, he had been driving east some twenty years ago, when he and his wife ran out of gas not far from where I would have had I kept going. Only they lost gas at about 3:00am, not 10:00am. It was dark all around. When you drive through the desert, all you can see is the road ahead of you. A black abbiss surrounds the stretch of highway, only rarely broken by the lights of a gas station or small town.

A man with a pickup truck had helped them out that night and long-story-short, him and his wife ended up staying there permanently. Now the family, including a couple children, owns that gas station.

After exchanging business cards, chatting a bit, and taking a few pictures, I got back on the road, happy to have met Francisco.

I arrived at the Grand Canyon with a few hours before sunset. As luck would have it, it was National Parks Week meaning that entrance and parking fees were waived! A good omen, no doubt. Just as soon as my bags were in my hotel room, the bike came off the car and got a quick cleaning. I rode to the visitor center, hoping to get some help picking out a good bike trip. They were a little help, but not much. I probably should have checked BikeForums.net or crazyguyonabike.com, but I was not completely aware of the wealth of information available at those sites at the time.

Anywho, I rode out to see the canyon for the first time. The size of it is continually described, but you just cannot be prepared for the sight of it. After gazing out, I decided to tool around on the bike. I noticed that, unlike in the DC area, the trees were so far apart you could just ride through them without any trail. I hopped off the road, keeping a keen eye on my Droid's google maps to steer myself back to the hotel. I fell once, the first fall I had taken since getting back on a bike. A small scratch on my knee only brought a smile to my face. Here I was, charting my own path through the trees ducking and dodging the branches and limbs as they whizzed past my face. This part of my life had been absent for some time.

After an early dinner snack, soup heated up on my camping stove, I leisurely rode back to the canyon to watch the sunset. I chose to spend two nights, giving myself a full day to enjoy the area. I found a fun looking bike trail nearby, the Arizona trail.

The next morning, I got up and began driving towards the trail. As I approached the "parking lot", or dirt space, at the entrance, it was clear that it would be all mine.

"Perfect." I muttered to myself as the car came to a stop in the empty lot. The ride was, and still is, some of the best mountain biking I have done since getting this bike. All alone on a beautiful trail that looks out away from the Canyon. Again, I fell once, this time a little harder than the day before. And again, I smiled. A couple more scrapes for me and some dirt for my camera, but no real damage for either. I also got the chance to test out another app for my Droid called My Tracks.

My Tracks uses google maps and your phone's GPS to track you when turned on. Once you stop recording the track, it spits out all kinds of useful information such as average speed, average moving speed, elevation changes... etc. After stopping to have lunch before heading back to the car, I started recording. I didn't want to risk killing the battery on the ride out so I decided only to track my ride back. Here is the map it gave me:

View Arizona Trail in a larger map

Thoroughly pooped, I went to sleep early that night and woke up slowly the next morning. I was in no rush to leave early since I was not due to show up in LA until the next day. I decided I would drive to about an hour outside of LA and find a motel 6 to crash at.

Aside from a ride or two around LA to get food and whatnot, I got one more chance at some real riding. While in Utah, I hit up the famous Moab. There is an area there of rolling slickrock, affectionately called a bikers playground. No marked trail, just miles of smooth rolling stone with plenty of dips and natural quarter-pipes. A ferocious wind made climbing the mountain of stone difficult, but riding down with the wind at my back exhilarating.

Everything I have told you so far was an effort to set the stage and give you a sense of where I was coming from when I decided I wanted to try out this "bike touring" thing I had read about.

You will recall that I mentioned, earlier on, that it was during my prep for this cross-country drive when I first heard of bike touring? In my googling for touring tips, the search "solo touring" produced one very unexpected the result. The first search result too. It was a journal at crazyguyonabike.com. Welcoming distractions as I do, a sometimes healthy, sometimes unhealthy mix of curiosity and ADHD, I perused.Almost instantly I was attracted to the notion of self-contained bike touring, where you carry everything you need, only rarely stopping to refill food supplies or fix a bike. One adventure at a time, I told myself. But it was clear to me that night that bike touring was in my future.

There are countless reasons I can list for why my heart leapt up that spring and why the thought of bike touring has continued to nag me over the last eight or nine months. It seemed like a brilliant challenge to motivate me in my efforts to get back in shape, not to mention the good exercise of touring itself. It combined biking with another childhood love of mine; camping. It was a chance to disconnect myself from the the city, from technology, and most importantly, from politics. It would fill me with stories, move me with the views of nature, and teach me more about myself. It just sounded, and still sounds, fun.

Over the summer, I read more about bike touring and started researching routes. By mid fall, I had chosen the path, from near DC all the way to Asheville, NC where my oldest friend is living. I plan to ride along the Skyline Drive and the Blue Ridge Parkway (BuRP). It was clear that I would not be ready before the weather turned cold in the mountains, and spring rarely affords me enough time off for the trip. So I settled on the summer of 2011.

As I write this, months after first choosing the trip, my interest is as high as ever. As the new year rolled in, and thoughts of new years resolutions danced in mind, only seemed appropriate: ride the BuRP. Let the real planning begin, quick open a new google doc!

Chapter 2: "Hills are good!"

That was the mantra of the journal that most peaked my interest in riding the BuRP by Victor Weinreber, "Hills are good!" The BuRP is known for its hills. Hundreds of miles of them, and only about 3 miles of flat road. In total, you climb about 50,000 feet riding along the 500 mile stretch. Dan Casey put it this way:

There is nowhere else in the U.S. where you can roll along almost 500 uninterrupted miles of breathtaking mountain scenery, with nary a stoplight, stop sign, fast food joint, strip mall, convenience store or any of the other signs of "progress" in our society. The Blue Ridge Parkway is the only place.

Right up my alley! I can picture a couple friends and myself resting our bikes against the trees as we arrive at a campsite for the night. Hungry and tired from the road, a symphony of grunts and groans as we unpack our tents, nighttime clothes, and food for dinner. Nothing but our feet pushing on pedals to carry us from one site to the next. Climbing hill after hill and racing each other down as fast as our bikes will take us, the reward for several grueling hours of fighting gravity.

Up until this break, the hills they scared me! By the end of my cross-country drive, my lungs and legs were vastly more prepared for this trip than when I first dared to ride back up the hill from the Canal to my house. However, the hills in DC are no match for what we will face on the BuRP and I needed to get a better sense of what I was setting myself up for. Chance would provide me with an almost perfect opportunity when my family decided to spend the 2010 Christmas in Kauai, Hawaii.

In researching where the best spots to ride in Kauai are, I came across one ride I could not turn down. There were essentially two good options. One was a relatively easy ride along a path right by the beach, the other was an intimidating climb up the Waimea Canyon, by way of Kokee Rd. How could I pass up an opportunity to spend hours riding from the beach up thousands of feet above sea level? After four hours of riding, I managed to climb nearly 2,600 feet, the greatest elevation change I have experienced since getting my Marin in the summer of 2009.

I ate lunch in a cloud, literally, before heading back down to the sea. It was misty and refreshing! What took me fours hours to climb, took twenty-two minutes to ride down, hitting a top speed of just over 35mph. Once again, I tracked myself using My Tracks on the way back:

View Waimea Canyon in a larger map

Here is a picture slideshow from the ride:

For the first time in years, I understand how well I can ride uphill for hours and hours at a time. I still have plenty of training to do before I am ready for the BuRP, but now I know how much further I have to go. And more importantly, I know what it feels like to repeatedly mutter to yourself the words, "Hills are good! Hills are good!" Those three little words seem to pump a little extra energy into one's tired legs at just the needed moment.

This is where I sit as I begin planning out the tour and inviting friends to join me. It's January 6th, 2011.

Droid Apps Update...

Awhile back, in August, I wrote about some of my favorite Droid apps and when a buddy of mine bought a Droid yesterday, it reminded me that it might be time for an update (not like my original "These Go Up To 11" update).

First and only change, I don't use PdaNet anymore, I use Easy Tether Pro. They both work well, but Easy Tether Pro automatically connects when you plug your phone in as opposed to making you click connect on your computer.

I also need to add AirSync to the list. AirSync lets you connect to doubleTwist on your computer through a wireless router. It is remarkably slow (slower than I expected), so I would not recommend it for anything beyond an album. Definitely not useful for dropping 8gb of music on the phone for the first time, but a good feature for quick updates.

Since I am making additions, why stop there?

Next up, LED Light. This does, exactly what you think, gives you a switch to turn on your LED flash, making your phone a fairly decent flashlight. Nothing fancy, just a solid, sensible solution.

Where's My Droid. This is a fantastically simple app that will help you locate your phone if you lose it. You can send a text to make the phone ring, or text you back the GPS coordinates of the phone (can also send an email in). You can set the word or phrase to activate these features to be whatever you'd like. I don't suggest setting it to "Tell me where you are so I can beat the shit out of you" just in case someone texts that to you and gets back a google map link to your GPS coordinates. If you are cellphone-keeping-challenged, this is a must have, so if you haven't downloaded it already why the fuck aren't you doing that right now?

AnonOps - Calling MasterCard

11.6" MacBook Air Review - Part 2 of 2

Just to refresh (click here for part 1)

We're comparing these two computers:

MacBook
Hard Drive: 250 GB
Processor: 2.26 GHz Intel Core 2 Duo
Memory: 2 GB

MacBook Air
Hard Drive: 128 GB
Processor: 1.6 GHz Intel Core 2 Duo
Memory 4 GB

In this part of the test, I install some of the more intensive applications to test the speed and handling of this MacBook Air.

Starting off with the Adobe CS4 package, I chose to install a slimmed-down version so as to save on hard disk space, picking select applications rather than bulk installing the entire dozen GB's. This, of course, is no problem for the computer. The real test comes when I've got Final Cut installed.

Now, this is something I did not explain well in part 1. I have an iMac which is my primary video-editing computer. What I need from my laptop is the ability to cut out short videos in the rare occasion that I cannot wait to get back to the desktop. I knew that the MacBook Air was CAPABLE of running Final Cut. What I did not know is how well it can do that. Well, now I know.

To start with, I completely forgot that the new Air has no CD drive. I had to spend a few hours burning dmg's of the Final Cut discs on my iMac. To do that, on a Mac that is, you go into applications, then utilities, open "disk utility", click on the CD, click "New Image" at the top, save the dmg where you'd like, put it on a hard drive and open it on the MacBook Air. Very simple, but takes an ample amount of time.

Anyways, with Final Cut installed, I began the tests. I loaded a recent Final Cut project on both computers. I choose some videos from a MD Democratic Party GOTV Rally I went to right before the election. This is a great example of the type of thing I might have to edit on the fly (of course, with no firewire on either laptop, I'd have to have my old powerbook in tow to capture footage to an external drive). In total, the project was about 15.4 gb, big but not huge. I choose to render a couple of the videos I had cut out from the source material. In all tests, the MacBook rendered anywhere from 33-40% faster (I repeated this task a few times, once with several other applications running simultaneously). That sounds substantial, but these couple minute videos render relatively quickly, and the difference was close to 30 seconds.

Ultimately, I've decided the MacBook Air will suffice for what I need. It is the ideal computer for my bike touring needs and perfectly capable of handling all the other heavy duty tasks that I have (albeit a little slower). After selling the other laptop and purchasing an external for the Air, I will expect to have spent a few hundred bucks.

11.6" MacBook Air Review - Part 1 of 2

Just 15 hours ago I received my new 11.6" MacBook Air. I still have a whole bunch of tests to do with some of the more intense applications (Final Cut, CS4, etc...), and I have a feeling I'm going to push the limits of this thing. My hope is that this MacBook Air can sufficiently replace my 13" MacBook (letting me sell the MacBook) while also satisfying my need for an ultra-light laptop to bring with me on bike touring trips.

Here's how the specs compare:

MacBook
Hard Drive: 250 GB
Processor: 2.26 GHz Intel Core 2 Duo
Memory: 2 GB

MacBook Air
Hard Drive: 128 GB
Processor: 1.6 GHz Intel Core 2 Duo
Memory 4 GB

First impressions: Although the computer feels as sturdy in your hands as all my other laptops, the size of this thing is remarkable . My father said it reminded him off his iPad when he first saw it. It was certainly a delight showing it off at a coffe shop for a little during the day. I worry about the processing capacity, and obviously the computer is a little less computer than my MacBook overall. Don't get me wrong, I love the extra memory since I consistently use multiple heavy applications. But the processing power is nothing to die for (the highest you can get on the 11.6") But I'll find out just how this compares to my other laptop on that front tomorrow (and I'll post the results!). For now, I'll talk about the experience I've had so far.

The laptop came bright and early in the morning and while I've read many descriptions about the experience of first holding this thing, it still kind of shocked me. It really is thin and light! I got right to work importing all the settings from my Time Machine,  which I did not know you could do. My mail, Chrome/Safari bookmarks, dock, and other features imported from the Time Machine letting me skip setting that all up by hand and saving me a butt-load of time.

But I forgot the golden rule. Always check for updates immediately. It seems weird but you almost always need to update software right off the bat. Anyways, I found that out shortly into my downloading-applications process when my newly downloaded flash player didn't work properly. Not sure why, but a quick update and everything was working up and running.

I've enjoyed the feel of this so far. The 11" screen is so high resolution that it isn't all that noticeably different from the 13" MacBook. I was worried about the fact that the keyboard does not light up, but even on the lowest backlight setting, you can read the white on black keys. And the thing barely heats up, unlike every other Mac I have.

So, as for a laptop I can bring with me bike touring, this definitely does the job. What I am looking for is something I can use at night with my phone as a modem to browse the internet, upload pictures, and do some work possibly involving minor web design. The Air is light as can be, weighing in at only 2.3 lbs, so it won't hold me back on the notorious, endless hills of the Blue Ridge Parkway. And it's more than capable of handling anything I might want to do while biking and camping for days or weeks at a time (re: energy. I have a solar panel that attaches to my bike which should provide enough of a charge during the day to keep my droid charged and give me some computer use each night).

That's all great, but I said I want this to be able to replace my 13" MacBook. To sufficiently do that, it needs to be able to run Final Cut, Photoshop, and Dreamweaver (preferably all at once). That's a lot to ask of such a tiny beast, but I think it can just manage it. Then I can put my MacBook up on the market, spend a little bit of the cash I get from it on an external to hang with the Air and pocket the rest! Everything hinges on tomorrow...

A 2010 Election Chaser...