Fast times on the asphalt track

Cadence drops throughout the run 

Today's run (intervals): 1.6 miles - 6 x 420m

I was extremely unmotivated this morning and decided that this whole running thing has finally played out. I've decided to quit and take up golf instead. April Fools! Fear not, I have no plans to stop, but if racing as we know it turns into this, I will reconsider it. Running through tree pollen is tough, but it's something we deal with. Running through clouds of rainbow colored corn starch is another thing altogether.

Happily, there was no rainbow dust in sight this morning when I went outside for my Tuesday speed session. Due to the weather, I have been doing repeats on the treadmill. Today's weather was so perfect I wanted to go outside. I'd picked out a stretch of somewhat straight road and adopted it as my track. Due to a lack of USATF measurement resources, I had to rely on Gmaps to define my start and finish points. This lack of precision resulted in a little extra distance per run, but really, what's a tenth of mile across six repeats?

My "track" has one property that is different from our local high school track: elevation change. It's not a big height difference overall, but I calculated the second half to be a 3.8% grade. Not exactly what one wants at the end of an all-out run. That's why tracks are supposed to be flat. On the other hand, the grade worked in my favor when going in the other direction.

I didn't know what to expect in terms of the speed I would maintain on these intervals. Hal Higdon instructs you to run at 5K or 10K pace for this series, but I ended up running a little faster, averaging 7:56 for the set. I found that sustaining a fast pace felt easier as I moved through the repeats, although a look at the numbers showed that I slowed down a little on the last two. Cadence was highest in the first third of each repeat.

Tomorrow I'm scheduled for my 5.x miles that I will do easy. I'm pleased with today's faster workout and I'm growing optimistic that the combination of performance running and base runs will prepare me well for Brooklyn.

Daft repeats: longer faster better stronger

Today's workout (treadmill repeats): 2 miles 
6 x 400m plus .5 mile warm/cool

Week 3 of half marathon training started better than week 2 finished off. After my second consecutive Sunday long run fail (only in the sense of performance, personally I had a great time) the evidence is pointing to cold induced breathing issues. Every run that I've done, either at temperatures above 40° or indoors, since my Brooklyn half training kickoff, has resulted in a decent performance. The two times I ran in high 20's/low 30's weather, I struggled mightily. Cold weather, J'accuse!

Or it could be the hills. Either way, the fact that I'm running decently more often than not is keeping me hopeful. Spring is here so chances are that one of these upcoming Sundays will provide better weather. That may help me turn the corner on my weekend base runs.

Today was speed day. It was 22° outside this morning, so I opted to do my workout indoors. Hal Higdon's program prescribed a 3.5 mile run, but I decided that I know a little more about this stuff than he does. But seriously, I've modified the Higdon training program to start my week with speed on Tuesdays and a base run on Wednesdays. Hal puts speed work into the Wednesday slot and allocates only Sundays to long runs. I felt I needed a little more base than that, an opinion echoed by some knowledgeable runners.

Hal's speed workout is 6 x 400's at 5K pace (8:24) and that's what I did this morning. In between repeats, I did 240 meter recovery jogs (.15 miles), which I may cut down to .12 miles next time. I also did a half mile warm up and cool down. I normally would have run another mile at my usual training pace to make a full three, but today I decided that 1.5 miles of speed stood on its own.

Tomorrow should be a 4.8 mile base/recovery run. The "feels like" temperature is predicted to be 19° when I plan to go out in the morning, so I'll have to decide whether to endure this cold and its effects, or suffer the tedium of a longish treadmill run. We're getting snow overnight, so that may help the decision.

Runsketeer training run at Bethpage

Why am I smiling? I'm done.

Photo and artistic effect by The Petite Pacer 

Today's run (Bethpage State Page): 6 miles

Today's run with my Runsketeer buddies had its ups and downs, and I'm not referring to the hills at Bethpage. The ups came from spending time with two of my favorite people, SIOR and TPP, who joined me on the trail this morning. The downs related to the struggles I had trying to cover 6 six miles today. It was the second Sunday in a row where I went out for a long run with great hopes, but ended up with a disappointing performance.

