Last week, on 26 August 2010 I left the house on what would turn out to be an awesome ride. At the time, of course, I didn’t really know what pace I was going to keep – I just needed to relieve some stress and energy built up from work. At my first main road I made the turn as a truck was coming my direction and was able to slip into the gigantic draft and go ~38 for roughly one mile. It was awesome to say the least, but I eventually had to make a turn and was forced to back off.

I was feeling more than fresh at this point and decided that I could probably make a decent attempt at my Swamp record, a 3.1 mile section of road in the Great Swamp Wildlife Refuge. The road is essentially flat save a few hiccups, but if the wind is wrong then you will be pushing a brick wall through much of the mileage. That day I was fortunate enough to enjoy a complete, dead calm. I knew what I had to do – set a pace of 25 and hold it as long as possible.

The first mile flew by and I thought that I might have been going too easy. Experience took over as I remembered the hiccups and how bad the last half mile can be as the wind changes and starts to hit you straight on. I kept my pace and dug in (Paul might say I was conserving my lead at this point) for the next mile, trying to focus on anything but the cycling. As I hit the right hander the pain started to set in a bit, a slight up hill towards the first intersection and I shoved the throttle down. I was going to break my time… by how much. Previously this year I had set an 8:09, and before that an 8:20. How much lower could I go? Could I break the magical 8 minute mark?

YES! As I smashed the lap button to reveal my time and it sat there in all its glory: 7:29.57 for 3.1 miles!! A new personal record. Progress. There is the evidence that I am getting faster; getting stronger. And if I needed any more proof – the data in TC says it all (relevant area highlighted in yellow).

Of course now only one question remains: how much faster can I go?

The first thing you’ll notice when cycling in the Adirondacks is that everything is big. Lakes are big, mountains are really big and even the roads are big (that is a good thing). Even the distances between towns is big. So when planning a route, you really have to pay attention to how much climbing you will have to endure. The image floating off to the right there is of me during my last ride this year. The mountain in the back is Whiteface which summits around 4500 feet. While I didn’t (and couldn’t) go to the top, as I went past it I had to climb roughly 1500 feet to a peak around 2500 feet. And that was just to get to the base of the toll road that takes you to the top!

That ride (yesterday) covered roughly 66 miles and nearly 5000 feet of climbing. No simple task for a guy who is more Texas Longhorn than mountain goat. I got it done in just over four hours, and learned a few things along the way.

1. Roads in the ADKs are wiide and have almost no tree cover. Result? My arms are burnt (a bit, I had a tan already). So wear sunscreen or arm "coolers"
2. While roads in the ADKs are wide, so are big trucks. Stay to the right as much as possible to avoid the wash.
3. Enjoy the flat and downhill sections of your ride. Breath them in and don’t fret the speed. The climbing is where you gain (or lose) massive time.
4. Bring lots of water. I never ran out because I had three bottles, but because towns are spaced out you could run into issues if you aren’t prepared.
5. Small cameras are the bee’s knees. The ADKs are beautiful and you’ll want to remember your ride, even if it makes for an embarrassingly funny story.

Aside from all that, go out and have fun. It is what you are there to do (hopefully)! While on my ride, I got to see a lot. Around mile 20 of my ride, I found myself along a river that empties out into Franklin Falls Pond. I road along the river for a few miles hoping to see a bear off in the distance taking in a drink but fortunately I was unlucky. The river empties out into the following pond which is capped by a dam.

Shortly after that, I found myself topping the ridge attached to Whiteface Mountain and essentially free falling down the other side. The road I chose to go down is roughly -10% gradient for three miles with absolutely no breaks until the bottom. I ended up passing cars easily as they were all happily enjoying a lower gear ride. Me – I had no choice but to let go of the brakes and hope for the best. Fortunately all went well and was able to get this shot of the ski side of Whiteface.

After cresting the bigger of two evils for the day, I had to set my sights on the next "climb" as it started immediately. The road crept along the valley, inching its way up and eventually over a ridge to Lake Placid. I had no mind to stop and take pictures, but there was plenty of scenery to soak in including the gorgeous gorges.

Finally after 56 testing miles, I made it back to Saranac Lake and knew my trip was to be completed. The shade (and Clif bar) taken in here was a reward like no other.

By the way – those are tubeless tyres you see on my rig. And yes, they are fantastic. Have ridden them for a couple hundred miles and they are incredibly comfortable and fast.

The new release includes the first version of the new XML serialization classes and numerous fixes. The License is included with the following downloads.

