Angry workers and the endless trail

My view of the trail today

Today's run (Bethpage bike trail): 9.7 miles

With the Marcie Mazzola 5K happening on Sunday, I needed to figure out a way to get my long run done this week. On Wednesday I logged six miles and was planning to run 10 or 11 on the weekend. I didn't want to run that much the day before a race, so I decided to cram it in today. I'm wrapping up a lot of things as I prepare for a new role on Monday, so my schedule was tight.

I decided that the bike trail was my best option, so I drove to the small lot that sits on the bike trail north of Old Country Road. I quickly started running north until I reached Washington Ave and turned around to run south. My target was 10 or 10.5 miles and I felt great. The weather was perfect and the setting serene. I must have seen thirty cottontails along the path and countless birds. Not too many people though.

I did fine through the first five miles despite the hills that came about every quarter mile. My only concern was time, because I needed to be home (and hopefully showered) before a business call that was happening mid morning. Once I'd traveled south of the Bethpage lot and down the big hill, I started to feel a little fatigued. I'd swapped the sock liners in my Virratas for gel insoles and that turned out to be a good idea. However, the softer landing probably made me work a little harder on the hills.

By the time I reached seven miles, I became concerned that my progress was not fast enough to meet my timeline. I was really feeling fatigued and the trail seemed endless. I also realized that I did bad math in terms of turnaround point and I wouldn't quite make ten miles. Oh well, it was only a 3/10th of a mile difference. The only disruption to this placid experience was when I reached Old Country Road near the end of my run.

Before I'd rounded the corner to the street, I heard loud male voices screaming at each other. It was mostly expletives. These were town or county workers who were fixing the bike trail at the point where it met Old Country Road. I was mildly concerned because I needed to run between them to get across the street and more concerned when I saw that one of the arguers was driving a huge front loader.

I think they realized the danger of interfering with a civilian, so they stopped while I passed through. Immediately after, the guy in the front loader started yelling, "I !@#$% quit!" By then I was on the trail on the opposite side heading to my car.

Even though today's distance was almost the same as last Sunday's, today's run was far tougher. I'm hoping it had to do with running almost ten miles after running 6 just two days prior. For some, that would have been a non-issue, but it was only about five weeks ago when I was struggling to complete 4 miles on this same trail.

Tomorrow I will rest and Sunday I'll race. What I'll do for training next week is still up in the air. I'll have to see what my schedule holds.

Bethpage run: Making friends along the trail

I really want that chocolate bunny

Today's run (Bethpage trail): 9.5 miles

Today is Easter and I hope it's a good one for those of you who celebrate this holiday. I don't, but I'm certainly celebrating the great weather we're having this weekend. Sunday is when I do my longest run and the distance gets extended each week as I build up to half marathon distance. Last Sunday I ran eight miles and today's plan was for 9. Depending on the training schedule, today could have been a ten miler, but I was reluctant to jump 20% from week to week. Though it was an accident, I ended up with a good compromise distance.

My Runsketeer friends are both in Boston for the marathon that's being held tomorrow. SIOR will be running it and we are really excited for her. She trains really hard while taking great care of her family (4 kids!) and she has the athleticism to make it a memorable performance on Monday. No pressure, just qualifying for Boston is a victory. TPP is there to support her sister T, who is also running tomorrow. T is another high performer. That, of course, is a prerequisite for getting entry into Boston.

As a native Bostonian, I would have loved to be there to watch them run through my old home town of Natick, but I'll be here on Long Island tracking their progress through the baa.org site. In the meantime, I have my own race training to do with the Brooklyn Half coming up mid-May and the Marcie Mazzola 5K next weekend. I'm very curious to see how I do in terms of speed in the 5K and whether all these hills I've been running will provide a performance payoff.

Today's run was split into two experiences, one being a pleasant but uneventful solo effort for about five miles and the other a highly enjoyable almost-five with an other runner on the path. I parked near Haypath Rd. again and got right on the bike trail going north. I followed the trail up to Washington Ave and turned around once I reached the underpass of the LIE.

I maintained the easy pace that I need to cover long mileage while I rebuild my endurance. I got to the five mile point and had stopped at Haypath to watch for cars when I saw another runner to my left. We exchanged hellos and crossed the road. I suspected that he was faster than me and was surprised that he hadn't taken off and passed me at that point. Instead, he (I'll call him J) pulled alongside me and asked how many miles I was doing. He was planning to do about the same, we're both training for different long races and his will be in Vermont.

Today's elevation profile

J turned out to be a very good and interesting guy who also works in the media technology space, but not in publishing like me. He set a slightly faster pace than I was running and I was very surprised that I was able to hold up my end of the conversation. J is a tall athletic guy and I'm somewhat older than him. He could have easily run two or three minutes a mile faster than the pace we held and I was grateful that he didn't. He really pulled me along, especially on the hills.