SIOR was running 17 miles today. She covered all but six of them before rendezvousing with me and TPP on the north trail at Bethpage. TPP and I took off in SIOR's direction and we both noted that the pace felt challenging. This was not a good sign for me because we were running slower than our normal training paces and I feared that today would be a repeat of last Sunday's performance. It turns out that it was.

We met SIOR at the one mile marker on the north trail. She had done an out and back from the parking lot and we all decided to head north from there. Both of my group-mates are speedy, although TPP has been hurting a bit and is still dealing with respiratory issues. She took a few moments for recovery (as did I) throughout the run, but when she was in "running mode" she did an impressive job of keeping up with our speediest run-mate.

Much of today's run was spent watching my buddies progress from a distance. At first my gap was about 30 feet as they tried to keep me included. They both slowed or stopped so I could catch up and participate in the conversation. Unfortunately, I struggled to both talk and run and eventually encouraged them to open up and run their faster pace. They are great people and they followed a "No Runsketeer left behind" policy, so periodically I would spot them waiting for me to catch up.

I am still puzzled by my difficulties today. They started early and remained, just like last week. I had really good runs on Wednesday, Thursday and Saturday where I maintained my targeted training paces. Wednesday's run was 4.4 miles where I ran strong from start to finish. Yesterday I did a hard three miles near targeted half marathon race pace. The only variable that could explain it is the weather. Last Sunday's run and today's were both around 30° with wind-chill and I wonder if I've developed a cold induced breathing issue.

I managed to cover six miles per my training schedule, although there were a few stops for rest and to let traffic pass on Old Country, Old Bethpage and Haypath roads. It was a strange experience to be running with such a high perceived effort, yet not being able to keep up with the continually shrinking silhouettes of my friends as they disappeared over the many hills along our route.

Reunited in the parking lot

Photo by The Petite Pacer 

SIOR made it to our end point first, followed by TPP who threw in surges at the end. I rolled in a couple of minutes behind her. One of the "ups" from today was when the three of us took a few minutes to chat at the three mile point of our run. We didn't get a chance to go for our traditional Starbucks after-run coffee, so this was a nice substitute. We also took a few minutes once we finished, but the combination of cold, sweat and scheduled obligations caused us to cut that short.

I'm trying to look on the bright side. I got to spend time with my buddies and ran my planned distance. After last Sunday's tough run, I did far better throughout the week. Hopefully that will repeat this week. Eventually I'll get past whatever it is that's making my Sunday runs so difficult. It may be something as simple as warmer weather. It's spring, so theoretically that should come soon.

Winter winds down and training ramps up

Safety first!

Today's run (street): 4.4 miles

Spring starts tomorrow at 12:57 PM but you wouldn't know it by this morning's chilly temperatures. I was excited to get back to my neighborhood roads after so many (many, many) treadmill workouts. It's inevitable that I'll be writing a lament about the tedium of neighborhood running in the coming months. Right now, access to the roads is a treat.

I was anxious to get out today to validate that my recent sub-par running experiences were an aberration and not a trend. I was going on two day's rest and despite the cold, I felt like I was in for a good run. I wore my day-glo orange long sleeve jersey over a short sleeved bamboo-cotton running shirt. I was tempted to add another layer (the temperature was 33°) but I didn't want to feel restricted. I wore my medium weight track pants, a warm hat and gloves.

One new piece of gear I brought along was a clip-on blinking red LED light that I attached to the back of my shirt at the top. This light was a giveaway from one of my 2013 races and I came across it while looking for my HRM in my gear drawer. It's a really nice gadget and it barely weighs an ounce. Even with a bright orange shirt, I felt it couldn't hurt to also have a flashing beacon to get the attention of drivers.

Ten seconds into my run I knew I was in for a better experience than Sunday's. My target distance was 4.2 miles and I ended up covering almost 4.5 today. I didn't worry about my speed at all. Before I can sustain race pace over 13 miles, I need to increase endurance. My plan is to run increasingly longer Sunday runs and then run 80% of that distance on Wednesdays. Next Sunday I'll move up to six miles and the following Wednesday, my target moves up to 4.8. And so on, until the penultimate training week, where I'll run eleven miles on Sunday and 8.8 the next Wednesday.

