Two big trips for 2013

As this year is winding down, I’m looking at a couple of big adventures in 2013…

– Some kind of January or early February thing. I pulled the trigger on an ill-fated plan to bike the Florida Keys until I found the camping was totally booked or outrageously expensive. So that’s scrapped. I’m now toying with an Arizona loop starting and ending in Tucson (might be too cold) or a Portland trip that is more about snowshoeing and urban biking. I suspect it may rain.

– The bigger deal is my summer. I have about 6 weeks to play with following WDS in Portland, so I know things start there. Option one is a loop from PDX to Seattle to visit friends and family, then a turn south to San Francisco, and then a return to PDX. Option two is bike east…. as far as I can… in 6 weeks. I thought this might be the year I could do a full cross country tour, but it’s just not enough time if I want to try to sneak in some work and keep the pace reasonable.

So, that’s the deal. I’ll probably overthink both options for both trips and I’ll likely write about the thought process. Apologies in advance.

In other news, I tried to convert my dog Louis into a bike touring dog. It did not go well:

adventure by bike

Hey, this looks cool… I’m game!

do NOT take me biking again

do NOT take me biking again

couch > bike

couch > bike

I repair iPads*

*but Jony Ive would cry if he saw what the finished product looks like.

I stepped on my iPad in France and crushed the glass digitizer this summer. Luckily, thanks to the brilliance of Corning, NY’s own Corning glass, that stuff is strong. Other than the ugly break pattern, the iPad continued to work…

20121023-193240.jpg

…until I dropped it again. Then it started acting like I was constantly pressing on a seemingly random spot on the shattered screen. It was time to act.

I found an amazing local business that would come to you, replace your screen while you wait and send you off with a perfect iPad or a mere $199. But I decided I wanted to do it myself for 40 bucks and a few hours of my time.

I won’t bore you with details, BUT… I’m clearly an electronic genius. A few YouTube videos to light the way, a glass kit from Amazon via some place in Jersey and I’m tapping out this post on a totally functioning iPad with its new screen.

But I’m too chicken to glue the screen down. There’s literally no way I trust that this can work long term without some itty bitty circuit coming undone in there, so instead of making he final seal in the perfect fit and finish of an Apple product, the screen’s locked down with easily removable electrical tape. Black bezel and black tape camouflages it ok:

20121023-193334.jpg

See it? Jony Ive would. But only when he wiped away his tears…

So, I humbly declare that I fix iPad screens!

I hate to say it, but iOS 6 Maps sucks (right now)

The ATL in iOS MapsI’m not a hater by nature… I really rebel against the trite negativity, particularly put out by vast stretches of the tech and political press (which I happen to read a lot, despite my professed rebellion). That said…

iOS 6’s Maps app just doesn’t work right now. It kinda sucks here in October 2012.

I didn’t have too many problems in DC or WV (the places I split my time) but on a quick weekend trip to Atlanta, the Maps app showed how being a little off can be really bad. Essentially every single trip I had… Airport to hotel, hotel to wedding reception location, back to hotel, then hotel to breakfast spot the next morning… all of them were off by a little bit. A turn here or there, an address off by a block. It all added up to a big mess when you’re in a place you’re not familiar and you’re banking on the data behind the app to work.

So, let me be a little more refined than shake my fist at the sky and declare suckage… the app is slick. Siri… well, she can direct you. But the underlying data is smelly, stinky, sucky. Google Maps was far from perfect, and was clearly missing turn by turn directions in iOS, but I don’t remember the consistency of misses like I just experienced in the new Maps app.

But… it’ll get better. I can use Waze or any number of other options until the underlying data mess gets fixed.

And by the way… Atlanta? You keep staying weird. We like that:

Eat More People

Update… edited to correct the fact I apparently can’t differentiate between “iPhone5” and “iOS6.”

Big Slackwater

Gorgeous view at Big SlackwaterIt’s a good day to be a C&O junkie… the Park Service has finally reopened the Big Slackwater portion of the trail, meaning we’re *this close* to having the entire trail reopened from Georgetown to Cumberland with nary a detour in sight. There’s the little matter of the much newer detour by Great Falls to dispense of, but that might be done soon.