My story begins nearly two weeks ago. The roll off of the Category 4/5 Pinecone Road Race was without incident. The course is a flat 10 mile loop with five right hand turns – easy enough for those who have ridden in serious groups before. Through the first turn I chose an inside line knowing that there would be a sand trap of sorts. By putting myself through the dangerous part of the turn I insured that no one could come on the inside of me and wreck the group. If I went down, I could only blame myself.

After making it through the first turn, we headed down the back straight towards the next set of turns. The group was packed in like tunafish in a can due to the double yellow rule (cannot cross the double yellow line). A constant shuffling of bodies meant that you had to fight just to stay where you were in the group to say nothing of moving up. The next set of turns come up and fly by without incident. I thank the lord quietly as no one has made a silly mistake of going into a turn too hot or not holding their line.

Finally we make it to the front straight on the first of three laps. The group is moving along at about 22 miles per hour, the road is flat, the sun is shining and the mood is calm but focused. I am comfortable, my heart rate shows it and my legs feel great. And that is when it happens.

A massive slowdown in front of me and voices yelling out “woah!” in anger and fright. I know immediately that I have no choice but to lock up my wheels and scrub off as much speed as possible before I reach the impending doom. A wall of bikes and people comes up and I hit something, go down, slide and land under my bike. People are falling on top of me, but I am okay. As the fallen recover, check their bikes and move on I realize that I am not to join them. A quick glance at my bike shows a decimated front wheel. No spare wheel means I will be walking to the start/finish (until picked up). But at least my limbs are still attached and nothing is screaming at me in agony. I am bleeding from a few spots, but with full motion I realize I got out extremely lucky.

It has almost been two weeks since that day and I am still struggling a little to find my mojo. While I rode last weekend, it was a feeble attempt to maintain whatever physical ability I have gained this season. The crash has ruined my momentum and has put me in a period of poor form. And while I am positive that I can get back on good form, it will take some time. And there is really only one thing that can be said about all of this: crashing sucks.

Here is a full list of the changes made since 1.0.0.4:

• Added drag and drop sorting.
• Added item pinning (will stay at the top).
• Added settings for turning off (and on) certain data formats.
• Added a “Clear Korkboard” button to clear all non-pinned and unselected items from the list
• Fixed current item selection for when items are selected outside the application
• Fixed text alignment issues in the settings page

I have also changed the download to point to the ClickOnce EXE file instead of the Application file. This should fix any issues with non-IE browsers. Thanks to Long Zheng and MetroTwit for this idea.

Korkboard is a little tool I have been developing that enables a uniform method of storing multiple items on the clipboard. When Korkboard runs, it hooks into the clipboard chain and attempts to intercept messages as you use the Copy and Cut commands. It then stores the items on its own list so that they may be retrieved at a later time. It is important to note that Korkboard does not mess with the functionality of the clipboard. If you copy an item, the clipboard works as expected without any interruption or user required interception. Check it out, and let me know what you think!

• Korkboard v1.1.0.0 (177)
• Korkboard (Zip) v1.0.0.4 (22)

Korkboard is written in WPF/.NET4 and uses ClickOnce to manage the installation and update processes.

Update: Added the Zip file for those having trouble using the ClickOnce method.

Photo by Jan Curran

Immediately leaving the gate, I felt good and settled into a comfortable albeit fast rhythm. My heart rate, around 170bpm, was right where I wanted it. This beautiful scenario was quickly smashed when I hit the first roller which brought me into the red zone immediately. You can see from the data below that this is where my problems started.

(Click to enlarge)

Because it was the first hill and because I was able to topple it rather quickly, my body recovered once over the top. However, with each subsequent hill my HR went through the roof and then remained high. Somewhere after mile three or four I developed and odd sensation in my chest; like a grapefruit had been lodged deep within. I pressed on, but each roller really started taking its toll on me until I could barely get over them above 15 mph.

Overall, I am pleased that I got out and did another race and gave it my best shot. As for my performance, I know what I need to work on and know I need to work much harder if I expect to beat my personal best at the Kingwood TT (end of July).

1

HttpContext.Response.AddHeader("cache-control", "no-cache");

Note that if you have already hit the particular view and it is cached, you can generally clear the cache by navigating to the URI of the view manually and hitting refresh.

This is just the beginning (facing backwards) of a long, hidden treasure in NJ. A road that creeps along a hidden lake/reservoir, waterfall and river.

This is the wide part of the river. It feeds towards the camera to the lake (behind the camera).

Daffodils (I think?) in bloom! These are everywhere along the route, giving you something to look at as you climb.

Lazy on the editing (electrical lines), I know, but pretty tree never-the-less.

Overall I am very happy with the camera so far, and very happy with my progression this year on the bike. I have lost some weight (horray!) and my power and endurance are staying pretty level. They are certainly much better than this time last year. Now, back to coding!