Saturday, May 24, 2008

Running Social


Running is inherently a big solitary, but lately I've checked out stuff online to make it more social. I've played around a little with RunnerSpace, which is what you'd expect. Runners Lounge is pretty similar. I decided to try out a new feature at FriendFeed, a service for sharing blog posts, links, photos, etc. The feature, FriendFeed Rooms, lets you set up areas devoted to particular interests. So began the Going Long room at FriendFeed. Just three hours old, it now boasts three members. This is truly the Long Tail.

7.1 miles 1:01 (Nike SportBand stats, so who knows)

Monday, May 19, 2008

A Sense of Pace: Internal Odometer vs Technology

I've gone running twice with the Nike+ SportBand. Both times were on a route I normally run during long-run recoveries. I figured the route is 5 miles. That felt right to me. But Nike+ told me the run was 4.72 and 4.69, putting my pace at 7:37 and 7:45. Uh-uh. I just didn't buy it. Yes, I'm still just 10 days or so from the marathon, but those runs felt faster, closer to 7:20 pace.

Tonight, I put my internal feel for distance and, more important, pace against Nike+ technology. Nike could argue it's not completely fair because I don't run in Nike+ shoes. Instead, I put the sensor in a pouch that attaches to the top of my Asics. Yesterday, on Twitter, I estimated that Nike+ was off .25 mile. My body told me it was a five-mile run to the Bridle Path, not these 4.72 and 4.69 miles that Nike said. To test the accuracy, I ran to the park, then started Nike+. I did the four-mile loop (technically, a USATF-measured 4.04). Nike+ told me 3.71 miles. I was pretty much exactly right about the distance. My internal odometer kicked Nike+'s ass.

It got me thinking about technology, something I write about quite a bit. For the most part, technology is great, even awe-inspiring the things it enables. Yet at the same time, I feel it's alienating people. We overlook the very simple things about life. It's why I was hesitant to add Nike+ to my regimen. Running is so basic, so elementary, so free of what Noakes calls "society's false privileges." My best miles in the marathon tick off one after the other, completely alike although unique. The times in the miles never vary too much. When there's a misplaced mile marker, our pack knew it because we had a sense of pace, developed with the most amazing piece of technology: our bodies. Bill Bradley, the former senator, was the subject of a great book called A Sense of Where You Are. The title came from the way Bradley, a basketball star at Princeton, described to the author how he always knew where he was on the floor without looking at the basket. He'd spent so much time practicing and playing that he developed an innate sense. We all have that, I believe, but we often don't trust it.

5.2 miles, 35:30

Sunday, May 18, 2008

How to Avoid Running Injuries

An inevitable part of the running experience is injuries, fearing them and getting them. Treating injuries sucks, mostly because it's hard to figure out whether there's really an injury beyond normal aches and pains. After all, pain is part of the deal with running. A good rule of thumb is whether the discomfort is localized (ie, not a general soreness over an area) and affects the stride. If it does, time to treat it.

Prevention is obviously the best cure. I get asked how I avoid injuries. After all, I run a lot -- probably 1,500 miles a year -- frequently on hard surfaces. Plenty of people have predicted knee and hip replacements in my future. Up until now -- knock on wood -- I've fared alright. Here are my commonsense tips for avoiding running injuries.

1. Efficiency. Yes, we're all born to run. I was reminded of this again when in Cincinnati for the marathon. My friend Tom, who tried to poison me with jambalaya, has a daughter about 18 months old. She's just starting to walk. Elena's impulse, though, is to run. But just because running is natural doesn't mean it doesn't require thought. Running is hard on the body. Your body weight comes crashing down on joints and tendons with each stride. Even Lance has said how hard running is because of the pounding. The best way to mitigate the trauma: lower the force. You do this by paradoxically taking shorter strides. Look at the best runners and you'll find they're very economical. The goal is to have your feet off the ground for as little time as possible. Aim for short strides. Don't bounce. Repeat: never bounce. It also helps not to carry around a lot of weight.

2. Soft Surfaces. There are many great parts of living in New York City. One of the downsides is the dearth of running trails. I still try to do as many miles as possible on softer surfaces, dirt paths in Riverside or the Bridle Path in Central Park. The softer the surface, the less trauma. A modest proposal: We turn the golf courses into runner parks.

