I’m a lean mean paddling machine!

On Sunday, Vicki and I went for a paddle with the Huggers.

But first, I went for a long fast paddle to get the “need for speed” out of my system. I did 5 miles, and while I started out slowly for the first half mile, by the 0.7 mile point I was definitely up to race pace. I just can’t get the hang of this “warm up” business – never have. Going up stream, I was maintaining a pretty good 5.8 mph or so – although the last half mile before the turn-around was up above 6.0 mph. When I turned around, I was making better than 6.5 mph. The fourth mile was an average pace of 6.6 mph and the fifth mile was an average pace of 6.5 mph. Even including the slow first mile, that meant that my five mile total time (49:41) was faster than the speed (50:14) when I did a 5 mile time trial a mere 21 days ago.

But more importantly, doing a big work out mere minutes before going for a fun paddle did have the desired effect – I could enjoy a nice leisurely paddle with Vicki and the others without any need to speed ahead or run rings around people or any of the annoying things I do when I still have the need for speed. And we had a great time picking our way up and back Red Creek, this tiny and wild little stream in the middle of Rochester.

Today I went for an even longer paddle – 8 miles. I was going to go up the river again, but there was a bit of a breeze going down the river and I didn’t fancy fighting a head wind on the way home. But fortunately the Genesee Waterway Center gives you a choice – the river intersects the canal right there, and the breeze was blowing straight up the canal. So I went down the canal. It wasn’t an extremely pleasant paddle – the canal parallels highways and industrial land almost the whole way. Although I did see a Great Blue Heron and some ducks. Once again, I didn’t manage a proper warm up. Looking at the speed graph in Garmin Training Center, it looks like I once again only warmed up for half a mile or so. For the first 3 miles or so, I felt no fatigue, no soreness, the only sensations were a slight pull from the bandage on the sores on my back and the relentlessness of my own stroke.

On the way back, I was a little disappointed that the tail wind didn’t improve my speed that much, or at all really. My third mile had an average speed of 6.0 mph, and my downwind miles had average speeds of 6.1, 6.0, 6.1 and 5.9 mph. I don’t know if I was slowing down, or the wind was abating, but I definitely felt that there was a current going against me. But that doesn’t matter so much. What does matter is that I kept my pace up, and besides a few pauses to grab a drink, I didn’t have to stop at all. And afterwards, I was tired, and I was ready to stop, but I didn’t feel like I had to stop.

Eight miles, 81 minutes. I am *so* ready for the Tupper Lake 9 Miler. Only 11 days to go.

A guy could get used to this

It’s been in the 90s and sunny for the last three days, and I’ve been privileged to spent a few hours each day out on the water enjoying the sun and warmth.

First on Tuesday, Dan, Frank and I went for a long slow distance paddle. I didn’t bring my GPS, but Dan figures I went a bit over 6.5 miles. I was attempting to go at a nice steady pace, and because Frank was having a bad day, I ended up zig-zagging some of the time so that Frank could keep up and I didn’t have to slow down. Interestingly enough, I had to zig-zag the first two or so miles, and then I had a mile or so where I could just keep up with him, then when we turned down stream I had to zig-zag again for about two miles, and then for the rest of it Frank and I were very well matched. I can only think there was a bit of wind that was impeding me for the last part of the upstream and helping me for the first part of the down stream. My boat (which used to belong to Frank) is definitely more subject to the wind that his.

Wednesday, most of the team went out and did a bit on the lake and a bunch on the bay. We were trying to learn to get comfortable in the waves, and the mixture of boat wakes coming from all directions (and the rebounds from the shores) were certainly a challenge. Dan remarked afterwards how I was up front leading most of the time, but there was method in my madness – I was almost sure I was going to dump, and if I dumped I wanted to have the maximum number of people in position to help me. In fact I didn’t dump, and while I wouldn’t call it all fun, I did manage to catch a few good waves and have some fun with them once in a while. I definitely recommend doing wave practice (or just paddling in the bay in general) with a bunch of other experienced paddlers around rather than on your own.

Today Dan and I went up the canal again. This time I went a bit further upstream that on Tuesday. There were some boats around, and some challenging wakes. There was one section just past 490 where there were vertical concrete walls on each side of the canal, and it acted like a wave laser, letting the wakes of the boats that had gone by some minutes before I got there to bounce back and forth and reinforce each other. There were times today, like yesterday on the bay, where I just had to stop paddling and brace. But I got through it and into the parts with the sloping walls and everything calmed down. I turned around when the GPS was showing a hair over 3.5 miles, since I figured a 7 mile day was a good distance. The “wave laser” wasn’t so bad on the way back, and I got some good help from tail winds, so I was keeping just around 6 mph most of the way back.