The time spent with J went by much faster than the previous five miles. Just like when I have group runs with SIOR and TPP. Good company is a runner's gift. I left J to finish on his own once we returned to Haypath and I felt remarkably good after covering almost ten miles today. All this focused training is making a difference and it demonstrates that there is no substitute for putting in the work. When the work is made easier with friends, it's simple to understand why we do this.

8 miles at Bethpage, but parking was the toughest part

X marks the parking spot (map and picture)

Today's run (Bethpage bike trail): 8 miles

Today was my longest run of the week and I knew I'd be doing it somewhere on the Bethpage bike trail. I just didn't know when or where I'd start. GLIRC had a clubhouse run scheduled for this morning and I considered joining them for that. Those runs start at 8:00 AM sharp in the parking lot of the GLIRC office in Plainview. I wasn't in the mood for running with a big group, so I decided to skip that event and do my long run solo.

TPP was also doing her long run at Bethpage today and I'd hoped to cross paths with her at some point. We did end up finding each other on the trail (she was easy to spot in her vivid pink running gear) and we ran together a bit. TPP was having a tough time this morning and decided to head back to her starting point. Despite that, she ended up covering almost 8 miles.

The Hal Higdon plan called for 8 miles today, although my ER plan had me down for 9. Since I ran 7 miles last Sunday, I decided that eight was enough <smiley face> today. I recall from my last half marathon training cycle that the challenge of going from 5-6 miles to 8-10+ took some acclimation. I was concerned that I'd hit the wall after 45 minutes or so, but I never felt depleted. I stayed around 80% of max HR throughout the run, largely due to maintaining an easy, but steady, pace.

Before I took my first step on the Bethpage bike trail, I had a frustrating experience trying to find a place to park my car. I'm planning to get a 2014 Empire Passport so I didn't want to pay the Bethpage parking fee today. I was hoping that they weren't charging for entrance this morning, but when I arrived I saw that the toll house was open for business. I thought about other options and turned around. I then drove to the small lot that is located off E. Bethpage Rd near Old Country Rd.

When I arrived at this lot, every one of its ten or so spots was filled. So much for that. I was 30 minutes past my planned start time and still had no place to park my car. I was going to park along Haypath Rd. but I wasn't sure that was okay. I then noticed some cars with people who looked like runners parking along Colonial Rd and found a spot near them. I took care to see any signs restricting parking along the street. Seeing none, I parked and crossed the road to the bike trail.

It was only a few minutes after that when I saw TPP. Despite her claim that she was struggling, she looked strong as I watched her coming south in my direction. I wanted to follow the trail north all the way to Sunnyside Blvd. After a few minutes of running in that direction, TPP decided to head back to the lot where she'd parked. She's really cut down on simple carbs and sugar and has been having trouble maintaining her targeted performance levels. I'm confident that will soon change.

I wasn't thrilled about covering the section of trail north of Washington Ave because it has a series of long hills. It was no picnic, but I did better than expected. I'm sure last weekend's hilly workout helped prepare me for today's. The only difficult times were when I was coming up steep hills against 12 MPH winds. I maintained the best pace I could, shortened my stride and got through those situations fairly well.

Today's route, with out-and-backs at both ends

It takes a while to cover eight miles and I ended up needing to go south of my starting point to pick up miles 7 and 8. That took me close to the start of the north trail. I kept waiting for my energy level to drop but it never wavered, except when I was a couple of tenths away from my finish point. That was obviously a psychological response to almost being done.

This training program has been nudging my weekly mileage beyond my average of 18. The past couple of weeks were 21 miles and this week I covered 23. That was with two rest days instead of my usual one, meaning my average run length has increased measurably since I've started training for Brooklyn.

Snowed out at the track, but not at the park

Track was snow go

Today's run (street): 4 miles

I ended up wimping out of the GLIRC run today. I debated whether to head over and see the condition of that route (it would have been a five minute drive), but finally decided to pursue a different workout. I haven't focused much on my speed lately and the Bethpage trail relay is next week. A track workout would be ideal so (after much preparation and stalling) I made my way to the high school track.

I was hoping the track would be clear, but when I arrived I saw that it was covered by at least three inches of snow. It would have been perfect conditions for Yaktrax or snowshoes. I was dressed for a cold outdoor run and didn't want to return home to the treadmill so I thought about my other options. First was the paved area at Stillwell that was right across the street. I knew that I could run a .6 mile loop there. Similarly, I thought about running the half mile route around the driveway loops at the middle school in my neighborhood.

Neither choice appealed to me, so I started to head toward the GLIRC office. I figured that I could park around there and pick up the northern end of the bike trail where the Clubhouse runs start. On my way there, I swung through the local business park and saw that it had clear roads and sparse traffic. I pulled into one of the lots and started a run going clockwise around the loop.