Getting through today's distance was not a big challenge and I enjoyed the parts when the cold wind wasn't hitting head on and freezing my face. My pace wasn't impressive, but I ran a minute a mile faster than on Sunday. I'm buying into the idea that more miles and weekly speed work will eventually lead to better performances.

Tomorrow I'll get a break and will only need to cover three miles plus "strength" whatever that means. I know what it means. I just have to do it.

Why bad runs don't really matter

The long unwinding road

Both Saturday's relay and Sunday's half marathon "Week 1" training runs were disappointing for me. The good news is that it really doesn't matter. Running is one of those things in life that can lift your spirits or temporarily disappoint you. But as long as you aren't suffering a running injury as a result, there's really no excuse for feeling badly about one or two bad experiences.

That's why I'm looking forward to getting out tomorrow. I rested yesterday and took an additional recovery day today. It's still winter-y cold outside, but at least it's sunny and the snow is gone. The Hal Higdon Intermediate Half plan says that I should run 3 miles, plus strength training, on Wednesday. However, the Emerging Runner Training Plan™ says that I should run 80% of the prior weekend's longest run on Wednesdays. So that's what I'm doing. I do appreciate Hal's attempt to add more diversity to the training schedule, so I may add in a small amount weight or core training.

I gave myself a break on speed training today, but I will resume that next Tuesday. Without weekday access to the track, I can either do treadmill intervals inside, or run 400's along a road that's adjacent to my street. That long road has a slight grade when running south to north, but SIOR says that shouldn't matter. I'll need to figure out how to manage recovery periods if I choose the street route because I'll need to start each repeat at either the beginning or end of the road.

Wisdom of the (running) crowd

 

Today's run (treadmill): 3.2 miles

I found it interesting that three knowledgeable runners (Carla, Karl and SIOR) have all recommended a mid-week long run as part of a half marathon training plan. I generally run shorter distances in the middle of the week. My excuse has always been a lack of time. But people with schedules busier than mine seem to get them done. Here are strategies I heard this week that I will take to heart for my training:

Carla: "The key for me ended up being doing at least two 15+ milers. and another 7-10 mile run during the week. Plus a 10k, 15k, and 10 mile race, and progression runs in the buildup phase. In effect, more overall mileage. And more of it at hoped-for race pace."

Karl: "It's all about stamina and endurance. Speed is largely innate. The stamina (tempo and progression runs) and endurance (long and easy runs) workouts allow us to maintain whatever speed that we have over longer period of times."

SIOR: "I would run speed work on Tuesdays, a longish run on Wednesday (7-9 miles), and easy runs on Thursdays and Saturdays. Then when all is said and done, I would sign up for a fall marathon." [Editor's note: SIOR is a troublemaker who knows I will never run a full marathon.]

Right now, seven mile mid-week runs are a challenge, but once I get my base closer to double digits it could be managed. If I'm going to go out for four miles anyway, what's another half hour? And now that I'm comfortable with using the treadmill for speed work, I won't have the excuse that I can't run weekday intervals due to restricted access to the track.

Today's workout was another treadmill run. I had planned to run slowly in deference to yesterday's speed session, but I ended up doing a more intense workout. I hope that by resting on Friday, I'll be properly recovered for Saturday's relay. I keep telling myself that it's only a two mile leg, but going all-out for 17 minutes (if I'm lucky) will seem like a very long time.

Again with the treadmill repeats

Today's run (treadmill repeats): 3.1 miles 
(10 x 340m plus 1 mile warm up/cool down)

I'd like to thank everyone who commented on my post and sent me emails regarding my Brooklyn Half training plan. The consensus is that my weekly long run schedule is fairly solid and that speed work should integrated throughout the training cycle. I'm anxious to return to Bethpage and excited to be able to begin this training, with the additional six miles of paved bike trail that was completed last year. If I chose to do it, I could run an entire half marathon distance from my house to the Massapequa Preserve along that trail. But somebody would need to pick me up at the end! 13 miles is one thing, 26 is quite another.