At about the 4.5 mile mark, Dan yelled at me to keep my chin up, and then I didn’t see him again for the whole way back. I was getting a bit worried, because he’d had to stop once already to adjust his foot brace and had something about needing more adjustment, so at first I thought he’d just stopped for that, but I expected him to catch back up soon. So I started to wonder if he’d had some worse problem and had to abandon ship. After I got back to his dock, I figured I’d go up stream a bit to see if he was coming. I got up to the rowing club, and he was coming and so was a motor boat I’d seen a lot of today. On the way up, I’d tried in vain to catch and hold this guy’s wake, then he’d passed me going the other way where his wake had just been a challenge, and then I’d passed him when he was on his trolling motor casting into the shallows at the side of the canal. I turned as he passed, and this time he seemed to be going a bit slower. I caught one of the perpendicular waves behind his boat[1] and tried to surf it, but it actually propelled me up to the next wave. Trying to get to the best surfing position, I found myself going over 7 mph and catching him. Pretty soon I got tucked in right beside him, matching his 6.2 mph speed and going along with only minimal effort. I could speed up and slow down and get to exactly the wave I wanted and where I wanted it. It was very cool. He eventually noticed me there, and he asked me if the wake was helping me, and I grunted out a few sentences to confirm it. I must have surfed his wake for about a mile, and only quit when I decided that was about as far away from Dan’s dock as I cared to paddle back to. The GPS says I ended up doing 8.8 miles, which more than I expected.

I’ve decided that all I need for my next kayak race is a motor boat to pace me at exactly the right pace so I can surf their wake the whole way.

[1] There appear to be three distinct types of wave from a boat – there are waves that come off the bow and spread out in a “V”, which actually curve to turn more to perpendicular to the boat the further out they go. Then there is another set which come out in a “V” which don’t seem to turn, and which are much steeper than the first set – I think they come off the stern. Then there is a bunch of much more subtle ones that come of behind the boat and which are perpendicular to the boat travel. All of them can be useful if you catch them right.

Why I find Objective C a hard language to learn

Lots of methods get an NSIndexPath as the argument, and all the sample code that I’ve seen gets the current row out of the indexPath object using [indexPath row]. Sometimes they get the section number using [indexPath section]. Ok, that seems simple enough. Now look at the documentation for this class, which is what you see if you use the XCode research assistant to show you the documents:

NSIndexPath Class Reference.

I cannot for the life of me see any way to extract the information that you get the current row using “row” out of that document. It’s not there. No, instead you have to figure out that UIKit has added some methods to NSIndexPath, and find ‘row” and “section” in a different document called “NSIndexPath UIKit Additions”. Isn’t that intuitive?

iPhone app

I haven’t written much about my iPhone app, but now that I have some time on my hands, I’ve put some more time into it.

I’ve been watching the Stanford iPhone course on iTunes U. They had a couple of successful iPhone app developers come in to give lectures, which were very useful. One of the things that stuck with me was an insistence that you prototype the user interface. They recommended sketches, but my sketches are horrible so I decided to try Photoshop. I grabbed this Photoshop template which is really great except it’s missing some important UI elements, like the symbol that looks like a “Do Not Enter” sign that iPhone apps use to indicate “delete this element”. In spite of that, I managed to mock up some screens, get some feedback, try running through a few scenarios, etc. You can see my current iteration on my gallery. Keep in mind that I don’t think I’ve got the correct fonts or font colours for the standard iPhone UI, but I mostly did it for looking at layout and program flow.

As well as that, I was working out the data storage, including the SQLite tables and stuff. I was trying to figure out how to get the lazy load the data and only keep what I need in memory. That’s when I started reading about the 3.0 software and the Core Data API. It seemed like exactly what I need, so I paid my registration fee and downloaded 3.0 to see if it will be as useful as it appears. One unfortunate side-effect – all the code I’ve typed in from the iPhone book I’ve been working through has tons of “setText is deprecated” warnings. Oh well.

Well, that sucked

I know you’re tired of all those “good workout” blog posts, so I thought I’d have a lousy one just to keep it interesting.

I was intending to go out into the bay for another 5 miler and hopefully still have some energy left for a few miles on the creek. But I wasn’t counting on two things – one is that the thunderstorm that blew through yesterday is being trailed by a very strong wind (the airport is reporting winds gusting from 15 to 26 mph) and the other is that my right shoulder started to hurt after about a mile.

The waves weren’t so bad while they were coming right at me, but the wind was cold. And after passing “One Mile Point”, the wind started to swing to the one side and so did the waves. Because of my shoulder, I was wondering if I should turn around, but also wondering how I could turn around since that would involve going broadside to the waves at least momentarily. The shifting winds sort of made the decision for me – I was going to be broadside whether I turned or not. So I turned.

On the way back, I got good surf, but unfortunately my sore shoulder was preventing me from enjoying it. And the soreness got worse as I went on.

Oh well, maybe tomorrow.