In any event, riding this portion of the trail was of great consequence to me personally, because it was the only piece of the trail I had yet to ride… of course I’ve ridden the detour many times. It seems to have been worth the wait… it’s a 5 mile (ish) stretch that includes the formerly impassable portions that have now been converted into gorgeous concrete roadways mere feet from the Potomac. Figure the flooding issues will always be issues, but these structures don’t look like they’ll be too subject to the whims of the river.* Figure it chops off about 30-40 minutes of the ride compared to the former detour, which is nice because that’s 30-40 minutes closer to beer o’clock at the cabin on the second day of the ride from DC…

All in all, my favorite part of the trail. Good job NPS!

*Be sure to remind me with headline links to “Massive flooding closes C&O trail again” later this winter. Jinx.

Continental Divide

Top of the Allegheny's

Last week, I wrote about riding the GAP to the MD/PA state line. Sunday, I rode with MJ for the first time since our west coast adventures and made the trail all the way to the eastern continental divide. At a length of 50 miles round tripping from Cumberland, this was a fairly vigorous ride, but oddly easy considering the accurate, but misleading, elevation chart.

The ride confirms that the 135 miles from Cumberland to Pittsburgh is an “easy” 2 day trip, with a likely overnight in Ohiopyle State Park, or maybe a leave-no-trace wild camp if it’s appropriate (although probably not technically allowed). Unfortunately as the fall weather makes this trip beyond tempting, my fall schedule is tricky to coordinate enough consecutive days to make it happen. Since one of the tunnels closes November 1st, it might be that this section of the trail may be the only part I can do until next spring…

MJ on a horse

MJ on a horseFrom the archives… this was before we decided wheels were better than legs. Also, I believe our ride guide was thrown from her horse shortly after this shot was taken. Number of times I’ve been on a horse since: zero.

Riding the GAP

Sunday was a gloriously perfect day for a ride, so I drove about an hour west of my cabin to Cumberland, MD to check out the Great Allegheny Passage, a 130-ish mile trail linking up the end of the C&O with Pittsburgh. I’ve read some great things about the trail, mainly its surface. Sadly, I didn’t have the time to carve out a multi-day trek, but I got a good sense of things in my 41 mile round trip.

  • The surface is nice, but not as solid as I thought it would be. The crushed limestone wasn’t compacted in several spots, leaving a pretty soft slide when hit wrong. The portion I was riding had a slight incline to it, so on the descent things can get a bit dicey if you’re not paying attention.
  • Come fall, the vistas will be amazing… serious foliage potential. One ridgeline on the climb features a line of turbines… not a natural feature at all, but I’ve always thought they stand as a nice juxtaposition of technology amongst the wilderness.
  • The climb is not difficult at all, but it is about 25 miles long. By mile 20 I definitely felt it, but then again I never really took a real break to speak of. About MM 25, you hit the Eastern Continental Divide, so the rest of the ride turns into a gentle descent as you roll west. Since the climb goes pretty fast (and the descent even faster), I figure it’s reasonable to do the 130+ miles in 2 days (and therefore, the Pittsburgh to DC run in 5).
  • The train was cool, but the smog that comes out of that stack is no good for the lungs. The tunnels were nice and big for this claustrophobe, thank you very much.
  • Loved the Mason-Dixon line setup at the PA/MD border. I chose that as my turnaround point rather than tempt myself with what lay beyond the Continental Divide…
  • Oh, and the Bills won while I was riding. Like Cube said, it was a good day

Change happens, just be ready for the unexpected

When I first met Bonnard, my soon-to-be girlfriend’s cat, we got off to a bad start.
20120818-120418.jpg
An eight year long bad start.

Bonnard would have preferred I wasn’t around, and one occasion seemed to be actively trying to crush the breath out if me with his rotund, but not-heavy-enough body. Hissing, biting, scratching… All part of the norm. Now, and quite suddenly, Bonnard cuddles with me. It’s disconcerting… I’m not exactly neutral on the subject of cats.*

This got me thinking about all of the other surprises that have come along in my life. My career path has diverged greatly from what I thought it would be, and probably for the better. I’m glad I haven’t resisted the change, even though a part of me bristles when people suggest I’m “not a lawyer anymore.”

Despite that, I’m glad I have been open to shifting away from preordained notions of career towards paths that have been fulfilling, interesting, diverse, and allow the lifestyle I have come to enjoy. Change in my “business” life has been good, particularly when it’s incremental and on my own terms.

—-
*I sort of dislike them, but he’s sitting…. right… here… as I tap this out…