My friends FS and SIOR both pointed out the Hal Higdon training plan and I found it realistic, accessible and very close to mine in terms of weekly long run schedule. Following months of complacency, I'm getting excited about performance again. After Monday's speed session, I opted for a moderate elliptical session on Tuesday. This morning it was back to speed work with another set of repeats done with a little less intensity.

Like Monday, I started with a half mile warm up before moving to intervals. I wanted to go a little longer on each repeat, so I bumped up the distance from 220 to 340 meters and set the speed about 3% lower than on Monday. I also capped  it at 10 repeats, although it worked out to almost the same distance. I finished again with a half mile cool down.

I'm not sure if this late stage speed work is going to translate into better performance on Saturday, but I hoping for the best. It's supposed to be very cold on Thursday, so I may have to do tomorrow's run on the treadmill. I would prefer to run outdoors, ideally on trail, so I could simulate trail race conditions.

Treadmill 220's, surprisingly fun

220m intervals with 70 second recovery jog

Today's run (treadmill intervals): 3.2 miles (16 x 220m, 1 mile warm up/cool down)

Although you wouldn't know it by looking at my Garmin data from my weekend runs, I have turned my attention back to performance running. It isn't without irony that, despite my now-clear neighborhood streets, I did my first speed workout this year on the treadmill. My preference would have been to do this on the track, but I was reluctant to risk being hauled off by security for trespassing at the high school.

I normally take Mondays as my rest days but I really needed to focus on my readiness. If the weather holds, I'll be racing on Saturday with the Runsketeers. I didn't intend to take as much time as I ended up needing for today's workout, but it was good that I did. My plan was to start with a half mile warm up at about 9:30 a mile and then run 12 x 100m before finishing with a mile cool down. I discovered that running intervals on a treadmill can be difficult. This is because the machine lacks the hard start/stop precision of the track. I had to account for the time it took the treadmill to get up to full speed each time.

As a result, I decided to run 220m repeats instead of 100's. I'm not confident of the accuracy of the speed displayed on the treadmill, but I set it 25% faster than what I usually run on the machine. I averaged 67 seconds for the 220's (about an 8:10 pace), after factoring in the starting lag.

I started and ended today's session with regular running. I bumped up the speed on the cool down to take advantage of the fact that 6.5 MPH feels a lot easier after pushing close to 8 MPH for twenty minutes. I was surprised that my heart rate averaged only 81% of max overall. Perhaps 67 seconds isn't enough time to go up from 64% (heart rate during recovery cycle). I'm sure that if I was doing 400's at that pace I'd be in the red zone by the end of each repeat.

Treadmill intervals were more fun than I expected and I hope this was a good way of reactivating my speed. I may do another speed session on Wednesday before my mini taper. Running fast is fun. I wish I could remember that more often.

Return to a real workout

 

Today's run (treadmill): 3.25 miles

Colds are funny. No matter their severity, they all seem to follow the adage, "Three days coming, three days staying, three days leaving." An impending cold signals the start of an uncomfortable week. Bad decisions are often made (certainly by me) about how far to push myself after the first symptoms appear. I questioned whether it was wise to run 6.7 miles two Sundays ago, when it was clear that I had started a cold. But if that had an effect on this cold's duration, it was a minor one.

Aside from some residual stuffiness, this cold has pretty much passed. I decided to ease back into running during the "leaving" phase, with extremely easy workouts. This morning I felt close to full strength and went back to my usual routine. I'll admit that I picked a program on the lower end of the performance scale, but it was a legitimate workout.

My concern was that resuming a normal training pace too soon would tire me out before I could finish the run. I had a moment around the first quarter mile when I wondered whether I'd taken on too much too soon. Happily, that didn't last long. Although the rest of the run felt long, it was completely manageable. My other concession to recovery was forgoing the anaerobic sprint I usually do for the last quarter or eighth of a mile.

The best thing about today's workout was knowing that I'm ready to train again. I'll take it fairly easy over the next week and hopefully see some pavement this weekend.

Serf of the road

 

Today's run (street): 3.7 miles

It was only 39 degrees outside, but it felt very much like winter this morning. I wore layers top and bottom and was comfortable throughout my entire run. Had I pushed harder, I probably would have overheated. I was in the city yesterday and covered 7 miles on foot. After that, and two moderately tough runs over the weekend, I kept my heart rate around 80% of max for today's workout.

