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.

Fast track to performance gains

Flow of the workout

Today's workout (track): 1 mile tempo, 12 x 100M, 1.25 mile cool-down = 3.1 miles

This morning I headed out early to the local track to run intervals and tempos. I took the Virratas out for their first run, and thought they responded well to fast pacing. My plan was to run one mile at 5K race pace, which I'd follow with intervals and a cool-down run.

The track had a few walkers and a couple of runners when I arrived. I got started quickly on my tempo warm up and found a pace that felt hard, but sustainable. I locked into that pace for four laps, guided by perceived effort. Along the way, I passed everyone including the other two runners on track. After last Sunday's low point of the race, when I was being passed left and right around mile five, it felt good to be the one who was doing the passing. I averaged 8:18 for the mile.

Next, I ran a set of 100 meter repeats, averaging 6:40 per mile. I was surprised when I later looked at heart rate data and saw that I'd averaged between 74-80% of MAX. Knowing that, I can probably get my pace down to 6:25, while still staying under 90% MAX. However, I'll probably keep it to 8 x 100's for that session.

I finished the workout with a 1.25 mile cool down, run at a moderate (9:21) pace. In total, it wasn't a lot of distance, but the intensity made up for that. I'm planning a long run tomorrow, either on the Bethpage path, or another route that will facilitate a 6+ mile distance better than my neighborhood roads. My performance has improved greatly for runs between 3-3.5 miles. It will be interesting to see how my pacing holds up, when I double that length tomorrow.

Elite sale yields bargain Virrata

New running shoe day. Guess which ones are mine.

Today's run (street): 3.4 miles

So far so good on the training front. This morning I went out with expectations of matching my recent pace range and I managed to do that. When I first entered time and distance into the pace calculator, I thought I'd missed the mark. I quickly realized I'd entered the time incorrectly, adding in an extra minute. It turned out that I'd actually exceeded my target and ran today's distance four seconds per mile faster than yesterday's.