I had put on a lot of layers and immediately noticed how it restricted my stride. The 1.2 mile loop rises and falls with the clockwise direction, providing about 40 feet of elevation gain within a .4 mile section. I usually run it that way, rather than going in the opposite direction where that elevation stretches across 3/4 of a mile.

After so many treadmill runs in the past few weeks, I found the pavement a little jarring. I thought about my blogger buddy SIOR who goes out for runs in the double digits a few times a week (20 miles yesterday!) while I struggled to get my road legs back. Soon enough, the snow will leave us and I'll begin my base training runs for the half marathon that will culminate with 12+ mile runs.

At 2.8 miles I needed to stop at an intersection where a few cars were taking a left toward Jericho Turnpike. I hit stop on the Garmin while the cars went by and (apparently) did not properly restart it. About five minutes later, I heard a beep and saw that the Garmin was shutting down to preserve battery. I restarted the watch and tried to estimate how much further I'd need to run to cover four miles.

Round and round the park

I figured that a side route towards the Route 135 underpass would gain me the distance I'd need to make four miles. I would have aimed for more distance, but my right knee was feeling slightly sore. I finished up fast, with my best pace of the run on the last quarter mile. I knew it was the right time to stop when I reached the lot where I parked. I Gmapped my route when I got home and confirmed my distance.

I only covered about eight miles over the weekend, despite my goal of doing ten. That was fine because my legs got a good workout, especially today. I do need to dial up the speed to help prepare for next weekend. With snow falling tonight, that will probably have to happen on the treadmill.

Seven miles of fun on the GLIRC Clubhouse Run

Group shot just before the start

Photo courtesy of SIOR and GLIRC

Today's run (GLIRC Clubhouse run): 7.4 miles

Well the snow came a little earlier than expected, but it didn't interfere with today's club run in the least. I arrived at the Greater Long Island Running Club (GLIRC) office just before 8:00 AM this morning and saw that I was almost late to the party. My friends TPP and SIOR were there among the assemblage of colorfully dressed participants. After some quick hellos and a group picture, we were all off and running.

The three of us followed the group and headed out of the business park onto the bike trail. It's a hilly section from that point to the turn onto Washington Ave. Although I had good energy at the start, I worried about how I'd be feeling after many more miles. SIOR and TPP are both speedy runners, but they maintained a pace that I could sustain with some effort.

We chatted with other runners as we made our way south and came under the LIE overpass at Washington Ave. We crossed the road and found ourselves on a wooded trail that roughly parallels the bike trail. The snow had covered the sidewalk that led to the paved path, so it was confusing where to go. A little diversion into the woods was unexpected and appreciated at different levels by the three of us. The ice and roots on the path made the going treacherous.

We came out at Old Country Rd and continued on the paved path that rose for a while and proved a little challenging for me. Unlike the last time we ran together, today was more of a workout (though not much of a challenge to my friends). I found it hard to maintain a conversation at times, but we did have our moments. We took the run past Old Bethpage Rd and as far south as Haypath. As we drew close, many of the returning runners warned us of black ice further down.

I struggled to keep up with my friends who were gracious about waiting for me to catch up from time to time. They were probably running one or two minutes slower than their normal training pace, except for periods where they opened the throttle for a few minutes. I was challenged but I didn't reach the point where I felt I was over matched or wished the run was done.

When we turned north from Washington Ave I knew we were close, but I also knew the toughest hills were coming. I took on the first hill with a pace slightly better than a fast walk. SIOR had no trouble burning up that hill as well as the ones that followed. TPP stopped to walk and I stopped with her. She will occasionally do that for 30 second periods and it's a good strategy. I probably delayed her a little, but once we saw SIOR at the top of a hill we returned to running form.

TPP and SIOR took on the remainder of the hills at a brisk pace and I followed. We reached Sunnyside Boulevard and made our way back to GLIRC HQ where they hosted an amazing spread of post race goodies. After indulging in some high carb treats, TPP, SIOR and I headed over to Starbucks for coffee and conversation. Given the greater effort on today's run that made it less conversation-friendly, we still had a lot to catch up on.

Post run - (from left), SIOR, ER, TPP

Photo courtesy of SIOR

It was a really fun time and it's the perfect way for me to do group running. The next adventure for "The Three Musketeers" will be the LIRRC Hangover Run at Eisenhower Park at 9:30 AM. It's a timed five mile run that goes around a one mile route. No bibs, tracking chips, or winners. In this event, everyone's a winner. I'm looking forward to this event as I do every year and it will be more special because my friends will be joining me.

Hill grinding on the Bethpage trail

Not much happening at Bethpage this morning

Today's run (Bethpage trail): 6.4 miles