I've been reading a newly published book called, Kings of the Road, that's about how Frank Shorter, Bill Rodgers and Alberto Salazar helped popularize competitive running in the '70's. As I ran today, I thought about my paces versus theirs. In one part, one of these runners described his 4:45 pace at the Falmouth Road Race as "easy."

I know that elite runners train so that they are able to sustain high speed over long distances. But how do they mentally prepare themselves to run sub-5:00 paces over 26.2 miles? For that matter, how do 7:00 or even 8:00 milers do it? Is running a half marathon in an hour as hard for Galen Rupp as breaking 2 hours is for me at the same distance? If these elites put everything they have into their races, why do they look so fresh after they cross the finish line?

Most people who compete in races push way past their comfort zone. All things being equal, a 4:45 pace, while impressive, is relative to the runner. I have my race targets and it's always great when I meet or exceed them. There are many factors that determine performance on a given run, but lack of trying is rarely one of them.

Hill running on marathon day

The long and windy road

Today's run (street): 4.6 miles

It's marathon day in NYC and I got an early start on the coverage. I didn't take advantage of the extra hour's sleep from DST, because I wanted to have my run completed prior to the marathon pre-show. There wasn't much drama in today's race, but it was still fun to watch. I was hoping all my friends who ran it had great experiences. I thought about them on my run knowing I'd be covering far less distance today.

Today was my last chance to do a good training run prior to next weekend's 10K. I decided to head over to the Greenbelt bike trail and run south so I could take on the long hill along Sunnyside Boulevard. It was cold enough for long pants and sleeves, but I remained comfortable (except when the wind hit me head-on). The Sunnyside hill is just long enough to wear you down because it gets increasingly steeper along the last half mile. I just kept reminding myself that I'd get to run it downhill on the way back.

Today's run went well and I'm hoping I've built my fitness to handle a brisk pace over 6.2 miles next Sunday. This will be a busy week with early mornings into the city. I'm not sure how I'll handle my taper, but I'll figure it out. Although the Hope for Warriors course is fairly flat, this weekend's hill heavy training should yield some conditioning benefit.

Running views and visualizations

Sure looked like fall along the trail

Today's run (Bethpage): 6.25 miles

The Hope for Warriors 10K next weekend prompted me to head to Bethpage this morning for a base run. I've plateaued on distance since Cow Harbor, having completed only a handful of 5+ mile runs since that race. After a week of rainy and windy conditions, today's clear, dry 57° weather made a run at Bethpage very appealing.

More scenes from today's run

When I arrived I saw that the right side of the lot was fairly full. There were lots of people with bikes and I wondered if there was a cycling event planned. I don't think it was anything that formal, although there were a lot more bikers on the trail than I usually see. Considering the density of cyclists on the path, along with many runners and a good number of walkers, I encountered few reckless riders.

With my headache and sinus pressure gone, I felt good energy along the trail and felt less intimidated than usual by the big hills. That isn't to say that I particularly enjoyed them. My plan was run 5K south and turn around at the 3.1 mile mark. It works for me to break a middle or long distance run into parts. For that same reason, I like to familiarize myself with a race course before running it for the first time. It's always valuable to understand the challenges of the course before you face them for real.

New Garmin Connect cadence graph

I didn't dog the pace but I wasn't looking to simulate race conditions either. The purpose of this run was to get a 10K distance under my belt close to the real thing a week from Sunday. When I downloaded my Garmin after the run, I saw that they'd changed the data visualization on Connect and added a new metric: average stride length. Better still, the site has a pop-up that helps explain SPM and running dynamics. I felt good when I read this in the explanation: "The data values in the green, blue, or purple zones are typical for more experienced or faster runners."

Good context on cadence

Ideally, I'll see less green and more blue data points as I work to increase my cadence. Races tend to bring out our best performances (my recent history excepted) so I might even get myself into purple territory next week.

Making my last taper count

A serious threat to pant-kind

Today's run (street): 3.1 miles

