This weekend’s race is serving two purposes: first, it’s a dress rehearsal for next month’s Bay State Marathon, my ‘A’ race this season. Second, it’s breaking up the 20 week training plan I’ve been on for the marathon. (If I use this plan again, I’d cut it down to 16 weeks. ) Racing is fun and a good litmus test to see if all the miles, tempos and intervals are paying off.
The race is actually at Suffolk Downs a horse race track in East Boston, not the city proper. The half marathon course is an out and back course that hugs the coast up toward the north shore. Should be nice views, but could be cold and windy off the water if the weather is bad. Right now it looks good (after a surprise burst of heat this week).
As a dress rehearsal for the marathon, I want to test out my pre-race routine (this race starts at 7:30, the marathon at 8), and nutrition.
During the race, I want to focus on early pacing. I need to keep the pace under control. My two previous halves, I’ve been too aggressive early and really paid for it in the last third. I know I will pay double if I burn too many matches early in a marathon. I want to finish strong. After the halfway mark, if I feel good, I’ll let go and run by feel. If not, I’ll keep pacing and treat the day as a catered training day.
I also want to test out clothes and shoes. After running the past two years in more minimal shoes, I found my feet aching after long runs and recently switched to a, still neutral, but more padded shoes (New Balance 750v2). We are still getting used to each other. A little worried about a persistent hotspot on my right foot.
Finally, I want to practice my nutrition. I’ve been pretty consistent during my long runs with the gels, food, salt pills and blocks, and have not had any issues, but want to put them through a race environment. Along with the fuel and race belts.
1. Practice my race routines
2. Stay on pace early
3. Finish strong
4. Set a half PR
5. Smile/Have fun
1:37:22 – I actually set a half marathon PR last week during a 16 mile long run, lowering it almost two minutes, from 1:40:52 to 1:38:46, so I know the training is paying off. If I can find that flow again, I think I can drop it even further.
I’m looking out my window and fresh snow is falling on the existing three feet high snowbanks along the driveway and I’m questioning the sanity of starting my season in February while living in the Northeast. In past years, I’ve eased into the season with 5Ks in March, typically around St. Patty’s Day, and typically with a race that featured a pint at the end. This year, perhaps to keep me motivated to up the annual mileage or just to avoid using my paternity leave as a crutch to slack off, I chose the Old Fashioned Ten Miler in Foxboro tomorrow as my first race of the 2013 season. One part of me (the type A part) is looking at it as a challenge. Snow, wind, black ice, sub-zero temps? Bring it on. The other part of me is itching to scrap it and log a few miles on the treadmill in the basement next to the percolating warmth of the boiler room.
A Quick Recap of 2012
First, a quick look back. The further I get away from 2012, the more mellow I become about the results. After the last 5k in December, I felt pretty down on the season despite setting two PRs and finishing another half marathon. My big goal for the first part of 2012 was strength and speed work with the benchmark being breaking 20:00 for a 5k. Believe it or not, of the 6 5k’s I ran in 2012, I ran each between 20:00 and 20:12. If you’re feeling generous, you might give me that one. I hit 20:00 on the nose, but never dipped under it. A new PR, but not a gold star for my goal.
The second PR was in the Finish at the 50 10k at Gillette stadium on a pretty hot July 3rd. I finished 16th in my age group and posted a 42:39. Not too shabby, but I put a mental asterisk next to this one as the first kilometer or so is on a serious downhill, so a steep hill-aided PR.
The big goal for the second half of ’12 was completing my second half marathon and improving on my first time at Rock N Roll Providence (1:40:52). I did finish the race (the flat Smuttynose Rockfest in Hampton), but failed to top my Providence time as both IT bands tightened painfully around mile 10 (up to that point, I was very pleased with my nutrition and pacing) and the last three miles were finished at a hobbling limp. Net result? Two minutes slower than Providence (1:42:50). Errr.
Goal Setting for 2013
Time to put the 2013 goals in writing to ensure a little accountability.
The big goal for ’13 is my first triathlon. I chose a sprint one, USAT certified, but with a capped field that I hope will provide both a gentle introduction to the sport and a fun experience. This is local and in mid-July. Ramping up cycling and re-learning to swim should be interesting learning experiences.
Full marathon or Multiple half marathons
Haven’t completely made up my mind about this one. Given that we have a new baby and being cognizant of how much time it would take to train the way I’d like for a full marathon, it makes me leery of stepping up to the full this year. If I chose a full, I’d aim for one in mid-October. Maybe the Bay State. If I go multiple halves, the Ocean State Triple Crown series looks fun.
Continue focus on flexibility
I am not flexible. Never have been, but as I work to take on more endurance races and get older, I’m increasingly aware of how better flexibility can aid training, recovering and prevent nagging injuries (see the IT band issues above). Last year, I did yoga fairly regularly, I’d like to continue that and be better about consistent foam rolling on a weekly basis.
Stay on a plant-based diet
I plan to write about this more soon, but since December I’ve been eating a largely plant-based diet and really feeling the benefits in all aspects of my life: sleep, work, energy for playing with the kids, training. The plan is to keep this up for the rest of 2013.
That seems like a solid, challenging, yet achievable list.
The Half Marathon needs a better name. It sounds like a cop-out, doesn’t it? Oh, you couldn’t do a full marathon, huh? Opted for the halfsie? By the end of 13.1 miles this past Sunday, I was quite ready to take any abuse, any insult, just to be done. I staggered across the line, legs like dead wood, chest heaving, eyes zeroed in on that finish line with a zombie-like stare. Sounds like fun, right? Why would I possibly subject myself to this? Good question.
In the days leading up to the Providence Rock N Roll Half Marathon, I asked myself this question a lot and came up with two reasons. I blame my co-worker and Christopher McDougall’s Born to Run. The co-worker because he innocently handed me the book and McDougall for writing a very convincing and very entertaining book that certainly made distance running seem fun and romantic. Before I go further, let me say I’m not a barefoot acolyte. I do own a pair of minimalist trail shoes and I did make a conscious decision to change my stride this year to more of a mid-foot strike to ease the burden on my knees, but please don’t attack me with do’s or don’ts of barefoot running. My advice? If you’re running without pain (or little pain) there is probably little reason to change. If you find yourself bogged down with injuries or returning to running from a long layoff, you might give the arguments in the book some thought.
The second reason was more esoteric and tangential. I play basketball once a week with a group of like minded, competitive guys. We recently switched leagues from the open league to the over-35 one. Seems rather banal, and definitely a good decision given how the 20 year-olds were buzzing by us like we were playing in cement shoes, but I think it triggered some sort of urge to still prove I could compete. Even if I was only proving it to myself. Like I said, esoteric, but better than buying a Corvette or something, right?
I wasn’t starting from scratch. I was pretty fit and had a solid base of 15-20 miles a week of recreational running. Still, I knew I needed a plan for a half marathon. Sure, I could probably wing it and complete it, but being a type A personality, I had goals and ambitions of running it well. There arenumerousplans out there on the Internet for free. Pretty much a plan for every type of runner, I think. I choose Hal Higdon’s Intermediate plan for a couple reasons. First, it wasn’t overly complex. A lot of plans had days (or multiple days) dedicated to speed workouts or splits or intervals or tempo runs. Undoubtedly that would probably help, but I the more I searched the more I realized I wanted less of a plan and more of a road map on how to ramp up to sufficient miles without risking injury. Second, I have a full-time job, a toddler and lot of other demands on my time. Higdon’s plan was flexible. It allowed for me to slot in my weekly basketball game as cross-training and for flip-flopping training days when necessary.
With the training now in the rear view mirror, I can say Higdon’s plan was successful and the right one for me.
Let me also pass along a few tips on the physiology of long training runs. I did come to welcome these runs (proves how short term my memory is) each weekend, at least until mile 9 or so, and definitely came to recognize a certain pattern: Mile 0 – 3: This is a good pace. Nice and easy. I can do this all day. Mile 4 – 7: Damn! I am flying. Half marathon? Screw that, I’m going for the full monty. Mile 8 – 11: Where did these elves and their little knives come from? Why are they jabbing me in the knees, ankles and hips? Aw, gawd, it hurts! Mile 12 – 13: Mental boot camp. Your numb lower body is on autopilot. A death-march to the finish.
Two final things, having a time goal did help me. It gave me a tangible measuring stick to track my training progress. Second, I always thought the idea of a mantra was kind of silly, but in those last three or four miles when your mind is a blank slate of pain, they do help bring a kind of focused determination to finishing.
When & Where?
On further reflection, picking New England in August for my first attempt, was pure folly. If I had to do it again, I’d aim for September or October. Hot and humid were not just a possibility (despite the 7 am start), but a probability. Not a lot I could do about it. I had trained through August, sometimes timing longer runs at midday to acclimatize a bit. The one thing I didn’t count on? The rain.
Well, I did finish, but Sunday August 7th in Providence was a monsoon. And that is barely exaggerating. Fifteen to twenty mile an hour winds with driving rains for a good three quarters of the race. It did build a sense of solidarity among the five thousands that turned out, but man it was less than ideal, especially for a maiden voyage. Despite a fifteen minute delay at the start, leaving us packed and shuffling in the corral, the race was otherwise well organized on all fronts. They could have used more post-race shelter for runners, but I can’t fault them for not anticipating the storm. I would have liked to see them put the gear bags under tarps or something as finishing and picking up your soaked gear was a downer. The on-course stations, timing, and post-race recovery spread was good.
I made it around the course a few minutes under my goal time and despite some pacing issues (like an eager beaver I went out waaay too fast) will definitely be running another half again in the future. My last piece of advice? Reward yourself. Running 13 miles is nothing to sneeze at. Take a few days off recover and reward yourself. Me? I spent the next day lounging, stuffing my gut with BBQ and cupcakes.
As I’ve crept closer to my mid-thirties I’ve become better at curbing my instincts for buying up the latest gadget. Having to pay a mortgage and daycare bills will have that sort of mitigating effect. After seeing the new Garmin Forerunner however, I’m seriously fighting the itch. While mulling over my argument to Michelle about why I really need to upgrade my “virtual coach and training partner” I thought about how the Garmin (I have a now antiquated 305 model which feels like carrying a grandfather clock on your wrist) has changed the way I run the past three years.
Even if you’re just running for health maintenance and not training for a race or other goal, not tracking and recording your runs can be a mistake. I’m not talking about religiously recording every step like a deranged fitness accountant (more on that in a minute) but not keeping any record of progress makes it hard to measure improvement and easy to slip into a rut and simply plateau.
There is a dark side to being able to capture all those stats. In those first heady months after you strap a GPS to your wrist you’ll be setting all sorts of personal records and pushing to reach new goals. It’s fun. It’s invigorating. It’s enticing. Up to a point. Eventually you’ll reach a barrier and those PR’s and goals become harder and harder to accomplish. In and of itself this is not a bad thing and can help keep you pushing, helping you avoid that plateau. But it can also lead to disappointment and drain the fun out of running. Beware.
One benefit of pushing for those PRs and having constant access to pace and heart rate is the more closely you tune into your body. You’ll soon learn to judge your turnover in relation to pace and when you’re having a good day and a shot and when it’s not there. The latter is the harder lesson to learn. Not every time out is going to be a PR. Some days it will enough to just log the miles.
Something happened in the third year of running with the Forerunner. I started leaving it home more. I started running to just to run. I knew instinctively when I was loafing and when I was pushing. Some days I just plain didn’t care. I just wanted to go for a run and not be tethered to time and distance.
Did I just talk myself out of it? Maybe I just need to go for a run.