I assign two factors to these recent gains: a constant focus on pace (via perceived effort, not watching the Garmin's display) and the continued recruitment of fast twitch fibers in my leg muscles. In other words, I'm thinking about running fast and building fitness. Runners come closest to their potential when racing and an active focus on speed while training does the same thing, to a lesser degree. That's why I'm not yet achieving sub-9 training runs, but I'm getting closer.

The family went out for a "Next to the last Friday before school starts" lunch and afterward we swung by the Gallery at Westbury Plaza. I wanted to check out Sports Authority's new SA Elite store that only sells adult size sports apparel and running shoes. I had no intention of buying anything, but they were having a sale, so I checked out the deals.

I've been looking for a lightweight running raincoat for a while. My venerable ASICS rain jacket committed zippercide last year and I've been on a quest to replace it. SA Elite was light on raincoat options, but they had some genuine bargains in their shoe section.

The store was running a sale, and this was no bottom of the barrel clearance. I did a double-take when I saw a pair of Saucony Virratas priced at $79 with a label next to it saying 20% off as marked. The best price I've seen on the web for these shoes has been $78 plus shipping. I asked for a pair in hi-viz yellow, but they only had my size in black. I was disappointed, but I tried them on the treadmill and liked the way they fit.

At the same time, my wife found a pair of ASICS Nimbus-14's that fit her well and were priced amazingly low with the included discount. I've been on her to replace her GEL-2160's that probably have more than 2,000 running miles on them. I'm serious, you should see them.

I'm thinking about doing a long base run this weekend and a shorter speed workout on the other day. I'm pleased with my progress and excited to be runnning in shoes with less than 500 miles on them. I hope the Virratas feel as good on the road as they did on the treadmill today.

Today's good run becomes tomorrow's expectation

The daily burden

Today's run (street): 3.5 miles

I was a little sore this morning, possibly because my last three runs were done at high effort (though perhaps not at high speed). I haven't put up any sub-9 runs yet, but I'm moving in that direction. My saving grace today was the need to have an early call to Asia. That allowed me an extra hour to loosen up my leg muscles before my run.

Have you ever thought about how great everything seems after you've completed a fast run? You can point to it with pride and feel good about what you've accomplished. But as they say in Hollywood, you're only as good as your last movie. And when training for a race, you're only as good as the last time you ran. Time for resting on your laurels = 1 day. And that day ended for me this morning at 8:00 AM.

I started to prepare for my run after completing my call. Wednesday's good experience had now become today's burden. I knew I couldn't default to my easy running pace and, while I wasn't planning to go all-out, I had mentally set my target. I was determined not to come up short. 

A slight soreness in my legs threw me off on the first half mile. I willed myself to run faster, but I'm not sure the effort fully translated. I do know that when I'm actively thinking about performance, my speed will usually move into the acceptable range. My goal today was to do better than that, so I kept up the mental pressure and hoped that would yield a good result.

I was pleased to see that I ran 5 seconds per mile faster than yesterday. It was great to repeat a good performance and I feel I'm heading in the intended direction. I have the rest of the night to enjoy today's gains. Tomorrow morning, expectations return.

I think, therefore I pace

Today's run (street): 3.4 miles

Okay, now we're talking. After two days off from running, I went out this morning for the first time since the Dirty Sock race. I recognized the need to keep my focus on speed, despite having come off a fairly hard run. It's always a lot easier to do that if you're energized from the start. I was pleased that my legs responded to the challenge.

Everyone has a different default running pace. By that I mean the speed that you'd run if you didn't care about performance. It's probably what people think of as their easy pace. For some, "easy" is 8 minutes a mile. For me, it's much slower than that. When I need to run faster, I know I need to think about running fast. No zoning out and letting my legs carry me along. I've read that running performance is largely mental and my experience supports that.

Today I put priority on cadence and form. I focused on holding a faster pace than my body naturally wished to run. At times, my mind would drift and I'd detect a little deceleration. I dialed back up to "urgent" and tried to reengage my focus. This was not running at 10K race pace, but it was much faster than I've been averaging.

For all that work, I'm still worrying about my readiness to sustain that pace for 6.2 miles in Northport next month. With James Street, Waterside Ave. and Pumpernickel Hill in the mix, I'll have to do a lot more than I did today. But it was a start.

To whom the Cowbell tolls

Pointing out James Street after last year's race

Oh, how the mighty have fallen. After some high mileage training weeks leading up to last weekend's Dirty Sock race, I haven't run a step. Mondays are my usual rest day, which works out great when I race on Sundays. Today started early because I had to get into the city for some morning meetings. I went to bed thinking I might run today, but I slept until 5:15 AM, which didn't give me enough time.

Even without running, I still managed to meet my daily requirement of Fitbit steps. Between my backpack and sports jacket, combined with 81% humidity, I worked up quite a sweat. So it was sort of like a workout, but I really missed the part where I get to shower.

Tomorrow I'll officially start my Cow Harbor training. The good news is that I'll be starting on two days rest. My plan right now is to go out early enough to minimize the heat. If I'm training for this race, I'll need to start pushing the pace right away. As for the hill training, that can wait another day. But not too long, James Street looms large.

Redemption run gives hope for Dirty Sock

The Garmin doesn't lie

Today's run (street): 3.25 miles

With the Dirty Sock trail race happening on Sunday, I had one more run to go before I finished my taper. Yesterday's run was disappointing and Tuesday's was similarly mediocre. I've recently committed to pushing harder on training runs and that paid off last week with a few decent runs. When I say decent, I mean closer to last year's average pace. Certainly not as fast as the paces I used to hit while training for a race.

The Dirty Sock is a tough course. The terrain isn't especially bad for trails, but the steamy weather conditions and muddy paths make the last miles difficult. My time expectation for this race is about 59 minutes, which is five minutes slower than my 10K PR. I'm usually happy to run it in under an hour. Actually, the way I've been running, I'm concerned about breaking 62 minutes.

Hope came this morning with a run that redeemed my spirit. The difference today was that I kept a steady focus on speed. It wasn't an impressive pace for many readers of this blog, but it was almost a minute per mile faster than what I "achieved" yesterday. I'm not going into Sunday's race with a string of fast runs under my belt, but at least I ended training on a good note.

Memories of a rainy run

Soggy and humid morning, or so I remember

Today's run (street): 3.1 miles

This morning's run seems so long ago that I'm thinking about it like it was yesterday. I wanted to go out very early to beat the rain, but my stalling worked against me. I walked outside and felt a few light drops. The sky was uniformly gray and I didn't see any dark clouds that might drench me. Despite my aversion to running in rain because it distorts my vision,  I couldn't face a treadmill workout today.

My weekend of hard running has taken its toll. Even with a rest day on Monday, my leg muscles felt tight. Although I had no issues with either anaerobic or aerobic energy levels, I couldn't generate the speed I was hoping to maintain. Exactly one mile into the run, I felt a pebble that had landed in my shoe. I tried to ignore the problem, but I finally gave in and stopped to clear it. By then, the light rain had become steadier and I wondered how bad conditions would get.

I had the opportunity to head directly to my house at that point, the loop I was on took me within a block. Instead, I decided to run my route regardless. I hoped that the rain would lessen, or at the very least, that it wouldn't turn into a thunderstorm. Lightning is scary when you're out running on the street, miles away from shelter.

The rain did get worse, but the thunder held off until I got home. The rest of the day was spent either on the phone or staring at my laptop. I'm glad I got out today, but I didn't get through the conditioning run I'd originally planned. On the bright side, the humidity was extreme and that provided some good preparation for next Sunday's race.

Speed work, if you can call it that

Running in circles makes me lose my tempo

Today's run (track): 3.1 mile tempo, plus 5 x 100m - total: 3.4 miles

This morning I headed to the local track to run intervals. I was not looking forward to the workout, but if I wanted to improve my speed, I needed to do my homework. Conditions were good, 66° with indirect sun, so I had little excuse to take it easy. I decided to start with a few warm up laps before taking on intervals. I ended up doing a three mile tempo run, followed by 5 x 100 meter strides, run two minutes/mile faster than 10K race pace.

I was concerned that I'd be dealing with some leg fatigue after yesterday's run. Once I got going, I became confident that I'd be okay, although I was frustrated with my limited ability to hit my targeted pace. By the second mile, I was running faster. There were others on the track during the time I was there, but it never got crowded. I appreciated having the first lane to myself, with no need to shift around any walkers or slower runners.

Observations: 

1. I'm still running pretty slow these days. My goal was to break 27 minutes, but I didn't succeed. However, I did run negative splits, with a 9% improvement between miles 1 and 3.

2. I was able to meet my speed target on the intervals. While these runs felt faster than the 6:54 average I recorded, the last time that I did speed work, I averaged under 6:30. Like I said, I'm still slow.

Overall, I'm pleased with this weekend's training. With a couple of tough workouts coming up this week, I feel like I'm setting up well for the competition on the 18th.

DNA extraction and the dog that didn't bite

My morning encounter

Today's run (street): 3.4 miles

For some reason I had it in my head that yesterday was Friday. When I got up this morning I started thinking about where I'd go for my first weekend run. The rain had moved out, and it looked like nice weather to be outside. I started going through my options for running venues when I realized that it wasn't Saturday and I had to get some work done.

My business schedule is less structured than when I worked in an office in NYC. I can now start my day with a run after the sun has come up, or work for a while and run later in the morning. My schedule also gives me the flexibility to do things I used to miss because I'd be in the city. Today I was able to attend my son's presentation on gene extraction methodologies at the Cold Spring Harbor DNA Learning Center. The most impressive thing I ever did at summer camp was make a lanyard.

Saying goodbye to his Beijing camp mates

Before all of that, I went for a run. Since I didn't have the time to cover much distance, I stuck to the neighborhood and followed one of my usual routes. A few minutes into the run I was accosted by an unleashed dog whose owner called to me, "He's only going to follow you to the end of the street." This annoyed me. Recently, I read a quote by Peter Magill, a Running Times columnist, who said, "Every dog that has bitten me was a dog that didn't bite."

The dog kept its distance and it stopped as the owner had predicted. I was soon past my first mile, enjoying cooler conditions than I'd expected. I tried to carry over the intensity of yesterday afternoon's treadmill workout into today and was only partially successful. I ended up pacing in the acceptable range. If the weather holds tomorrow I'll probably return to Bethpage and do a hybrid run on both the dirt and the bike trails. I need to build my base in preparation for the upcoming 10K that happens in just two weeks.

Speed decline, is it nature or nurture?

My story in two axis

Today's run (street): 3.25 miles

Conditions were near perfect when I went out for my morning run. The 7:00 AM sun was low enough to cast great shade along my route and the air felt cool and dry. The neighborhood was quiet, with just a few cars and a couple of walkers. I moved along well and thought about the fact that my running performance has suffered greatly this year.

A few years ago, I would average around 27 minutes for a three mile training run. Over time, my normal training pace has edged up almost a minute per mile. Back in 2010, I went out on every run with a pace goal in mind, and I was racing far more frequently than I have this year. That may explain some of the loss of speed.

I'm not willing to concede any performance drops to age at this point. Although I really want to run for the sake of running, I do find myself thinking about turnover and stride length while on the road. If I look at my pace on the Garmin during a run, I'm often surprised by how much effort it takes to break 9:00 minutes.

Every time I find myself on a run, struggling to stay under 10:00/mile, I vow that I'll go back to doing core exercises and speed work at the track. Somehow I forget that commitment once I get home. I think it's time to get serious about speed. I'm due to run with a friend this week who tends to push me past my comfort zone. Maybe that's exactly what I need right now.

Bethpage base run and a new pair of "minimal shoes"

Justifiable replacement

Today's run (Bethpage State Park): 5.9 miles

I needed to do some base building as I prepare for my next race, so I headed over to Bethpage State Park to run on the northern bike path extension. The section between the trail head at Bethpage and Old Country Road is a personal favorite, due to its rolling terrain and handy distance markers. For longer runs, I cross Old Country Road and follow the trail as far as I wish. Running it to the end leaves me off near my neighborhood, allowing me to run all the way home.

I managed to stall a full hour between the time I dressed for the run and when I actually left for Bethpage. Despite a later start, weather conditions were still good, due to heavy cloud cover that prevented direct sunshine. Humidity was much lower than yesterday and I felt energized as I took my first steps from my car to the trail.

My goal today was to cover 5 to 6 miles at around a 9:30 pace. My ideal goal pace for the Dirty Sock 10K is 9:00/mile (or better), which will be hard for me to achieve. The best I've ever done on that race is 58:26, so I'd need improve on that by over two minutes. My 10K PR is around 54 minutes, but that race wasn't a trail run held during the dog days of August.

I didn't quite make today's performance goal, but I came respectably close. The cyclists were out in force today and I was disappointed by their lack of trail etiquette. A number of bike riders zoomed by very closely without giving any "On your left" warnings. Are they aggressive because they resent all the runners and walkers on the path, or are they just selfish?

I was humbled early on by a woman who came off a wooded trail that intersected with the paved path. She appeared to be running at an easy pace as she came up beside me, but left me in the dust before ducking back into the woods. It's really hard to gauge a runner's speed just by looking at them. There was a group of high school aged boys doing a training run and a family of five (including three pre-teens) who were all running together.

Most of the run felt good. It was only near the end, when I faced the biggest hills, that I began to feel some fatigue.  Despite that, I pushed hard during the last half mile and I was surprised to have the energy to do that.

After I got home, my daughter and I went to Modell's in Plainview to buy ourselves new pairs of pool shoes. My old pair (top), which served me well for at least five years (including time on the road as "poor man's" minimalist running shoes), are starting to disintegrate. I'm not sure I'll use my new pair for running, but they worked great in the pool today!

Conditions are ideal for Dirty Sock race prep

 

Today's run (street): 4.3 miles

I've been thinking a lot about the upcoming Dirty Sock 10K that happens on August 18th. I ran this race in 2009, 2010 and 2011, but I skipped it last year. It's a hard race, especially at the end. Conditions are often brutal, with temperatures near 90° and humidity approaching 100%. The website describes the course as "USATF Certified and Sanctioned, fast, mostly flat, picturesque, wooded trails, only 2/10 mile paved. Splits, water stops, road apples, uneven terrain." The last mile of this race always feels as long as the previous five.

The best way to train for this race is to run the course, something I'm planning to do with my friend Mike in early August. In the meantime, I'm planning to push my speed more often in the training runs I do each day. This might be a challenge if the weather remains hot and humid, as it was today.

This morning I got out reasonably early. After a quick loop around the northern section of my neighborhood, I headed to the middle school where I could access the foot path that leads to a service road and local business park. I ran the park loop clockwise so I could take on all the elevation at once, rather than endure the long, but less steep elevation I'd encounter going the other way.

During yesterday's run I'd moderated my pace in response to the sweltering heat. Today was slightly cooler and the sun was less intense at the start. I focused on my turnover, in hopes of achieving a faster pace than Friday's. I ended up with a respectable time, although I'd like to improve that by 20 seconds per mile by race day. I'm thinking of visiting Bethpage tomorrow and hoping that this evening's rainstorm will chase away the heat and make running conditions more pleasant on the running trail.

Run turned back at the driveway

Today's run (treadmill): 3.2 miles

I watched the garage door rise to reveal a rain covered driveway this morning. It had looked dry from the window, but that was obviously an illusion. I wasn't interested in running in rain-soaked conditions that would obscure my vision and saturate my shoes and socks. I turned around and headed upstairs to wait for my wife to complete her treadmill workout.

Today's schedule was tight and I wanted to get in my run before I got caught up in business calls. I've been fighting a mild chest cold and could have used that as an excuse to skip my workout. I figured that I should at least try a run and see how it felt. I wasn't looking to push myself too hard after a couple of hard runs on Tuesday and Wednesday. I did pretty well, but I skipped the progressive speed increases.

I'm getting closer to my next race and I know I should begin tuning my runs towards speed. I'm not sure which approach to take: intervals or tempos. I can't really do speed work at the track during the week because school is still in session. If the weather is clear over the weekend, I may head to the high school. I think all the hill running I've been doing is helping to build my fitness, but I don't know if it's also helping my speed.

Treadmills aren't always portals to boredom

Today's run (treadmill): 3.2 miles

For all my complaining about the treadmill as a portal to mind blowing boredom, I'm sure spending a lot of time on ours. Back in 2011 I managed to go almost six months without using the machine. This was a well timed period between spring, summer and fall when it never seemed to rain at 4:00 AM. On those rare occasions where the weather interfered, I'd default to the elliptical machine.

Once again, the weather kept me inside today. 22 degrees plus wind chill made for an uninviting outdoor running experience. I could have bundled up and gone outside but I wanted to focus on my speed. I don't run as fast with lots of layers and I'll need to figure that out for the race on Saturday. I'm hoping for a mild turn in the weather and I'll stay inside the registration area as long as I can to minimize the amount of time spent in the cold prior to the start. Those five minutes waiting for the gun can get downright chilly.

This morning's treadmill run started fast and I didn't let off my speed until I'd finished. I increased pace incrementally over the last five minutes, pouring it on at the end to simulate the finish of a race. I'm feeling primed at this point and I'm looking forward to returning to the road tomorrow. I'm still not a treadmill lover but, with these speed focused runs, I'm rarely bored.

Snowflake looms so no backing down

Speed play and HR % of MAX

Today's run (treadmill): 5.2 miles

I was up at 5:30 AM this morning and the winds were howling. The news stations were talking about wind chills in the teens and I decided to return to the treadmill rather than face the bitter cold. I'm hoping that by next Saturday the weather will be milder. Many races provide no warming shelter prior to the event. I'm happy that the Long Beach Snowflake race is staged in a school gym located across the road from the starting line.

Yesterday's run was done a little faster than my normal training pace, and I debated whether I should take down the intensity today. I decided to go the other way and started at a brisk pace, maintaining that speed until the 15 minute mark. I increased it 8% at that point for about five minutes. I then backed down to my original pace and held it until I surged again for the final five minutes of my run.

I often question the accuracy of the treadmill's display because the effort required on the treadmill seems greater than an equivalent pace on the road. That's okay, I'd rather have it under-count the distance than gain a false sense of my performance. So my 5.2 miles was hard earned and likely lower than the actual "distance" I'd covered.

I'll probably run tomorrow through Wednesday and rest the two days prior to the race. I've read about the benefits of moderation in terms of weekly distance and the frequency of workouts, so I have no problem with that taper plan. I'm running well but I haven't raced in three months, so I'm not really sure how competitive I'll be. I'm not expecting to beat last year's PR, but I do have a target that I hope to beat. In reality, it's just nice to be back in the game.

Preparing to run the Snowflake

Even though I've been away from the office since Thursday, this has probably been the busiest week I've had this year. I'm not complaining, but my plans to run today needed to be postponed. I was planning to go into the office tomorrow, but that's also going to have to wait a day.

I may head to Bethpage on Tuesday morning to enjoy the peaceful experience of running without the weekend crowds. I am definitely in the mood to take on some hills and push the pace. Even though the Snowflake Race will happen on the pancake-flat streets on Long Beach, I've found hill training to be a great way to improve my speed.

My friend Steve, who has run this race with me the last two years, won't be able to join me this year. He has two reasons, one good and one bad: paternity leave (good), knee injury (bad). I'm anticipating a very cold morning on race day and a very big crowd at the starting line. I have done pretty well at this race and, last year, I achieved a 4 mile PR. I don't know about this year, but I plan to be competitive. I may be busy, but not too busy to get out and start training tomorrow. 

10K training run on the old Bethpage route

I'm going to stick with the SPIbelt

Yesterday's run (treadmill): 35 minutes
Today's run (Bethpage State Park): 6.2 miles

It's been a busy weekend but I did get in a few runs. Yesterday morning I had to get blood drawn as part of my annual checkup, so I elected to do a moderate length run on the treadmill. I've learned from past experience that losing blood, even small amounts like this, can effect your stamina. I didn't suffer fatigue at any point in the run but I capped my time at 35 minutes. I needed to reserve some energy for the day ahead.
 
The Emerging Runner family headed into the city to see my dad, along with my aunt and uncle who are visiting from France. Later, we were excited to meet up for dinner with Adventure Girl, who was in town this weekend for a friend's wedding. They are all great people and we had a great time with everyone. I was glad that I didn't push myself too hard in the morning, because I was exhausted by the time we arrived back home.

I headed over to Bethpage State Park this morning to get in some extra miles and to take on a few challenging hills. I love the new trail extension to the north but I had not run it in the southern direction in a long time. I headed down the bike trail feeling energized by the crisp fall air, but I was regretting my decision to take the RooSport to carry my phone instead of my SPIbelt.

The RooSport hangs over the top of your running shorts and stays secure with magnets that connect the inside and outside flaps. I had some issues the last time I ran with it, but I thought it was related to the shorts I was wearing. I had on different shorts today but, from the start, I felt like the pouch was slipping. I feared that it might disconnect and fall off, so I took it off and ran with it in my hand.

Other than that, my run went very well. I covered the first three miles barely breaking a sweat. My heart rate was only 84% of max despite the hilly route. On my way back I boosted my glycogen with half a GU Roctane that I had diluted 4:1 with water in my gel flask. The helped take the edge of the first of two challenging hills that need to be managed on the way back.

There were less runners and running groups today than I expected to see. Friends TC and FS, who are running the ING NYC marathon in a couple of weeks, are doing their 10+ mile workouts this weekend.. I thought I'd see more marathoners doing the same but it was mostly cyclists, including a woman who was riding a tall unicycle.

After last week's 14 mile total (due to running the 5K race and two less training workouts), I wanted to get back up to 20 miles this week. I think I might have made it but I'll have to check Daily Mile. I have a month to train for my next race, the Long Beach 10K Turkey trot. Today's 10K base run was a great start to that training.

October made me a runner

Burning up the treadmill four years ago

October has been a significant month for me in my history as a runner. Modern history I should say, because my running experience in the early '90's (and before that) is hazy and undocumented. But in August of 2008, I took my first running steps during my walking workouts. I steadily increased the ratio of time I spent running during my walks, all through September, and then into early October.

The reason I know the details of my early progress is because I'd used a Nike+ wristband and chip and I'm still able to look back at my workouts and see the histograms that show my pace and distance. It's interesting to see the first run/walks, where I traveled at about 15:00 min/mile, with short sections dropping into the 10:00 range.

A scan of the log shows that I averaged 9:34 per mile on October 21, 2008, making that my first full run over a mile with no walking. One year later I ran on a relay team at the Cape Cod Marathon where I achieved a then-personal record distance of 8.75 miles (over two relay legs). Two years after that, I took my big spill on the driveway at the end of a morning run that scraped me up so badly that I still have scars a year later. You have to take the good with the bad.

I guess the longer your running history, the more you'll have to look back on every month. Still, I'll always look at October as a most important month, because that's when I truly became a runner.

Attacking the hills at Bethpage

View of the recently re-opened bike trail head

Today's run (Bethpage State Park): 5.3 miles

I was up very early with hopes of getting to Bethpage before 7:00 AM. I couldn't get my act together and ended up stalling until almost 8:00. Although I felt okay, I was experiencing some of the symptoms that caused me to cut my run short yesterday. I debated whether to stick around and run closer to home, rather than heading to the park.

This is the last weekend I have to train for the upcoming 5K and I knew that I'd be better off running at Bethpage because it provided the best resource for hill training. When I arrived I saw a crowd of people setting up for the "Lean on Me" 5K Walk and Talk that benefits the Breast Cancer Network. It looked like it was going to be a fun event.

Walking and Talking today at Bethpage

My plan was to run the longest hill of the bike trail a couple of times. The hill goes on a bit, one trip up and down equals a mile. After I reached the top for the second time, I headed north and ran the upper trail to Haypath Road and back. Like the rest of the bike trail, the upper section is rolling and it has a few hills. One hill is fairly steep, but its relatively short length makes it manageable.

Once I got by those hills it was easy running and I reached the end having covered 5.3 miles. When I got back to the trail head I saw that the crowds had grown at the Walk and Talk event and the music was booming. I hoped the rain that was predicted to move in would hold off and I'm guessing that it did.

Despite feeling a little off, I had a decent run and the hill practice will hopefully pay off next Saturday. I'm not sure what type of workout I should do tomorrow. That will be determined by the weather and the way I feel. I probably should do some speed work before I taper off, but I don't want to push hard if I really need the rest.