As much as I love running, business needs to come first. For that reason, I was unable to get in my workout yesterday. I was in the city all day for meetings so the opportunity for a run didn't surface. I'm temporarily boycotting my Fitbit because the holding clip has deteriorated to the point where I fear it will rip my pants when I wear it. Without it, I don't know how much distance I covered yesterday on foot, but I'm estimating it was between 4 and 5 miles.

Today I had no excuses. Without a commute into the city, I had enough time for one final run before Saturday's 5K. Although I've heard that I need to do weekly speed work in order to avoid embarrassing myself on race day, I think I've prepared well for the race. I decided that a good hard run over three miles would be a nice way to end my taper.

I took off at a brisk pace and tried to maintain that turnover throughout the entire run. The difference between this type of workout and a race centers on two factors: the influence of other runners and the psychology of competing in a timed event. Without those two things, my expectation was to see a very good, but not spectacular performance today.

That's exactly how it came out. I'd kept my heart rate around 85% max and covered the distance in a little over 28 minutes. For me, that was exactly on the mark. I could have pushed harder and dropped my pace into the 8:00 range, but I didn't see any reason to do that. 9:06 was a decent average under the circumstances. I'm making no predictions for Saturday. A lot of it will come down to how I feel on race day morning.

Bethpage run and a surprise in the mail

A Garmin it's not

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

I'm in the middle of some high intensity work related to a new project that's requiring some focus over the weekend. This morning I felt a lot of pressure to get out early for a run. I needed to be back in time to accomplish some work before shifting gears toward my son's birthday activities. I couldn't face another run in the neighborhood, so I went to Bethpage to run the hills.

With my 5K coming up in a week, I have a limited amount of time to train and I wanted to make today's count. The weather could not have been better and that helped motivate me up the hill toward the start of the newest part of the bike trail. I felt very good and moved along at a decent clip. At least I thought it was decent until the first of many runners passed me like I was standing still. There was an extraordinary number of capable runners this morning and I wondered if there was a low key race going on.

Overall, I was pleased with my performance on the hills and I'd maintained a pretty good pace. Some of that came from running the last mile at my most sustainable speed. I would have liked to cover a another mile today, but I was concerned about staying on schedule.

Yesterday I was surprised to receive the above watch in the mail, the result of my renewing my subscription to Running Times. I didn't even realize it was coming. I spent many years with a large magazine publisher and I know subscription premiums can be a little chintzy, but his one brings it to new level. The watch seems to work fine (no running features besides a stopwatch) but the metallic bezel is actually "chromed" plastic. But I'm not complaining. After all, I can always use another stopwatch.

Tracking well through the taper

4 minutes of intensity

Today's run (track): 3.1 miles - 1 mile warm up, 10 x 100m, 1.6 mile recovery

Nothing like 52° weather to make speed work bearable. I went to the track early this morning to run intervals, but I didn't decide on my workout until I got there. I started with a mile warm up and followed that with 10 x 100 meter repeats. I finished with six more laps around the track, three at an easy pace and the last three somewhat faster.

Overall, it was a decent workout and I managed to run my 100 meter splits at 6:50 while maintaining a heart rate around 80% of max. I would have like to see better paces after the repeats, since my leg muscles were theoretically "activated." Residual fatigue was the likely culprit and my overall pace for the full distance run was 8:58.

Tomorrow will be a busy day in the city for me and I'll forgo my workout, since Mondays are my usual rest day. I'm thinking I'll do one more easy base run, one more short fast run and then rest. I had two good race-oriented workouts this weekend with acceptable results. I'm not sure I pushed as hard as I could either day but I didn't want to invite injury less than a week before the race.

Arduous base run and an impromptu trail

Lots of cross country teams on the trails today

Today's run (Bethpage bike and dirt trail): 6.1 miles

Tough run today. I went to Bethpage to get in some base miles and a little hill practice. From the start, my level of energy told me that this would not be a high performance workout. My intention was to make it a variable run: 20 minute easy warm up, 20 minute tempo and a moderate pace to the finish. I even intended to cap the workout with a couple of runs up the big long hill at the start of the older bike trail.

As I made my way the hill leading to the north trail entrance, I knew that I'd be hard pressed to manage the planned tempo. I felt a buildup of excessive lactic acid in my leg muscles and I tried to keep my form correct. I hoped that my stride would soon loosen up. I picked up the pace around mile one, where the biggest downhill section starts. I gained more speed down the hill, but soon encountered the two uphill sections that come just before the Haypath crossing.