I've been keeping busy on a big project that's required long days on the laptop and phone. A combination of meetings and deadlines on Wednesday related to the project stole my scheduled window to run. I'd planned to go out for six miles as a final base workout prior to Sunday's race. The idea was to end my taper with this run and spend today focusing on core or upper body. Losing my run window yesterday meant moving my last taper run to today. It was probably for the best, as I probably wouldn't have done that core work anyway.

Running a six mile route around my neighborhood was not appealing, so I headed off to Bethpage to hit the trail. The weather was really cold when I arrived (29° degrees per my car's display). I'd definitely dressed for freezing conditions, so I was comfortable at the start. As expected on a cold Thursday morning, the park was mostly empty. I took off south to start and noted that I felt good, but my leg muscles were a little tight. I hoped that would work out along the run but unfortunately it just got worse.

Despite yesterday's break from running, my legs began to feel like lactic acid containers. I ran a mile south and then turned back the other way, reaching the big hill at around the 1.5 mile point. I'm sure it was due to my uncooperative legs, but climbing that hill seemed especially tough today. Once I passed the point where I started, I continued north to the newer extension.

I often complain about hills, so much so that a friend once told me to do more hill training and less whining. It was a little mean, but good advice. I like to think when I run at Bethpage I am training on the hills. On good days it feels rolling. But on other days (like today) it grinds me down. I went as far north as Old Bethpage Rd. before turning back toward my start and covered 6.5 miles in the process.

I don't know why my legs were so unresponsive today. I was glad that this was practice and not a race. If I can I bounce back by the weekend, I may be able to improve on my performance at the Hope for Warriors 10K two weekends ago. Tomorrow I'll try to do some walking to shake out the built up lactic acid that made today's run so tough. I'm glad I put in some real mileage today. Hopefully it helped reinforce my 10K base for this Sunday.

My favorite running club

From left: ER, SIOR, TPP

photo courtesy of the Petite Pacer

Today's run (Eisenhower Park): 6.1 miles

This morning I had the pleasure of running six miles with two great people who I've gotten to know through the running blog community. I joined the authors of She is Out Running (SIOR) and The Petite Pacer (TPP) at Eisenhower Park, under cloudy skies and light rain. I'm no fan of running in the rain, but I wasn't going to pass up an opportunity to spend time with these two fun people.

I'd met TPP in October at the Oyster Bay 5K and saw her again last Sunday at the Hope for Warriors 10K. Neither of us had met SIOR in person before today, so it was exciting to finally get together. You can tell a lot about a person by their blog, so I was not surprised to find them both to be fun, smart, thoughtful, interesting and kind.

The rain had slowed to a drizzle by the time we set off on our run. TPP had suggested that we start at my pace and then switch it up to hers followed by SIOR's. Since the idea was to run together (I would have had trouble keeping up with them), we agreed that it was better to follow the most common denominator (me). We ended up running an overall pace that even I'd consider slow. But taking it easy helped us freely converse. And converse we did.

Eisenhower Park is under construction, so we needed to reverse direction once we reached a fenced off area. We ran the planned route backward and turned around at the southern side of the construction zone. Usually when I run six miles on my own, the tedium  starts early. I was genuinely shocked when I looked at my Garmin and saw that we'd covered 1.68 miles. At that point I was checking to see if we'd completed the first mile! Time (and distance) flies when you're having fun.

Today's route

We'd passed five miles as we grew close to the parking lot, but we wanted to keep going. We decided to take our second loop around the pond and then finished after either 6.12 or 6.19 miles, depending on if you believe my or TPP's GPS. My Garmin usually under counts by 2.5-3.5% so I'm guessing the actual distance was closer to 6.3 miles. Whatever it was, it seemed to go by faster than any six miles in recent history. That includes last week's 10K.

The icing on the cake was our post-run coffee at a nearby Starbucks, where we continued the conversation for another hour. I don't think any of us wanted to end our morning experience but the day's obligations required it. We agreed to try to do this again, perhaps on a regular schedule. That would be really great because this would be the first running club I'd actually want to join.

Being a down to earth runner isn't always good

 

Today's run (street): 4.3 miles

This week has been a challenge, but I'm not complaining. I'm working on some interesting projects that have required me to spend long days in the city. I'm hoping all the walking I've done this week has provided some conditioning benefit. My running frequency has suffered a bit, but in terms of mileage, I'm not too far off track. Last weekend I decided to move my minimum training distance from three to four miles, so I've done over 8 miles coming into the weekend.

This morning I went out in 40 degree weather for my first run since Tuesday.  I started easy and picked up the pace about midway through. At one point I started thinking about the way I run. Elite runners are fast because their form keeps them off the ground most of the time. In comparison, I find that I spend a lot of time on terra firma. In the moments that your foot is touching the ground, you're not moving. That explains a lot about my speed.

I experimented with opening my stride hoping that it might make a difference. After reviewing my Garmin's performance data, it looks like it did improve my pace from that point forward. Tomorrow I'm excited to run with the authors of two excellent blogs: She is Out Running and The Petite Pacer. They are both great runners and I hope I don't hold them back too much. I'll try to convince them of the benefits of long slow distance.

Data visualization drives a decision

Downward slope

I downloaded my Garmin after yesterday's race to get a breakdown of my run. I'm a big fan of data visualization. When I looked at the cadence chart the data showed exactly where my base training had come up short. At 3.2 miles (almost the exact distance of my daily training runs) my average cadence had dropped from 89 to 85 SPM.

The shortcomings of my running routine could not have been clearer. I wasn't putting in enough distance in my daily training. I've always prided myself on the fact that I usually run six days out of seven. While the frequency is high, the distance is middling. It's a healthy routine, but not one that produces great race performances.

I'll admit that it's hard to break a running routine that's been a way of life for five years. Clearly a change is due. I'll continue to aim for longer runs on weekends, and try to increase my weekday distances. I'll aim for the same 18-20 miles a week, but will only run three days instead of four. If I could get closer to a 5 mile average run, my performance might proportionately improve.

One of these routes is not like the other

Post run relaxing

Today's run (street): 3.36 or 3.41 miles

It was another mid-high intensity run this morning. My heart rate (the only performance metric I'll view while on a run) was close to target, and I knew I'd be happy with my finish time. A quick look at the Garmin confirmed that I'd managed another good run. I cooled down by the pool when I finished and tried mapping my route using the Gmaps web app on my phone

I was pleased to see that the Android OS was finally supporting Gmap's functionality. That allowed me to record my distance and calculate my true pace. I liked what I saw: 9:05. Although I worked for it, getting there didn't feel as hard as I thought it would be. Looking a gift horse in the mouth, I mapped the run on my laptop after I'd finish showering and discovered a surprising disparity in distance.

Distance: Android version

Web version, same route

For some reason, the route on my laptop registered 5/100ths of a mile shorter than the exact same map on my phone. Weird and disappointing, because that small disparity meant my average pace was actually 9:12. Not bad, but not what I wanted to see. I remapped the route to see if I'd somehow missed a street, but the distance came up the same each time.

So what if the phone mapping is actually the correct measurement? That would be nice. But I use the web version as the standard, so I'll have to go with that. In the end, the difference is measurement is minimal. Unfortunately, the difference in pace is not.

Full contact running on the Bethpage bike trail

Today's run had its ups and downs

Today's run (Bethpage State Park): 7.25 
1,600th Emerging Runner Post!

Speed is one thing and endurance is another. I've made progress on my pacing over the past week, but that was with distances ranging from 3.1 to 3.4 miles. Doubling that distance reveals opportunities for improvement. This morning's workout confirmed my need to focus on base mileage. The good news is that I'm not as far off from my target as I thought.

Bethpage at 7:30 AM is usually a quiet place, but when I arrived, the parking lot was 3/4 full. Judging from the streams of people with stadium chairs and kids walking with soccer balls, I assumed there was a tournament or clinic happening at the athletic fields. It didn't look like they were charging for parking, so I was lucky to get there before the whole lot filled up.

According to News 12 Long Island, the temperature was 64 degrees and, at that hour, the bike trail was mostly in shadow. I wore my new Virratas for the first time on pavement (yesterday's run was on the track), and they felt very good. I had none of the problems I'd experienced with the Kinvara 3's (when new) during my half marathon training. Then again, those issues could have been with my feet, not with the shoes.

My first half mile was a little rough, and I wondered if I was pushing myself too much following three consecutive hard workouts. I decided to ignore the discomfort because the transition from anaerobic to aerobic breathing is sometimes difficult. Once I hit the first mile, I knew I would be able to manage the planned distance.

Bethpage's bike trail is rolling, and the north trail is predominantly uphill, all the way to the end. Me and my friend KWL ran it all the way to Woodbury a couple of months ago, and that was brutal. Today, I viewed the hills differently, because I knew all the elevation I was experiencing on the way up would come back as downhills on my return. Yet there were times when the trail seemed to run uphill in both directions. While that was true, I had few troubles along the route.

My plan was to run as far as Washington Ave, turn around and come back, a distance of about 7.25 miles. I had the path more or less to myself on the way north, except there were some reckless riders zooming along without helmets. That's a dangerous decision when you're exceeding 20 MPH on downhills. By the time I changed direction for the return leg, there were numerous other runners, walkers and even more cyclists.

At around the five mile point, where the path is only wide enough for three people, I saw a man and two women running in my direction. They were running three across. As they came closer, I decided we had a math problem. I kept expecting the woman on the left (who was lined up with me) to drop back or move up to her right. But fifteen feet away, they were still spread out across the trail.

I moved as far to the right as I could go without spilling onto the shoulder, so I stood my ground. The woman tried to squeeze by, but she miscalculated the space and her arm caught the point of my elbow. I have very hard bones so I'm sure that hurt, although I didn't feel a thing except contact. It was too bad that we'd bumped, but she saw me coming for at least 30 seconds.

The remainder of the run was contact-free and I felt like I was moving well throughout every section. I focused on shorter strides on the two final hills, and tried to maintain my normal cadence. In the end, It was my longest run of the year. I barely squeaked in under 10 min/mile but this run wasn't done for performance. This week has been about speed, distance and a few hills. I'll need to keep it up this coming week. After all, you're only as good as your last run.

My Garmin speaks the ugly truth

It's a match

Today's run (street): 3.25 miles

I'm incredibly annoyed with my Garmin today. I did this morning's run and, as always, recorded my distance using GPS. I always assume the watch will under-count my distance, so I wasn't upset to see the indicated time and pace. Usually, after Gmapping my route, I'll need to add about 3% more mileage to the calculation. That often makes the difference between a good and mediocre pace. Today, both the Garmin and Gmaps said exactly the same thing, and what they said wasn't good. I missed my targeted pace by 23 seconds per mile.

There's no reason why I ran this slowly today. I'd tried to focus on form and turnover. The weather was perfect, so heat and humidity were not a factor. Perceived effort was on par with my better runs and I even ran the last quarter in a semi-sprint. But in the end, my performance did not match up to expectations. Tomorrow is my last run before Sunday's race, so I need to make it count.

Zeotrope concept (left), example (right)

I took most of the day to be with the family and we spent it at the Museum of the Moving Image in Astoria, Queens. The experience was great, and I even got to play with a nineteenth century zeotrope of a man running. But instead of marveling at this 100 year old wonder of technology, I was watching his form and thinking how he should shorten his stride.

City trek dwarfs morning workout

And the day ain't over...

Today's workout (elliptical): 25 minutes + 7 miles city walk

I figured I'd be covering some ground today, but I had no idea that I'd travel over seven miles in the city on foot. My meeting locations varied between east 53rd Street and Spring Street, with a couple of other spots in between. I could have used the subway, but I didn't see the point of that when I could just as easily walk.

Before I left for the city, I did an elliptical session. I wasn't thinking about the fact that I'd be getting a second workout later. The Fitbit recorded a couple of miles from the elliptical and, fortunately, I remembered to bring it with me when I left the house. I'd forgotten to take the Fitbit on Monday when I covered significant territory around Manhattan. The Fitbit recorded none of that, causing me to look like a slacker on the Fitbit dashboard. But today was a different story.

Should have that distance number over 10 miles tonight

Avoiding redundancy on a neighborhood run

Today's run (street): 5.4 miles

After yesterday's gloomy weather, it looked like spring was finally coming back. It was still fairly chilly when I stepped outside this morning, but it was mostly due to the wind. I stood in a patch of sun to stay warm, while my GPS took its time finding a signal. Today's route was around the neighborhood, and I thought about the combination of roads I'd have to take to meet my distance goal of five miles.

I wore my Brooks Pure Drift prototypes, rather than my Kinvara 3's. Lately, I've been wanting less cushioning in the forefoot, and the Drifts are similar in that respect to my old beloved Hattoris. I definitely prefer to run with shoes that have a low "stack height" and minimal cushioning in the mid-sole. The Kinvaras have been excellent, and I'm a stone's throw away from 500 miles with them, but I've been missing the feel of a firmer-landing shoe.

I felt great from beginning to end on today's run. It was one of those rare training runs where I felt I could just keep going all day. Adventure Girl used to call it "perpetual motion running." Since I only planned to run five miles, I figured I could spend some energy on speed. I opened up the throttle every few minutes without affecting my high energy level, and it paid off when I saw my overall time.

I managed to cover most of the streets in my immediate neighborhood without doubling up too much on any one road. For some reason, I dislike running on the same section of road twice during the same run. Even if it's just seeing different houses and cars on other streets, it's still a different view. I noted that my hip seemed completely fine, and I can probably stretch my base runs to six miles now. I haven't been to Bethpage in a few weeks, so it's a possibility for tomorrow. I guess it's as good a time as any to buy my 2013 Empire Passport

Correlating my sleep time and run fatigue

Frozen Fitbit

Today's run (street): 4.8 miles

Yesterday afternoon I checked my activity progress on the Fitbit only to discover that the readings hadn't changed since morning. The numbers displayed at 5:00 PM were almost the same as they were at 9:30 AM. I took some steps to see if they would record but the numbers didn't change. I connected the Fitbit to my laptop using the USB charging cable and that seemed to jolt it back to life.

I was happy that the device was working again, but disappointed that I wouldn't get "credit" for the steps, miles and flights of stairs that didn't get captured yesterday. I'll watch the display a little more closely, now that I've had that experience. It was working fine this morning and I took it along during my run.

I again recorded my sleep pattern overnight and saw that I'd slept a total of six hours. The good news was that I "only" woke up six times instead of twelve. The Fitbit site assigned me a sleep efficiency rating of 96%, far better than the first time I tracked my sleep cycle.

Perhaps it was a lack of sleep time that factored into the fatigue I felt during today's run. I'd averaged 40 more minutes of actual sleeping time prior to last night. After yesterday's rest day, I expected to feel slightly more energized than normal, but a few minutes into the run I knew something was missing. I set the best pace that I could, determined to cover my distance target of 4 miles.

When I run, I often think about racing and how I'd feel if I was in a race in that moment. I'll often tell myself that I could manage more speed, if needed. Depending on the distance, I can usually muster enough energy to pick up my speed and sustain a better pace. Today I hoped I had enough in the tank to get me through the route I'd planned.

I was determined to get in a full workout and, after making a few loops through my immediate neighborhood, I crossed into neighborhood #2. I had this dual sensation of feeling tired yet ready to cover my distance. There were a few points where I could have cut the run short, but I didn't. In fact I ended up running almost a mile longer than I expected. I was plenty tired by the time I got home and a little puzzled that my heart rate didn't reflect the perceived effort I was experiencing.

Tomorrow I may keep it short, as I'm close to reaching my weekly mileage goal. If my energy returns I may even do some speed work. I'll try to extend my sleep time 40 more minutes and get back to average. I think that contributed greatly to my tiring experience this morning.

Late start, stiff winds and some different roads to run

Today's run (street): 5.25

It took a while, but I finally got myself out the door for a run this morning. All week long I'd looked forward to getting a couple of extra hours sleep. I slept well last night and still got up up relatively early. Somehow the time slipped by and I found myself standing outside at 9:30 AM, waiting for my Garmin to acquire its signal.

I wasn't thrilled to do another weekend run in the neighborhood, but my procrastination had limited my options. My plan was to run a nearby loop and then head over to neighborhood #2. I set off running north and quickly encountered stiff winds coming from that direction. The weather report said that these winds would make it feel like 27 degrees and they were right. A slight change in direction made a huge difference. Without the wind, the warming sun made it quite pleasant.

Before long, I was running through the southern neighborhood, battling headwinds in one direction and appreciating the tailwinds when going the other way. Halfway through, I checked my distance and saw that I hadn't made as much progress as I'd liked for the time I'd been running. I picked up my speed from there and finished within acceptable range for my overall pace.

It's supposed to be even colder tomorrow so I'll need to give some thought as to where I might run. It was nice to get out of the neighborhood today for a slight change of scenery. Perhaps I'll find a more interesting route tomorrow.

Increasing fitness by not running

Building fitness can be relaxing

I believe it's okay to take an ad hoc rest day every once in a while. I did it today and I feel no guilt whatsoever. While I will probably never get up and say, "Hey, I feel great, I think I'll skip my run", I didn't rest this morning because I was feeling weak or ill. What I felt was under-rested and I concluded that I'd be better off taking it easy, rather pushing hard and inviting a problem.

When you think about it, a day of rest is often better for you than a single day's run, because recovery periods are when your body actually builds fitness. That's holds true for a day or even two, but then it starts to go the other way. I've been doing workouts six days a week for the past few years. That generally works for me. My average run  (accounting for shorter distances on weekdays and longer ones on weekends) is 3.3 miles. This seems like the right amount of exercise to keep me fit and (knock wood) to prevent me from sustaining injuries.

The reason I don't feel any guilt for skipping my today's run is that I know I'll be back at it tomorrow. However, my decision puts me three miles behind in terms of reaching my weekly target of 20, but I can probably make up some mileage on Saturday or Sunday. In the meantime, I'm happy knowing that taking a rest was the right thing to do this morning.

Defining a long run

Goodbye Boston, hello vacation 

Today's run (street): 5.6 miles

For all intents and purposes, my business year has ended. I finished things up with a trip to Massachusetts on Thursday and Friday and I'm now - officially - on vacation. It was a necessary excursion, but the travel logistics and schedule were tough. Shortly after leaving South Station, I took this shot of the gloomy conditions that I was leaving behind.

I wasn't able to run during the time I was away, so I looked forward to getting outside this morning. We have plans that will prevent my running on Sunday and Monday. I wanted to get in at least five miles before taking my next break. The other night I was asked whether I considered five miles to be a long run. I wasn't sure how to answer that, but I finally decided that five miles represents the dividing line between short and not-short.

I went to bed early and took the opportunity to sleep a full eight hours. My wife and kids had early morning activities so, after they left, I got ready to run. The temperature was in the low 30's when I stepped outside. Although I wore layers to stay comfortable, the five minutes it took to acquire a GPS signal forced me back into the garage to stay warm. I hoped that the first few minutes of my run would help me generate some body heat.

Prior to leaving I'd mixed a packet of chia seeds with an ounce of watered down coffee. I think that chia can make a difference. Chia seeds may not enhance performance, but they do seem to provide some sustainable energy. It could also be that, after taking two days off, my body was rested and ready for a run.

I covered the neighborhood as much as I could without duplicating too many streets. I kept waiting to feel fatigued throughout the run, but I felt almost as strong at mile five as I did at the start. My route took me to the northern part of my neighborhood so I extended the loop and finished with a little extra distance. I ran the last half mile briskly and that helped put my overall pace within normal range.

I felt great on today's run and I regret that I won't be back on the road until Tuesday. Still, I'll have some vacation days that will provide me the opportunity to run longer distances, leading up to the Hangover Run on January 1st. 5.6 miles may not be a long run, but it's the longest run I'll be doing for a while.

Autumn running brings front loaders and pumpkin bread

Today's run (street): 5.3 miles

A runner's reward

 I needed to drop off my car for inspection this morning and that delayed my run until 9:00 AM. That was no big deal, but the world is far more awake at 9:00 than at 7:00. People who are awake tend to drive their cars, so the streets were busier than I prefer. Worse, the tree trucks and front loaders were also out in force, attending to the remaining pockets of destruction caused by Sandy.

On weekend runs in the neighborhood, I usually stay fairly free-form in terms of my route. That way I can run distances as they play out: 4, 5, 6 miles or more, depending on where I am when I decide to head for home. Today I pre-mapped the streets I'd follow, because I wanted to cover at least five miles. With a couple of exceptions, my run went fairly well.

The temperature was in the 40's but it still felt cold, probably because there were strong winds blowing from the north. The combination of wind and a slightly rising road made for a tough start. At one point something - a leaf, twig or small acorn - hit me in the face, right above my brow. Fortunately, my glasses had prevented it from hitting my eye.

Along my route I encountered crews of workers that were blocking the road with their trucks and equipment. I saw a few large sanitation trucks that were picking up some remaining debris. I avoided a couple of streets that looked impassible, and stayed on the sidewalk while I managed around a particularly big work operation. I ended up running my distance a little faster than I thought I might. I wasn't concerned about speed, but it was nice to see that I beat my performance expectation.

When I got home, my wife and kids were in the process of preparing their famous pumpkin bread that they bake every year around Thanksgiving, for friends and family. To a ravenous runner, the smell of pumpkin, ginger, nutmeg and cinnamon was intoxicating. After a quick shower, I was treated to one of the mini-muffins that were baked from the batter. Recovery food doesn't get any better than this.

Athlinks bemoans declining race times

Today's run (street): 2.5 miles

I had a funny exchange yesterday with Troy Busot, the founder of Athlinks. This website aggregates race results and allows members to compile a rich racing history. Athlinks members can comment on their race experiences and compare their performance to "rivals" (other members who have participated in 2 or more of the same races that you've run).

The reason I contacted Troy was that he'd sent an email that, in a tongue and cheek way, chided runners for what he called, "an alarming decline in U.S. racing performances in distances across the board." He compared average finish times for the most common race distances plus Olympic, Half and Full Ironman Triathlons. He made his point but I noticed that his times for half marathons were exactly the same as for 10K's, an obvious typo:

Average Times for Leading
Race Distances from 2009-2012

Distance	2009	2012	Change	% Change
5K Run	30:30	31:47	+1:17	+4.04%
10K Run	1:01:01	1:02:28	+1:27	+2.34%
Half Mara	1:01:01	1:02:28	+0:18	+0.15%
Marathon*	4:33:18	4:33:13	-0:04	-0.03%
Olympic Tri	2:52:53	2:55:55	+3:02	+1.73%
Half Iron	5:59:43	6:05:49	+6:06	+1.73%
Ironman	12:49:44	13:11:39	+21:54	+2.77%
* Marathon times were the only notable improvement.

Troy quickly fell on his sword after I sent him a note about it and he gave me the correct figures for 2009 and  2012, which were 2:15:16 and 2:16:40 respectively. Troy wrote, "Yep, I have quit the company in typo-shame." I've never run a full marathon but I have run the other distances. In every case (except my first half), I've beaten the average, both for 2009 and 2012. So perhaps I'm not as average as I thought, although my scores would not be so favorable were the comparison more age and gender based.

Speaking of average, my pace this morning was exactly that. The temperature was 35 degrees with a noticeable breeze, and I wore some extra layers anticipating the cold. I stayed comfortable throughout the run and didn't really have a clue how fast I was going until I looked at my heart rate near the end. I saw that I was at 80% of Max. I tried to get it to 85% in the remaining quarter mile, but I didn't quite get there. Even so, my average morning run still gets me around the course 45 seconds per mile faster than the 5K average!