3. Stretching. Yeah, there's a school of thought that stretching is actually bad for you. Don't buy it. Stretching done incorrectly is bad for you. Lots of people treat is like a battle, grimacing while yanking their leg is a direction it clearly doesn't want to go. Since I came down with a tendon injury three years ago, I've done Active-Isolated Stretching. It's really helped me improve my flexibility, which was never great and became more constricted with all the miles. The principles of AIS are that the key to stretching is to isolate a muscle and apply quick (two seconds) pressure to slowly increase the range of motion. There's a rope involved. A father-son duo put on a class about it for the New York Road Runners.

4. Core Strength. My near-term goal for the summer is to get stronger. My upper-body strength is pretty pitiful, and it hurts me at the end of races. Injuries commonly happen when there's a set of muscles that's getting a lot more work than another set. (OK, this is a little outside my realm, but something like this is true, I'm sure.) There are lots of regimens for building strength. I do Pilates exercises in my apartment, a site the people across the way must love because it's typically shirtless after a run.

5. Patience. This is the hardest to follow. Lots of people fall in love with running. They're like your friend who meets a girl and all of a sudden is always over her place. That works out sometimes, but often ends up a mess. Lot of injuries happen when people try to do too much too soon. The marathonification of running has made this worse. Casual or non-runners decide they're running 26.2 because they had a four-mile run and it's a life goal. Running marathons is hard and the distance requires respect. I ran for two and a half years before training for a marathon. It wasn't the first race I'd run, but a gradual progression from four miles to five to 10K to a few halves. I realize there will always be "marathon tourists," the people who run for six or nine months to slog through 26.2 in five hours or so, like they're climbing the Eiffel Tower. That's pretty uninteresting to me, particularly if they don't stick with running. Doing marathons is just the byproduct of running as an essential part of a healthy lifestyle, not just physically but mentally.

Tracking Runs via Nike+ SportBand



Despite my day job covering how digital technology is changing media and advertising, I'm a bit old school with my running. One of the great things about running is its simplicity. You only need sneakers, although shorts and a shirt are probably a good idea. Sure, I run with a $30 triathlon watch, but that's about it. I've been of two minds about Nike+, the system that lets runners record and share workouts through their iPods. On the one hand, I've admired it as a legitimately revolutionary step toward marketing as a service, something I've written about quite a bit. Yet as a runner, it never appealed to me. Why? First, I don't believe in listening to music while running. I used to say it was for "the mentally weak." But more seriously, I think it's dangerous, not because of muggers necessarily but the more dangerous runner foe: cars. Taking away one of your senses is dumb. And it's true that "real runners" typically don't listen to music while running. Music is often used as a crutch by people who say running is "boring." Since running is the one time of the day I'm truly alone with my thoughts, this leads me to conclude those people are the boring ones. It's also an artificial stimulant. I see people surge when some song comes through their ear buds. Fine and all, but not exactly an efficient way to train.

With all that in mind, I figured Nike+ was properly aimed at the mass-market lifestyle runner. Then the SportBand came out. This intrigued me because it did away with the iPod in favor of a watch-like band. The idea of easily tracking my workouts is very appealing. On Saturday, I dropped $60 for the system. I don't run in Nikes, so I got a little pouch that attaches the sensor to the top of my Asics, rather than the built-in opening in Nike shoes. I know Nike wants to sell shoes through this system, but I can't think of many people running for years who would suddenly switch shoes. It just doesn't happen, unless you've had injuries. So far, I'm underwhelmed. The chart above shows my run today. After nine years of running, I figure I have a pretty good sense of pace. There's no way it was that slow. I ran today more at 7:30 or a little below. The graph also has all these peaks and troughs that don't make sense. It would have me believe one mile was 7:02 and another 8:13. I'll keep trying it to see how accurate it is. Right now, I think my regular watch and knowledge of the distance works just fine.

Saturday, May 17, 2008

Ryan Shay

I came across this video from an ESPN segment about Ryan Shay, the marathoner who died during the Olympic Trials here in the fall. It focuses on Alicia, his wife, who is now trying to accomplish her own dream of running in the Olympics in the 10K. I'm not much for public memorials, but there's a nice understated one to Ryan in Central Park. On the way up Cat Hill, there's a rock with "Shay" written on it.

4.72 miles, 36:00

Tuesday, May 6, 2008

Race Report: A Step Forward

Going into the Flying Pig, I had reservations. For one, I knew my training wasn't quite there to run a 2:59, one of the two running goals I still have. (The other: do Comrades.) I wish I'd trained more, harder and smarter. But you go to war with the army you have, not the army you'd like to have or plan to have, I guess. The week before the race was a whirlwind, with lots of travel and work -- and too little sleep.

Pre-Race: I stayed with my friend Tom and his wife Kremena before the race. One thing I learned, which I should have known, is it's not ideal for me to combine running marathons and visits. Sure, it's convenient, but I'm too distracted. I just wanted to sit down the day before the race rather than go anywhere. We went up to Cincinnati on Saturday, picking up my number and then eating at friends of Tom's in northern Kentucky. I was pretty nervous. I ran once in the week before the race, not out of strategy but a lack of time, and just five times over the previous two weeks. Maybe this was for the better. I felt like shit, that's all I know.

The Start: I got to the starting line at a little after 6am, following a fitful night sleep in a disreputable Travelodge in Newport, KY. The weather was great, probably in the high 40s or low 50s. I went right to the start area to get in the right frame of mind. I never know what to think about standing there, waiting to begin the long journey. One trick I try is to visualize what it'll be like running the course, even though I'd never stepped foot on any of it. Most of all, the battle is to relax. That's so important in running. The race director came on with some "bad news": the start would be delayed because of a fire along the course. What's more, it would be a quarter mile longer. It took a few seconds for everyone to realize he was serious. Inauspicious.

Miles 1-4: I promised myself I would go out slowly. The Flying Pig is pretty hilly, particularly the first eight miles, when it gains tk meters of evelation. My idea was to go out at 7:30, then see how I felt at mile 8, when the worst of the hills were crested. The start was a bit crowded but not too bad. Mile one flashed by at 7:29. Perfect. The next couple miles, the course wasn't marked correctly. That happens in smaller marathons. Mile 2: 6:39; Mile 3: 7:57. Add them together, about 7:15. This was where I caught on with the 3:10 pace group, which turned out to be a savior. Mile 4: 7:20.

Miles 5-8: These miles were decisive. The course went over to Kentucky, traversing the many bridges over the Ohio. We then headed east and started climbing. Dave, the pace leader for the 3:10 group, was awesome. It's unusual for a pace leader to factor in the hills. Usually, they're tyrannical about staying on pace, but Dave rightly knew that we could give up time in the ups to make up in the down. Mile 5 was 7:14; Mile 6: 7:09. Then it got tougher. Mile 7 came in at 7:30, followed by another tough 7:22 . At this point, I felt good, not overly fatigued, but my feet were a little sore. So far, no tightness or muscle soreness.

Miles 9-13.1: I think of these as middle miles. At this point, I'm into the groove but not yet at that point of comfort where I'm clicking off miles. The best feeling as a distance runner is to be a metronome, knocking back miles almost mechanically. It's an amazing feeling. Mile 8 was a slow recovery at 7:13 for Mile 9. At this point, we picked up the pace noticeably. At first, I struggled a bit and faded to the back of the 3:10 pack. Mile 10: 7:10; Mile 11: 7:00. At this point, I seem to remember Dave dropping off for a pee while another guy, much more annoyingly voluble, took over the pacing. He messed up the mile, and we came in at 7:26. This was reeled back to a 7:16 to come into the half at 1:35:43. I take assessment at the half. At this point, we were on pace for, with even splits, a 3:11: 30. Not bad.

Miles 14-20: My confidence was up at this point. Even though I felt great, I was totally determined not to overextend myself. The Delaware and Indy experiences hung heavy on me. Yet I was nearly equally determined to leave it out there. That's the paradox. I'm haunted by the fact that I didn't run 75 seconds faster in Philadelphia in 2005 to run sub 3. I finished with gas left in the tank. That sucks. These are typically my miles. I typically run my best between the half mark and about mile 18. I don't know why. Mile 14 was a slow 7:26, followed by a 7:08, 7:06, then down to a 7:01 at 17. I was running at the front of the back now, and ventured out beyond it with one guy. This was, in retrospect, a mistake. Mile 18 was 6:53, but I started to fatigue. Mile 19 hurt at 7:23, but I pulled that back to a 7:07 at 20.

Miles 21-23: In every marathon, the goal is to get to mile 20, then scratch and claw. I've done this so many times, but I've never figured out a way to plan for what happens beyond 20. It's a total crapshoot. We were heading down into the city, along the Ohio. It's mostly downhill. Mile 21: 7:07. Mile 22: 6:59. It was here that I started to lose touch with the 3:10 group. I wanted to keep up, yet I worried about blowing up. 3:15 is my Boston time, so I played it safe. Was that a mistake? I don't know. Mile 23: 7:25

Miles 24-end: Flush with pain. It's true that the discomfort at the end of marathons is difficult to describe. The best word is dispiriting. The experience helped lots, because I was ready to deal with how bad I felt. I saw people pulling up with cramps or walking uphills. I would shorten my strides, power away. Mile 24: 7:17. By now, I'm counting down to what the distance left is in city blocks. Mile 25: 7:31. The last mile, I completely played it safe. It comes up on my watch at 9:14, which can't be true. My guess is the extra quarter mile added came in here. According to the chip time, I did the final mile in an embarrassing 8:20. Yikes. The guy finishing before me was dragged across and put into a wheelchair.

Final result: 3:11:55; 7:15 pace; 132nd of 4728 overall; 19th in division.

Takeaway: Cincy was a great experience. The race went as well as I could have hoped. I ran, for the most part, very evenly and under control on a pretty hilly course. I still think it's possible to run a 2:59 in the fall.

Wednesday, April 30, 2008

The Countdown: Worrying

It's unavoidable to worry before a marathon. Runners worry about phantom injuries, possible illnesses, lack of training, everything. The ideal for me has always been a relaxing week before the race, without job stress. It never works out this way. That's why I'm typing this going on hour 12 at the office, with a "jumbo cheddar turkey burger" (albeit with a baked potato) on the way. I don't think the Ethiopians are in drab office buildings scarfing down food from Cozy Burger four days before races. But there's not much that can be done. I had to make a quick trip to Minneapolis on Monday and Tuesday, with lots of screwed up sleep because of early flights and/or late nights. I'm tired and feeling the taper depression.

Wednesday, April 23, 2008

The Mind of a Marathoner


Out at dinner last weekend, a woman found out I was running a marathon and asked the inevitable: "What do you think about all that time?" I never know the answer to that question. During the average long run, there's time to think about lots of stuff, zone out, consider breathing and plan for fueling. But the marathon is different. It's about a high-level of effort for three hours and more. That takes a lot of mental energy. Trying to stay relaxed but not slough off is kinda hard. It gets worse when the shit goes down around mile 20. At that point, the mind races to all sorts of things. I've found that after a marathon, I have the craziest dream sequences: my mind races through all sorts of dreams on fast forward. The interesting thing is the elite runners go through the same stuff as regular marathoners. Ryan Hall, the best U.S. marathoner alive, has a fascinating article about his recent marathon in London, where he ran a 2:05. He talks about taking in the sights -- at a 4:35 pace -- along the way, trying to stay relaxed, wondering if the pace was right, and trying to find his rhythm. His description of the end is fitting -- even the best in the world suffer along with the rest of us mortals.
The fatigue I feel in a marathon is unlike any sensation I have felt. The last couple of miles I felt totally numb. Its like what I picture an out of body experience to be like. My legs don’t feel like they are mine anymore. No matter what I say or how hard I pumped my arms they just kept going at the same rhythm.
Let's hope for the out-of-body experience in Cincy.

5 miles, 36:40

Saturday, April 19, 2008

Ten Signs You're Tapering

I'm in the tapering period for the Flying Pig. It's two weeks away. The neverending taper debate is two weeks or three. I've gone both ways, with mixed results. Before one of my fastest marathons, a 3:02 in Chicago in 2002, I ran in a 100-mile relay race two weeks before the marathon. All told, my portions were about 20 miles of hard running. I was no worse for the wear. Other times, I went with two weeks and felt stale. Who knows? One thing is for sure, the taper is the worst part of preparing for a marathon, for me at least. Some people look forward to the relaxation, but I don't find it relaxing. My body finds it disconcerting that all of a sudden it's not exerting itself as much. As one message board poster put it, "We're in the barn now." During my run today, I thought up some signs a runner is tapering.
1. You say things like, "I'm only running 12 miles today."
2. Meetings at work seem even longer.
3. You are absolutely positive you've hurt your hamstring, calf, IT band and back.
4. You register to post on Runners World message boards.
5. Maniacally checking weather forecasts 10 days in advance.
6. Running feel sluggish until four miles, but you're only going five.
7. A treat is not eating pasta.
8. Hours are spent debating the right socks.
9. Trying to sleep, you resemble a hot dog at 7-11 turning around and around.
10. Chariots of Fire winds up in the NetFlix queue.

12.2 miles, 1:26:14

Sunday, April 13, 2008

Running Alone

Earlier this week, one of my Twitter friends asked me if I trained alone. I felt a little awkward replying nobody. It's not that I'm opposed to the camaraderie of running, but I don't have any friends here to run with on a regular basis. It hasn't always been that way. I have great memories of long runs with Stroh of Arabia, particularly when we'd head north and explore the top bits of Manhattan. We even ran two 50Ks together, which are among my fondest running memories.

It got me thinking during my long run about running alone. One of the things I like most about running, particularly long distances, is it's disarmingly personal and solitary. Anyone who has run over 20 miles knows this. Go to a marathon, set up shop around mile 22, and look into the eyes of the people going past you. While the cheering and crowds might help, the real battle is personal. They're totally alone, in many ways, confronting uncomfortable truths, like the overwhelming fatigue that inevitably makes them want to quit. But most don't. That's overcoming the Internal Pigdog. Today, I set off for Central Park by myself to run 20 miles. I've done this literally dozens of times, yet it unnerves me each time starting out. I wonder how I'll deal with the discomfort and fatigue. The marathon only heightens this, with the fear of failure always lurking in the background. Tim Noakes wrote some very true (if overly wrought) words about this in his awesome Lore of Running:
Running provides complete solitude. Even in the most crowded races, we reach points where fatigue drives each of us back into ourselves, into those secluded parts of our spirit that we discover only during times of durress and from we we emerge with clearer perspectives of who we truly are.
20.2 miles, 2:27

Monday, April 7, 2008

Marathon Countdown: Four Weeks

Quite amazingly, there are only four weeks until the marathon. These things always sneak up on me. My friend Tom is trying to get me to sleep in a smoking room at the Ramada Inn in northern Kentucky. I'm resisting that option. Despite my grand plans, I haven't been structured about my training at all. Coming down with the flu didn't help. Here's my evaluation of where I'm at:

1. Miles per week: I'm peaking at about 43. That's not a lot of miles. In previous marathons, I'd get up to 60 miles per week. Right now, I'm just working too much for that. Running six days a week isn't happening, and my regular runs are 6.2 miles.
2. Speed: Here, I'm doing alright. Early in the winter, I was doing really well, regularly doing my daily runs right at the 7-minute pace. Since then, I've actually regressed, for a variety of reasons, and now my runs are closer to 7:15.
3. Long runs: So far, so good. I've done three 20 mile runs, including a 20.2-miler on Saturday in 2:29. I also ran a couple 18s. I'll probably do two more 20s the next two weekends.
4. Races: Again, not so great. I've only run two half marathons. The Manhattan Half went quite well; the Bronx, not so much. I wish I'd done a few more to get used to suffering.
5. Speedwork: Nope. I don't know what it is, but I just can't get myself to do speedwork. This is troubling, because I won't get better at this point doing the same training I've done for years. My body has reached where it can go with that. I can see that with the consistency of my run times. They're all pretty much the same. I'm not happy with myself over my inability to get into speedwork. It's why I need to join a running club.

Overall, I'm OK with my training. I've come to grips with the face that the 2:59 Project will have to wait for the fall. I'm just not there yet. But I'm there to run a sub 3:10 marathon, I think. We'll see how the last few weeks of training go.

Sunday, March 23, 2008

Why I Started Running

One of the questions I typically get from non-runners is, Why? What's the point of logging all those miles in all sorts of bad weather. I was reminded of this when Laura posted about how she first fell into running. Everyone has their own story about how it happened. For Laura, it began during an internship in Florida.

My running story began in Washington, DC, in 1999. I'd lived there for about a year and half, mostly unhappily. Some people love Washington; I wasn't one of those people. I had my first job out of school, spending my days doing work of dubious value and living in basement apartments on Capitol Hill. I'd even started to become a social smoker, buying a pack on Friday, then putting it out on a newspaper box on the way to the Metro for a homeless person. At some point, I realized I needed something new. It turned out to be running.

I started just going for a jogs around a park near me on the southeast side of Capitol Hill. I probably ran about 20 minutes before feeling winded. But I knew the consistency was key. My goal: run five nights a week. This proved hard, partly because I was totally out of shape and partly since it was the start of summer in Washington. I kept at it. My shins would kill me, but I got hooked on how great I felt after a run. It was that summer in Washington -- my last, as it happened -- that I learned the No. 1 thing about running: I never felt worse after a run than I did before it.

Shockingly, I've now run for nearly nine years. In that time, I've run 13 marathons, including two 50Ks, come within 63 seconds of running a sub-3 hour marathon, and logged thousands of miles. The decision to start was the best and hardest decision during that time.

6 miles, 43: 40