Once I got to the other side, I made a split second decision to duck into the woods and follow the dirt trail that runs roughly parallel to the paved trail. I was surprised by the number of twists I encountered along this path. It went on much longer than I thought it might. As expected, the dirt trail terminated at a point on the paved trail, just south of Old Bethpage Rd.

The run in the shady woods invigorated me, and I ran the last of my northern route to Old Country Road. Instead of crossing the street to continue on the bike trail, I followed the sidewalk south about a few tenths of a mile before turning back toward the paved path. At the point, my energy level had dropped to the point where I struggled to maintain speed. I decided to dismiss the plan to do hill repeats at the end of the run.

Th only thing left to deal with were the three consecutive hills that come a mile north of the trail head. I locked in a cadence, shortened my steps and made it through the first one, and was grateful for the slight slope that comes before the next one came. I knew I was less than a mile from the end, so I maintained the fastest pace I could until I reached the end.

Today's run felt far harder than the 7+ miler I did last weekend or yesterday's hilly workout. I suspect that today's difficulty was driven by too much hard effort over the prior six days. I've decided to take both Monday and Tuesday off from running this week to help me recover a little. I'll probably do another core session on one of those days and/or some upper body exercises. I didn't love the run today, but I'm glad I put in the miles.

Can you really improve your running speed?

Looping the loop

Today's run (Business Park): 4.8 miles

I'm beginning to wonder how much one can actually do to optimize running speed. When I first started running, I was averaging 12 minute miles over the first full month. Two months later, I was breaking 10 minutes a mile. When I completed my first full year, I was averaging 9:15 per mile, with occasional dips below 9:00 on shorter distance runs.

Four years later, despite holding consistently to a six day running schedule, I'm still averaging about those same paces. The good news is that I've managed to keep my performance at the same level. The bad news is that it now takes a lot more effort to do that. My goal has always been to average below 9:00 a mile and I'm wondering if I'll ever get there.

As I focus on speed, I'm realizing how difficult it will be to get to my targeted pace. After taking a break from performance to run the trails on Friday, I headed over to the local business park to run the big loop. This route provides a lot of elevation gain and loss (+/- 1,040 feet), which I thought would be helpful training for Cow Harbor.

The temperature was 59 degrees when I went out 8:00 AM, and that provided great conditions for taking on the hills. I did two laps around the park before ducking into an adjacent neighborhood for another mile. With the great weather, I was surprised to see only two other runners out this morning. One woman was circling the park counter-clockwise while I ran it the other way. She was running with traffic and we passed closely. I wonder if these people ever connect the reason why I run on the left with safety. I'm guessing they don't.

I made it back home in time to make an early obligation. When I mapped my run, I saw that I'd averaged 9:27 a mile. Despite my focus on speed, my performance is still lagging on longer runs. Tomorrow, I'm planning on doing a fairly long tempo run, followed by hill repeats. Only one more weekend after this to train for Cow Harbor before I taper. I'm doing the best I can to prepare, but there may not be much more performance to gain.

Stalling for time, but getting it done

Well, I did finally run

Today's run (Street): 3.9 miles

For no good reason, I just couldn't get myself out the door this morning. I finally did, but it wasn't for lack of stalling. I knew that every minute I spent taking care of "just one more thing", it was getting warmer outside. And yet I found plenty of distractions that kept me from starting my run before 11:00 AM.

We had a family dinner last night and got home late, but I still got up fairly early. I got right into  work and that delayed me from focusing on my run plan. I usually prepare my gear while my wife starts her treadmill run, and get back home around the time she's finishing up. I knew I was in trouble when I heard the treadmill's motor slowing for her cool-down while I wasted more time. At that point, I considered taking a rest day. Somehow, I found myself getting dressed for a run.

The run itself felt a little harder than yesterday's, and I wondered if I should allow myself a break with an easy recovery run. But I was committed to the tougher option, so I focused once again on my speed. I mixed up my route and even added an extra half mile to get closer to four miles today. In the end, I did good, but not great. The important thing is that I ended up getting the run in. Even if it took a while to get out the door.

Just me and the road, and the cars, and the buses

My worst nightmare

Today's run (street): 3.3 miles

After three consecutive indoor workouts, I was finally able to get outside today, and it was beautiful. The sun was bright and the temperature was cool. While I waited for the Garmin to acquire a signal, I noticed a breeze that actually made it feel cold in the shade. I knew once I got started that any feelings of being cold would disappear, but it was nice to start out that way. 

Due to a scheduled call, I had to get my run done in a certain amount of time. I could have gone out earlier, but we live close to both an elementary and a middle school and I didn't wish to compete with all the buses. By the time I hit the streets, a few buses still remained, but car traffic had picked up. You can't win, but you can run on the sidewalk. I ended up yelling at a guy who rolled through a stop sign as I approached the intersection. To his credit, he sheepishly said "sorry."

I continued my focus on speed and moved along, although I was having some trouble with my form. I didn't feel like I was getting good turnover and I was concerned that I'd end up with a disappointing time. Still, I knew that I was making the effort. Most of the time, that will yield a satisfying result.

I ended up averaging 9:05, which surprised me in a good way, because I expected I'd be about 15 seconds slower per mile. My speed described a bell shaped curve, with the first and last half miles being the fastest. So far my training strategy is working, but I still haven't put fast and long into the same run.

I really should have thought this through

Accidental self portrait after the run

I was trying to get this shot of the new gates and info kiosk

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

As I made my way along today's Bethpage route, I came up with various titles for this post. At the two mile mark, it was something like, "Great base run at Bethpage." By the time I'd reached my turnaround point it was, "Oh the humidity!" By the time I reached the end of my run, the above title popped into my head.

Today was a base building run to help prepare me for Cow Harbor. With all the focus I've been putting on speed, I didn't want to neglect the fact that the Cow Harbor course is 6.2 miles and hilly. I thought that Bethpage's bike trail would be a great place to duplicate those properties. Cow Harbor's race day weather can be oppressively hot and humid, so today I hit the trifecta for simulating conditions.

I didn't plan a particular distance this morning, although I knew I'd run at least six miles. Once I arrived at the park, I decided to run a mile on the north trail before changing directions so I could do the bulk of my distance on the older, somewhat more challenging section. I had little trouble getting through this first part. It was cloudy and 73 degrees, so despite the 89% humidity, it didn't seem so bad.

My new-found speed allowed me to pass numerous runners. This was gratifying since I'm often passed by club runners who populate this trail on weekends. My pace for the first couple of miles was on par with what I've been running lately, and I felt encouraged. By the time I reached mile three, I started to feel the effort, especially as I took on a couple of tough hills that come before the Plainview Road roundabout.

Despite growing evidence that my smooth base run was about to get rougher, I tried to maintain a brisk pace. The trail between miles three and four trends slightly down, so I was able to keep going without a lot of extra effort. By the time I passed four miles, it became clear that my glycogen level was depleted. I did my best to hold on while my body figured out what to do next.

Between a lack of fuel and the overwhelming humidity, I was hurting. Why, after seeing the weather report showing close to 100% humidity today, did I forget to bring a water bottle? My pace had slowed 90 seconds per mile compared to the start, and I switched to a more mechanical stride in an effort to just keep going. I nearly bonked at mile six, but instead slowed my pace even more. I needed to prepare for the dreaded hills that make up most of the last mile leading to the trail head.

By the time I reached the biggest and longest hill, I was moving slowly. But I was moving. I even passed a woman on a bike who was struggling to get up the hill. About 4/5ths of the way to the top, my energy began to return and I stepped up my pace enough to put me back into target range. I was thrilled to run the final section of trail leading to the lot. Stopping never felt so good.

It was a very tough workout and I'm still feeling the effects seven hours later (although I did participate this afternoon in our family's annual obstacle race - a summer tradition). I don't know if today's experience was due to fitness gaps or if it was more about the weather. Last weekend I ran almost the same distance and performed much better, so it probably had more to do with conditions than conditioning. Next time I'll think about going out so fast on a base run and I'll definitely remember to bring along water.