Race Report: Eugene Half

Oh hey there blog, I’ve missed you. Want to chat about a really cool race I ran about a month ago? I remember it decently well. Let’s take a crack at it and just see what happens!

For those of you not familiar with the Eugene Marathon, it takes place in and around Eugene, Oregon, a picturesque college town (not unlike Athens!) that is legendary for its running culture. Hayward Field is the locus of the legend, having been home turf to such notable athletes as Steve Prefontaine and Jordan Hasay. Both the full and the half actually end on the track itself, which is of particular note since 2018 was the last year before the stadium closed for major renovations, including a full replacement of the original track that Pre and others actually ran on. So we were the last ones to share the same surface as the heroes who put the place on the map.

Our own journey began super-early…

Super-early, Thursday morning (April 26): The Lady and I woke up at the butt-crack of dawn to catch a 9am flight to Portland, OR. We were lucky to be able to stay with our friends Keeley and Dave, as Keeley would also be running the half, so we were able to split an Airbnb in Eugene.

But that night we crashed in Portland. In fact, we made a point of rushing over to Portland Running Company for their Thursday group run, attended by none other than Mark Remy! We gabbed the whole 5 miles around town, and joined him and some of the PRC folks for a beer at a nearby brewery (Portland has a few of those).

Friday, April 27: We hit the road for Eugene! It took a couple hours, but the drive was awfully pretty. We checked into our Airbnb, which was adorable and easily one of the nicest I’ve ever stayed in.

(ignore for the moment I’ve stayed in all of about 2-3 Airbnbs)

Saturday, April 28: We kicked off our day by going to an amazing waffle joint for breakfast following our morning shake-out run. After that…

…drum roll…

Infinity War! I mean, can you think of a better way of staying off your feet the day before  a race than going to see a movie? I won’t give away any spoilers. We ended up spending the evening at our Airbnb watching Thor: Ragnarok (as Keeley and Dave had not seen the complete movie).

Sunday, April 29

I haven’t really said anything about the race, or what my goals were. Frankly, I wasn’t sure. I was aware that I’d been making strides (very, very slowly) and improving my times over the past few months, but I still felt like I had no gauge for what I was capable of. Yes, my mileage was piling up, and that was extremely satisfying to see, but I still felt shorthanded when it came to quality workouts like tempo runs; I tended to burn out pretty quickly.

It rolled around my head all morning as we prepared for the race, established the game plan with Dave (who would be the chauffeur and cheering section), and culminated when we got to the field in a kernel of a radically different plan.

Photo Apr 29, 14 29 18

Right outside Hayward field!

I kept thinking about my recent half marathons; Chickamauga and the most recent Albany had been great ego boosts, but the AthHalf just the month before Chickamauga–while still a solid performance–had been bruising. I’d just completed easily my most intense training regimen in years, but I still just couldn’t convince myself that I was ready to set an ambitious goal and run it into the ground. I still had so many question marks about my fitness, particularly my fast-twitch endurance, and my mental toughness over an extended race.

So my thoughts went over to The Lady, who was gearing up for her latest run at a Boston Qualifier, having also crushed a tough training cycle, and the thought struck me:

The half and the full run the first 10 miles together. That never happens. Nor, really, does the opportunity to run our respective [different] races as part of the same event. So I made the decision: forget my race. I don’t care what time I get. My goal is to make sure The Lady reaches mile 10 at a flat-8 pace (a 3:30 finish at that pace, well under the qualifying time for her age group). I’ll worry about the last 3.1 when the time comes.

And I actually relaxed. I mean, I knew an 8-flat for 10 miles would be hard for me; I hadn’t put that kind of consecutive workload together for years. The last time I remembered even doing that pace in a half marathon was March 2015’s Georgia Publix Half. But for once I wasn’t obsessing about my own race, and it felt good.

The feeling only lasted for a minute, though–once the race kicked off, I felt like shit in the first mile or two. But probably because…

7:56, 7:46, 7:54

…I was going a bit too fast 🙂 I tried to rein things in a bit, but I stayed pretty much glued to The Lady, hawking my own watch to keep us on-pace and letting her do her thing. The entire first 10 miles are basically in and around neighborhoods of Eugene, so the views were cozy and beautiful.

And did I mention: the weather! It was overcast (par for the Pacific Northwest), but not rainy! And it was very cool; starting temps were in the mid-40s, which is perfect.

8:07, 8:06, 7:47

I definitely felt better into mile 4 and beyond; despite a warm-up mile before the race, it seems like I still needed a few more miles to really shake off the rust and settle in. The super-flat neighborhood stretches also helped, and my revamped half marathon playlist was keeping me pumped without overdoing it.

7:52, 7:51, 8:06

It was at mile 9 where we encountered The Hill. I don’t know what it’s actually called, but it’s pretty much the only hill of any consequence on the course. Don’t let that fool you, though, as it almost did us: just because it’s the “only hill of consequence” doesn’t mean it’s a weenie. It’s no Negley or Baxter, but we had numerous folks at the Portland Running Company group run mention that this hill derailed their race in previous years.

We plowed up the hill. I had AC/DC’s “Thunderstruck” blaring so I was pumped. The crowd support, fantastic pretty much everywhere, was phenomenal on this hill, cheering us to the top where there were banners congratulating us on reaching the apex and encouraging us into the relief of the downhill.

It was awesome.

Of course, it was only once we’d climbed the hill and descended the other side that I realized I was definitely starting to hurt. I was also stoked that it hadn’t registered until just then! But I was almost to 10 miles, and I’d kept The Lady at a rock-solid pace (maybe even a bit faster than 8), so I needed to hang on just a bit longer.

At this point, the race exited the neighborhoods and went onto some trails. This changed things somewhat, as the route became much windier, which didn’t do much for my feeling of flagging.

8:02

It ended up being almost mile 10.5 before we reached “the bridge”, the advertised point of the half and full courses splitting. In fact, at some point, The Lady had asked if we’d somehow missed the split–we’d gone well past the 10-mile mark! Was she inadvertently now on the half course, or–horror of horrors–was I inadvertently on the full? Thankfully, no repeat of my 2012 Air Force half marathon (how did I not write a blog post on this?! tl;dr I was having the best race of my life up to that point and then was mistakenly diverted onto the full course for almost a full mile); the split was just farther down the course than either of us had realized.

242ceebe-e7cd-4b3d-8800-8c1fd79405a6.jpg

This was taken on that very bridge, seconds before the half/full split.

We wished each other good luck as we crossed the bridge. I hadn’t been able to get a good feel for how The Lady was doing, but I also didn’t want to bust her Lizard Mode bubble, so I let her know I was proud of her, regardless of what happened.

She’s a badass, BQ or no.

Me, on the other hand–moments after the split, I stopped and walked for a bit. Partly to give myself a break, but also to take it in: holy SHIT. I’d just thrown down a flat-8 pace for 10 miles! I hadn’t done that in YEARS. AWESOME.

I had no plan for this juncture of the race, but I honestly didn’t care. So I cranked my music and kept plugging away as the trails continued. These trails kind of kicked my ass, to be honest; the weaving and all the minor bumps and dips were making it tough for me to find my own Lizard zone.

Perhaps amazingly, my last 3.1 weren’t all that far off from the previous 10 miles:

8:12, 8:14, 8:18

Managing to kick things up to a 7:04 pace for the last 0.1 (my watch measured 0.2), I finished with an overall of 1:45:43.

Which was, in my fact, exactly my best half time since the March 2015 Georgia Publix Half.

Photo Apr 29, 14 00 47.jpg

Eugene finishers! Left to right: Dave, Keeley, The Lady, me

I waited at the finish for Keeley (also doing the half), at which point we met up with Dave (who’d enjoyed some hiking + alone time to vent about putting up with runners) to engage in the subtle art and definite witchcraft of Predicting Where The Lady Would Be So We Could Cheer Her On.

We found a spot around mile 22(ish) that was easy to get to, and set up shop. When The Lady came by, I ran with her for just long enough to ascertain how she was holding up, grab a selfie, and to remember that I’d just raced a half and didn’t have functional legs.

Photo Apr 29, 13 29 18.jpg

Would YOU be smiling at mile 22? Like I said: badass.

(I’ll link to The Lady’s race report once it goes up)

After the race we went back to the Airbnb to get cleaned up and, unfortunately, check out. We couldn’t really even stick around to relax. By evening, we were back in Portland, though we did take this opportunity to buy a bunch of ice cream and play several round of Peggle before happily crashing.

Monday, April 30: Another bright-and-early wake-up to catch a flight back to Athens. We said goodbye to our hosts, thanking them both for putting us up (and putting up with us). The flight and drive back, while long, were uneventful.

Final Thoughts

Even now, a month after the race, I still don’t know where my fitness really stands. I still burn out on quality workouts pretty quickly, but I seem to have a strange ability to maintain a sustained pace for a longer-than-expected period of time if my mental game is on-point.

And maybe that’s the real take-away here: my physical fitness is absolutely, definitely, positively coming back. More quality workouts, especially tempo runs, would certainly help things, but the sheer volume (and lack of injuries KNOCK ON WOOD) has done wonders on its own. What’s still missing, what would really get me to the next level, is an improvement in my mental game.

Annnd I’m still kinda stumped on that one. As the summer months close in, and the temperatures and humidity skyrocket, mental toughness will be the name of the game; so in some sense, I can count on a baseline level of development through simply maintaining this volume through the summer. But I’m still hungry for getting on the hunt again: a sub-1:45 half marathon that puts my PR on notice, a 45-minute 10K, or even a pair of sub-7-minute miles strung together.

I’ve come a long way in the past 12-18 months; the progress is tangible. If nothing else, Eugene was an indicator that, if I can get my mental game in order, there’s a lot more progress to be had.

Photo Apr 29, 17 43 26.jpg

Oh Pacific Northwest, you so purty.

Advertisements

Injuries and All-Binny (Albany Half)

Yeah yeah, it’s March already and this is pretty much my first blog post of the year, despite saying I would blog more often. It’s a work in progress.

At any rate, January started off well, but February was marred by my first injury of the year: some kind of inner knee muscle/tendon pull. I can’t be more specific because I’m honestly not sure what it was, but during runs I was starting to feel a “pull” in my left knee (inside the right part of the socket). I thought perhaps it had something to do with a really tight inner left groin tendon I’d been trying to stretch over the previous couple weeks, but even now I have no solid proof.

You can see the progression of it pretty starkly:

Screen Shot 2018-03-04 at 3.35.44 PM

After recording my highest single-week mileage since April 2015 (!), I was starting to feel that pull during the workouts the following week. It’d go away–like it was a muscle that needed to be warmed up–but by the time Saturday’s long run came around, it wasn’t going away. Hence, a 2.6-mile run was all before I bagged it.

The next week was rest, followed by cross-training of ellipticals and rowing machines. I did try to run on it that first Thursday on the treadmill, but quit after only 0.4mi as I could feel the pulls getting tighter with each step. Wasn’t worth it.

In addition to heavy cross-training, I also brought back some single-leg workouts I picked up from PT back in Pittsburgh. All that together seemed to do the trick: I ran 8 pain-free miles the following Saturday, and then slowly upped my mileage over the next week with no problems.

I’ve since been congratulated many times on showing restraint in how I approached the injury, and the abundance of caution I exercised. I missed 100 miles in February (had 82.98), and my race fitness for the Albany Half this past weekend certainly took a hit, but a week off running that results in missing a small mileage goal and slightly degraded tune-up performance versus potentially multi-week (multi-month?) downtime? I’ll take the former, thanks.

Which brings me to this past weekend: the Albany half marathon!

This is actually our third year participating in the event–Strava was kind enough to remind me of this fact and show me the trend over those years in my performance.

Screen Shot 2018-03-04 at 3.48.45 PM.png

SPOILER ALERT I’m improving!

This year (as with every year, I think) I went in with pretty low expectations. The Lady and I had just had a brutal work week, including at least one night for both of us where we didn’t get more than a few hours’ sleep. And I’d missed a week of training a only a few weeks before, courtesy of the aforementioned injury. Still, I was hoping to put in a performance at least on par with last year’s. Furthermore, The Lady was treating the race as a tune-up for Eugene, and with her job promotion formalized on Friday, she wanted to see just how much wind she had at her back! And I, of course, wanted to see if I could keep up 🙂

Things certainly started off with a bang: I got a little caught up with the fast-packers, especially since The Lady was out to see what she could do at the halfway point for our Eugene race in late April. The first few miles were a bit faster than I’d originally planned:

8:04, 8:10, 8:06, 7:51

Still, I’ve internalized over the past few years that one should not look a faster-than-anticipated mile gift horse in the mouth. Instead, consider it a gift of buffer space if needed later in the race when things aren’t clicking quite as well.

Somewhere within the first mile, one of our own Athens Road Runners snapped my picture.

28515986_10213627063004783_4117420558916198550_o

Mile 1 and Feelin’ Fun.

I kept considering slowing down, but around mile 2.5 was a water stop, and I was slowly passed by a group of steady-paced racers, and I just decided I’d hang with them for as long as I could. I was also intent on focusing only on the mile I was on: do what felt good, and worry about the later miles when I got there.

8:00, 8:08, 8:08, 7:56

Still rock-solid pacing, though after the very first mile I didn’t look at my paces, opting to go entirely by feel. I was also definitely starting to feel the pain at this point, my week off from running thrown into sharp relief. I yearn for the days when flat-8s for 13.1 miles feels like a manageable workout instead of a race, but that was not this day.

8:14, 8:11

At this point, I definitely had to start letting that pacing group go, as I just wasn’t feeling it anymore. There was a long, uncovered stretch on a main city drag around mile 8.5; it’s right when things start getting hard, it’s completely unshaded, and it’s long and straight and pretty much flat as a pancake (with a slight uphill, if anything). That one hits pretty hard, and I knew it would be a slog from there.

8:31, 8:21

Yeah, definitely in pain at this point. I was still focused on just the current mile, but I had resumed checking my mile splits, which didn’t help my mental game. I did, however, blast Wonder Woman’s Wrath (and again as I neared the finish). That helped.

8:30

This was really freaking painful. I felt completely gassed and just wanted to cross the finish line. I will say, though–I didn’t feel any of what, until now, had become almost a refrain of being angry with myself at this point in the race for not performing as well as I thought I should’ve been. Certainly a mental game improvement!

The Lady got some pretty awesome pictures of me coming into the finish at a surprisingly-brisk 7:17 pace for the last 0.3 (ok, 0.1, but my watch measured 13.3 so):

I crossed the finish line at 1:48:16 (unofficial), which set a new course record for me by about 15 seconds!

28619386_10213627186927881_4340936163456539820_o

It’s all in the headband.

It wasn’t a hammer-drop shatter-the-ceiling outing; it was a 15-second improvement over last year, though about 90 seconds slower than last November’s Chickamauga. And it’s still a good 7 minutes beyond my still-standing 2014 half PR. But it did tell me a few valuable things:

  • My mental game is slowly improving. My focus on each individual mile is a small, albeit crucial, step forward. I can’t run with reckless abandon if I’m counting down the miles the whole time.
  • Taking some time off if something is making running physically uncomfortable is always, always, always a good decision. Even if you rage against it at the time.
  • It’s slow, sometimes agonizingly so, but physically I seem to be getting back into things as well. The last three years have been marked by an almost token ~1:53 half marathon time, but in the last year I’ve seen more 1:48s than 1:53s. That’s still a ways off from my PR, but again it’s a definite sign of progress.
  • Snickers are delicious.

In a couple weeks I’ll be doing a fun 15K trail race, and then in late April it’s off to Eugene, OR for the half marathon, while The Lady aims for her second BQ!

Photo Mar 03, 17 10 21.jpg

Just keep running, just keep running, running, running…

I’m getting stronger. Slowly, agonizingly slowly, but I’m undeniably getting stronger.

Screen Shot 2017-03-09 at 5.00.01 PM

A few weeks ago, I recorded a weekly mileage of 38.07. That may not seem all that amazing, but I haven’t hit a 1-week mileage in excess of 38 miles since my Big Sur marathon training in late March 2015, nearly 2 years ago. It’s been a long. damn. time.

Last October, I ran the Ath Half in 1:48:52, a 5.5-minute improvement over the previous year. Just this past week, I ran the Albany Half in 1:48:24, the fastest half marathon I’ve run since the GA Publix Half almost two years ago, also in March 2015. It’s been a long. damn. time.

As has been a regular mantra here of late, I still have a long, long way to go. I’m still barely within sight of my half marathon PR of 1:41–set back in May 2014–and I haven’t done speed work in so long I have to actually sit down to think about what a 7-minute mile would translate to on a per-lap basis.

My mental game is also an utter disaster. I seem to have completely forgotten how to push when I’m entering the pain cave; I mentally cringe and try to hold the pain at bay (which, of course, does nothing except exacerbate it) instead of accepting it and feeding off it. My brain runs at a million miles an hour, just like it does at work, which all but keeps me from settling into a rhythm and letting the miles just tick by.

And holy crap, I can NOT give myself a break. Remember just a few paragraphs ago when I mentioned this year’s Albany Half? By all objective measures, and especially in my specific context, I performed extremely well. Intellectually I understand that, but emotionally I just cannot convince myself I ran a good race, that I’m improving, and that I should be proud of my performance. All that registers on an emotional level is that I’m still 7+ minutes away from taking another crack at my PR, and jfc my mental game is shit.

I know at least some of this is, as always, the fault of the crazy stress levels I’m feeling from work. I’m 300% overextended with no end in sight until at least July; every week is a new version of finding a way to squeeze 100 hours of work into 60, which invariably means dropping the ball on some things, pushing off others, and outright sucking at whatever’s left. Running may be an escape, but it doesn’t exist in a vacuum; it’s still a function of everything else that’s going on.

One of the few reasons I’ve managed to stick with it is because everything else is also a function of running.

It’s March already, and I still haven’t outlined a concrete set of 2017 resolutions. Or, as of last week, Lenten resolutions.

There are definitely some things I want to do that I know would help across the board. For instance, yoga 5x/week: I did this back in grad school for several months, and the results were absurdly awesome. The problem is when the debate inevitably arises between sleep and yoga, guess which one wins 95% of the time.

I also want to start regularly incorporating core work and weights. For the latter, I’ve already been semi-successfully bringing back “DropAndGiveMe.” But core work has been nonexistent, as allocating time for it has largely run into the same conundrum as yoga.

Speed and tempo work are things I’d like to do regularly, but as long as I’m getting the miles in, these won’t be too difficult to mix in.

Finally, I need to get my diet back on track. Through January and half of February it was pretty good, but I fell off the bandwagon. Stress snacking is one of my less-healthy coping mechanisms, but definitely something I can work on without a huge additional time investment.

As I’ve said, I don’t really know how I’m going to implement some of these. But I suppose it’s a lot like my running. I honestly don’t know how I’m going to get back to making runs at my PRs, but somehow, I’ve kept plugging away when I’ve had no desire to. As a result, every measure says it’s been paying off. Progress has been agonizingly slow, but undeniably measurable. Maybe that’s a good way to approach these resolutions: even when it isn’t pretty, even when it feels like it isn’t working or I would be better served by forgetting about it this time and trying again tomorrow: just keep plugging away.

Just keep running!

9k=-1

Finish chute photo!

Race Report: Holy crap, where did that come from?!

To those of you who stop running because it became tiresome and grindy: I absolutely get it.

The last year of running has been the most unproductive and least enjoyable that I’ve ever had. It’s come from a really bad combination of 1) stressful job that hasn’t let up in this time frame, and 2) bad, lingering injuries that have been extremely slow to heal. I’ve had to mentally put myself in the position of essentially starting from scratch, albeit with the knowledge of having once run 5×1600 with 6:20 splits and a half marathon PR of 1:41.

“Frustrating” is putting it kindly. So when someone expresses their own frustration with running, or dreads going out for a run, or drops it entirely for these reasons, I totally get it.

But if you manage to catch a glimpse of light at the other end, a whiff of progress out of the seemingly-endless grind, it is beautiful.

With very few exceptions, my running the last several months has been consistent down to the week: mid-20s’ worth of mileage.

screen-shot-2016-10-18-at-12-06-18-pm

It’s just that so little of it was actually fun. That the majority was during the absolutely horrific summer we suffered through this year probably didn’t help much, but an enjoyable run in this stretch was the exception, not the rule.

Sheer determination to hit 20+ miles each week, seeing how many weeks in a row I could do it, and stubborn refusal to give up on it were just about the only reasons I kept going out every day. That, and trying to keep my endorphin levels as high as possible with the stress of work. If I wasn’t running, I wasn’t working out, period. And I needed to work out.

So I kept running. But it wasn’t confidence-inspiring; if anything, it did the opposite. When almost every run hurt, my already-dim view of my own abilities only drooped further. It probably doesn’t come as much surprise, then, that when Ath Half rolled around, I was just hoping not to thoroughly embarrass myself.

<Aside>

You can argue that one’s finishing time ultimately doesn’t matter. And you’d be 100% correct! The problem is, once you actually hit the road, that just doesn’t matter anymore. The fact that I haven’t run a half marathon in over 2 hours since 2010 weighed heavily on me as I considered possibly exceeding 2 hours in this race, given how miserable my runs had been.

I was telling everyone ahead of Ath Half that I just wanted to come in under 2 hours.

</Aside>

Truthfully–as runners do–I had in the back of my mind that I wanted to come in under 1:55, since my 2015 Ath Half time was somewhere around low-1:54. C’mon, I thought: at least make a run at last year’s time, right?

But I had absolutely no gauge for what I could do. The last half marathon I’d run in recent memory was the brutal downhill Scream Half, where I posted a respectable 1:53, but the insane elevation change obviated any possibility of comparison. Plus, that was all the way back in June. I had no barometer against which to infer my limits.

And, because the aforementioned summer sucked so freaking much, I wasn’t putting much stock in my abilities. Hence, sub-2 sounded like a treat to me.

Enter race day.

14523070_10106070238844540_418103367267214522_n

Up and at ’em, rise and shine!

One of our running buddies, Jonathan, was the 1:40 pacer. A bunch of ladies on the Fleet Feet running team were going to hang with him. Going in, I figured I’d stick with the group for the first mile for the lulz, then just coast the rest of the way to the finish. An eclectic plan for sure; it also betrayed just how not-seriously I was taking this race.

(and belied how much I was dreading it)

Still, the weather was quite a bit nicer from Ath Half 2015. That year, it was muggy as hell, and I suffered quite a bit as a result. But while the more pleasant weather was certainly welcome, it did nothing to assuage the dark recesses of my mind worrying about the hills on the back half of the course. They’d be there no matter how nice the weather was.

Thus began the race.

It was clear within the first couple of blocks that I wasn’t going to stick with the 1:40 group; I let them go pretty quickly after the start. Still, I knew I was being pulled along at a decent clip by all the folks around me, so I focused on slowing down.

8:06

Cool! But too fast, let’s try to draw it back a little.

8:01

Wow, that’s neat. But still too fast. Pull back on the throttle.

8:02

Hmm. Is the throttle busted?

7:58, 8:02

Yeah: first 5 miles of the race in 40 minutes flat. I was not expecting that. But at the same time, I knew it was the flattest 5 miles I’d get, so I really, really needed to slow down, no seriously guys, for real, time to slow down.

Somewhere around this time, I caught up to The Lady, who’d fallen off the 1:40 group. I walked alongside her for a bit, checking in and making sure she was ok. I was also confident at this point that I no longer had to worry about living through my WORST NIGHTMARE of coming in over 2 hours (by my math, would’ve had to run 10-minute miles for the remaining distance for this to be a problem).

Turns out, we weren’t far from the next water stop, at which point The Lady stopped there for a bit to collect herself, and I started back up running again. I could feel that my legs were definitely getting heavy, and we’d only just started with the hills. Welp, I figured, I wasn’t going to set any landspeed records anyway. Let’s just see what happens.

I was mentally kicking myself at every mile, as I kept watch-hawking. I couldn’t seem to help myself; I was going by feel, but at the same time felt an overwhelming need to check the distance, check my splits, blah blah blah. I knew it was mental, that my mind wasn’t the honed, sharpened, hardened diamond it had once been, and as a result I was doing things and engaging in habits that were counter-productive in a race environment. But the discipline just wasn’t there. I tried to shake it off and just keep on going.

9:24

Yep, definitely slowing down (though I did walk this mile…).

7:54

Huh, apparently not.

8:23

This is where it started getting hard: the hills kept coming and my mental game wasn’t improving. Turning down some extremely rolling terrain, I tried to focus entirely on the relief I still felt that it was nigh-impossible at this point to finish in over 2 hours.

Still, that damn hill coming out of River Rd is effing brutal. I used the water stop there as an excuse to stop and re-tie my right shoe, which had become loose enough that it was becoming a distraction. I recalled at the starting line it had crossed my mind to double-knot my shoes, then something shiny must’ve come along. Go me.

8:54, 8:47

At this point I was coming into the home stretch where we loop around the stadium a few times. It’s both electrifying (lots of cheering sections) and deflating (so close to the finish for so long). I was still allowing myself to slow considerably on uphills; I’d like to say it was because I was refusing to walk at any point, but really it was because I was just mentally lazy and knew that I’d come in under 2 hours, so who cares about shaving off a few seconds on this hill.

Then I finally did the math–wait, I’m less than a mile out and barely into the 1:40s? I CAN BREAK 1:50?!

!!!

8:30

I tried to kick, I honestly did. My legs were burning pretty good at this point, and my chest felt like it was being compressed by an anvil, but for once in the entire race I managed to push my mental laziness aside and give it everything I had left–an average 6:43 pace.

1:48:52

I couldn’t believe it.

I just finished Ath Half–ATH HALF–not only faster than last year, but under 1:49!

For comparison, here’s the mile-by-mile breakdowns of Ath Half 2016 versus last year:

One hell of an improvement!

This is not to say I’M BACK B#^*%ES. I still have a ton of work to do. My cadence fell off considerably, especially in the last few miles. Given my foot issues from the last year, cadence is the one thing that I absolutely cannot slack on; it needs to stay above 160, preferably around 170.

Speaking of slacking, my mental game is a joke. I had absolutely zero capacity to settle in, let the world around me disappear, and just let go and go. I kept glancing at my watch at least a couple of times each mile, I kept oscillating between worry about the next hill and worry about embarrassing myself. And I had no ability to push myself in the last few miles, instead getting lazy and just slowing down, even though I clearly still had gas left in the tank. Speedwork and tempo runs will help with this, though.

And hills–in a not-so-distant previous life, a source of strength and motivation–have become borderline intimidating. That’s a little worrisome; downhills have always been hard for me, but it’s helped that I always got a boost out of uphills, even if it was only psychological.

But! Yes, there is, in fact, a “but.”

There’s a core here worth building on. Something has clearly been clicking for the past several months, to the point where I could run a sub-1:50 under less-than-ideal conditions; my previous sub-1:50 performance was at last year’s Chickamauga Battlefield half marathon. Absolutely perfect conditions–extremely gentle hills, near-freezing temperatures, and perfectly sunny–and it was still a squeaker: I came in somewhere around 1:49:57, and only after redlining the last two miles to do it.

I had time to spare this year, on a much harder course. Time that, of all things, I spent being mentally lazy on the final climbs. Had I really pushed myself that last 5K, who knows how much room under 1:50 I would’ve had.

I’ve been telling people how this past year has basically felt like starting over from zero, except with all the knowledge and experience of “I used to be able to do this…”, which has made it so easy to be so hard on myself. It’s been true in a big sense: I’ve had to accept limitations I haven’t experienced since I started running, and at that time I was blissfully unaware of said limitations.

That’s made it hard. Really hard. Which is why I understand if you’ve been in this position and have chosen to walk away and try something else. And who knows: maybe this race was an anomaly and running will go right back to sucking in the near future.

All I know is something clicked at Ath Half, and for something to click in a half marathon, something has to be clicking for weeks before that. Plus, I told The Lady years ago that I would retire when I broke a 1:35 half marathon; can’t stop now that I’m making headway toward that goal again!

Sprinkles Are For Winners!

*waves* I’m not dead yet!

So, first things first. The Lady and I were recently in our old stompin’ grounds–fabulous Pittsburgh–for the Pittsburgh Marathon Relay. We’d formed a team a few months ago with Kim as our fearless leader, a team named “Sprinkles Are For Winners.”

The relay runs the full marathon course, split up over 5 runners who each cover some distance between roughly 4.5 and 6.7 miles. As The Lady and I had never run the full, there was an entire 13.1 miles we’d never run before, so it seemed like a good opportunity to see the full without actually having to run the whole 26.2 miles. And, y’know, see Pittsburgh and the folks there whom we love dearly 🙂

The race itself more or less went off without a hitch, albeit with a few wrinkles with respect to the weather. It was a lot more humid than anticipated due to in-and-out rain (which was also unexpected), and this made things a little tricky, but overall it worked out ok.

We stayed with Kim and her husband Scott in the Pittsburgh suburbs, and managed to absolutely pack our schedule with friend-visiting time. We arrived in Pittsburgh on Friday morning at 9am–yes, arrived at 9am; I’ll let you do the math–and spent the rest of the day meeting up with The Lady’s work buddy Lara, some of my former graduate school colleagues, and dinner with Matt and Maria, before heading to Kim’s for the night.

The next day was more running around. First, we went for a shake-out 3-mile morning run with Kim, Michael, and someone named Octavius or Jonathan or Maximillian or something, and his lovely wife Jill.

ChSyQHkWwAANKWc

Courtesy of Ferdinand. Or was it Randall? (that’s me on the far right)

Following the shake-out, we hit the Expo! Woohoo!

IMG_4939

Always a blast.

At the expo, we once again ran into Ellen, as well as Kelly and her family. Following the expo was a strategy session with Kim, a delicious pre-race dinner with Kim and Scott, and glorious, wonderful sleep.

The relay itself was pretty awesome. Our first runner, Danielle, was also running the entire full, so once she handed off to our second runner Shay she just kept going. I was the intrepid third runner, stationed around mile 10 of the course. I was excited to run my leg, as it started near where the half and full races diverged, so I’d briefly get to see some familiar sights before stepping off onto a course I’d never run before.

Of course, the elevation of my leg was…interesting.

Yeah.

I went out feeling fairly good, and climbing Birmingham Bridge wasn’t too much of a problem, but there was this offramp that took us onto Forbes…that beat me up pretty good. I was definitely hurting after that.

I didn’t set any landspeed records–8:38 average pace, which for the 10K it essentially was is definitely on the very slow side for me–but I finished intact, handing off to The Lady in Squirrel Hill, right next to Bakery Square.

IMG_4960

Kim saw me around mile 5 and snapped a photo. I was deep in the pain cave at this point, but thanks for the awesome shot!

After The Lady dashed off, I took some time to hang around Bakery Square, get some coffee from the adjacent Coffee Tree Roasters, and generally take things easy before hopping back on one of the convenient relay buses that took me back downtown for the finish.

Soon enough, The Lady handed off to our anchor and fearless leader Kim, and The Lady and I managed to meet up at the finish with [almost!] our whole team.

IMG_4955

4/5 (runners 1, 3, 4, and 5) of team Sprinkles Are For Winners!

We hit up Burgatory afterwards for some glorious burgers and spiked shakes before getting cleaned up and hitting the road back to good ol’ Athens.

It was a really fun race weekend. Exhausting for sure–we spent the next week trying desperately to catch up on sleep. But not only did we once again have the privilege of running through the city we’d fallen in love with, but we got to see a large number of the people who made the city so special to begin with. We don’t see them nearly often enough and it was great to catch up doing the very thing that effectively introduced us to each other all those years ago.

As a bonus, the Danimal and Sarah were in town, too! They both ran the half marathon–Sarah’s first ever! They joined us for post-race celebrations at Burgatory, and a wonderful time was had by all.

There’s more to be said–lots more–but I wanted to go ahead and reassure the MASSES WHO READ MY BLOG (lolololol) that I’m still alive, still running, and especially in this case, still having a lot of fun 🙂

 

It’s the journey, not the injury

Like I mentioned in my previous post, the longer I’m out due to injury, the more I’m convinced this will ultimately be a good thing for my running psyche.

Allow me to explain using two races I ran in the last weeks as Exhibits A and B, respectively.

Sunday, Sept 27: Pittsburgh Great Race 10K

Yes, ladies and gentlemen, The Lady and I returned to the city we are still as madly in love with as ever (disclaimer: we really and truly do love Athens and the wonderful people we’ve met; doesn’t mean we don’t still miss Pittsburgh, too) for a wedding: Kim and Scott (go ham)!

It was a beautiful ceremony, and so very Them. It took place at North Park, an exceptionally picturesque park that’s far enough outside the main Pittsburgh area that deer are a regular sighting (also host to such events as the Frigid Five Miler, Spring Thaw, and Just A Short Run). The ceremony itself was intimate–maybe 70 people in attendance–and took place under a pavilion on a day that God Himself was probably proud of: mid-60s, a gentle breeze, low humidity, and barely a cloud in the sky. It was, in every possible way, perfect.

But it just so happened their wedding coincided with the Great Race, Pittsburgh’s annual 10K that has as much personality as the city that hosts it. We couldn’t pass up the chance. Even with my injury, I felt my foot could handle 6.2 miles, and with all the cycling I’d been doing felt confident my cardiovascular system could keep up.

I went into the event knowing I wouldn’t be setting any PRs; in fact, I wasn’t going to try, not even for anything close. The Lady had to use the race as a training event and stick like glue to her goal marathon pace (8:12 min/mi), and I felt like sticking with her would be plenty given my complete lack of running mileage the past month.

<3

So that’s precisely what I did. I soaked in the sights and sounds to a level I rarely ever have at this event (been too busy in previous years gunning for a PR), and all the while felt great. I wasn’t officially pacing for The Lady, but I also had to be careful: I noticed I would keep speeding up to a sub-8 pace without realizing. Come mile 5 and the infamous Boulevard of the Allies climb, The Lady said I was more than welcome to take off if I was feeling good; she would stick to her own pace.

I pushed an 8-minute mile 5 (nothing spectacular), a 6:45 mile 6 (not too shabby!), and a 6:23-pace last quarter-mile before crossing the finish line at 48:41. Definitely not a PR (almost exactly 6 minutes long), but I’d had a blast and felt great the entire time. I was truly on Cloud 9.

Yeah, I was definitely sore the next week: muscles I hadn’t used in almost a month had suddenly been called upon to run a hilly race at a reasonable clip. My lungs, quads, and hamstrings were more than up to the task, but all those little stabilizing muscles had a serious case of WTF M8. Furthermore, my foot was pretty pissed at me the rest of Sunday; while it felt great during the race, it tightened up very quickly afterwards, so I made the decision that I would skip the next weekend’s half marathon in Atlanta and resume healing.

Sunday, Oct 4: Michelob ULTRA 13.1 Atlanta

…at least, that was the plan. Until I recalled that The Lady and I had signed up for the ATL Challenge and had already completed the first of the two required races back in March. I wanted that medal, dammit!

Of course, if it was just the medal, I would have been disappointed but not enough to switch strategies. I noticed that come Monday (24 hours later), my foot was feeling better. As in, better than before I’d run the Great Race. So I started aggressively icing each night after work while making plans for completing the ATL Challenge.

Like the Great Race, I had no plans to attempt a PR. 100 miles of cycling each week, while certainly more than sufficient to maintain a baseline level of cardiovascular fitness, does not for a long-distance PR prepare one. But I was still nonetheless confident my fitness level could carry me through the race standing up.

Come race morning, me and the 7.2 miles I’d run in the last month (Great Race, plus a 1-miler on Sept 4, the only other time I’d run) lined up at the starting line, with the lofty goal of a sub-1:50. The Lady, meanwhile, was using the race as a training tune-up: she had her coach’s blessing to open up the throttles and see what she could do. With that, The Lady took off at the start, while I settled into something that felt comfortable.

A few things I very quickly realized within the first three miles:

  • This humidity was going to be a problem: I’d drained 2/3 of my handheld within the first few miles and my body temps were still skyrocketing.
  • A sub-1:50 wasn’t going to happen; 8:24 min/mi just didn’t feel comfortable, and I had no intention of feeling uncomfortable within the first few miles of a race that was effectively doubling in one morning my entire running mileage for the last month.
  • Holy. Hills. Batman.

Really, that list could be condensed into just the third point (with the side addendum: there were 11 aid stations advertised on the event website, but only 5 on the actual course). The hills were brutal. They were fast elevation changes that zipped up and down, leaving the runners very little on which to build some momentum before shifting yet again.

Michelob ULTRA elevation chart.

Michelob ULTRA elevation chart.

…and yet, I felt strong. I felt focused, alert, and in control. I wasn’t breaking any speed records, but I was consistently staying within the 8:30-8:45 range every mile, regardless of terrain; in fact, only mile 3 broke 9 minutes (9:07); the rest were below 9, often solidly so. Helping even more was a steady, misting rain that started around mile 5: it perfectly countered my rising body temperatures and kept them stable through the rest of the race, allowing me to preserve what was left in my handheld water bottle in case of emergency.

I kept cruising, feeling strong, taking the hills at a slow-but-steady pace and chewing up the miles. I high-fived The Lady a few times as we passed each other on out-and-backs, cheering her on. The only hiccup was around mile 9, when I discovered my calves were really hurting but I couldn’t figure out why.

And then it dawned on me: I haven’t been running, so my calves weren’t used to absorbing the shock from my midfoot-to-forefoot strikes, and the Great Race was too short for this problem to surface. Cycling is great for your quads and hamstrings, but doesn’t do a whole lot for your calves. The last couple downhills I had to switch to heel-striking to give my calves and ankles a break, but I made a mental note to start mixing some calf work into my workouts.

I crossed the finish line at 1:53:10, again setting no speed records but nonetheless giving me an immensely satisfying finish, especially considering 1) the humidity, 2) the lack of aid stations, 3) the omg-hills, and 4) my complete lack of running mileage.

Also got my hands on this supaswank challenge medal (in addition to the regular finisher’s medal [not pictured]):

13.1 from the Georgia Half Marathon, and another 13.1 from the Michelob half.

13.1 from the Georgia Half Marathon, and another 13.1 from the Michelob half.

Again, I’d felt great throughout the race. The hills were brutal but I never stopped having fun. The pace was a good workout but it still felt comfortable, giving me a huge psychological boost toward keeping doing what I’m doing while making me all the more antsy to get back to running full-time. My foot was somewhat pissed the rest of the day, but I’m waiting to see if it does the same as before and feels better following the initial 24 hours post-race.

Conclusion

Technically, I’m still injured. My foot definitely still hurts when I walk, some days worse than others. I’m still not going to run on it during the week (dooming myself to miss even more group runs with Fleet Feet and Athens Road Runners), and I’m going to keep hitting the bike as much as I can to maintain my cardio fitness.

But I’m cautiously optimistic that my foot is–slowly–healing. I’m thrilled that I can still race and hit certain milestones. And I’m stoked that I enjoyed those races as much as I did, that I’m chomping at the bit to get back into running form. I miss running. And I like that I miss it.

I needed this break from running, without a doubt. Now I want to do everything I can to get back into it.

Race Report: The Hilliest Marathon Evar

Upside of running a marathon on the opposite coast: it basically forces you to take a vacation, unless you really want to fly back within 24 hours of touching down (not this guy).

Downside of running a marathon on the opposite coast: holy 500 unread emails, batman.

BUT ANYWHO. BIG SUR!

West coast best coast?

West coast best coast?

This whole trip was a very interesting logistical ballet. While the race was on a Sunday, we flew into SFO on the previous Thursday, giving us a few entire days to get settled beforehand. Afterwards, we left on that Tuesday, giving us yet another day after the fact to stretch our aching legs and tour around before cramming back into a tiny metal tube flying at 35,000 feet for several hours.

It turned out to be a brilliant plan.

Thursday, Friday, Saturday: Pre-race

She is SO EXCITED for the 6-hour plane ride.

She is SO EXCITED for the 6-hour plane ride.

The flight was long, but uneventful. The wild card, I noticed in class I was teaching the previous day, was a tickle in the back of my throat that, historically, signaled the onset of a head cold. With hardly 72 hours to go before a marathon, I was more than a little worried that this could be problematic. So we tried to accommodate by making sure we got plenty of sleep and fluids.

That first evening, we stayed in a hotel right next to the airport. Pretty much rolled out of the plane and into bed.

Friday morning, we rented a car and drove the ~2 hours from San Francisco to Monterey.

It's a surprisingly long drive, especially if you're still a little jet-lagged.

It’s a surprisingly long drive, especially if you’re still a little jet-lagged.

The plan was to arrive by lunch time, both so we could get to the Expo in plenty of time, and so we could meet up with friends of ours from Pittsburgh who were also running–Danielle (The Lady’s running buddy!), and her husband Jose (who ended up not running). We met them for lunch at a nearby crepe restaurant (omnomnom) which, not at all coincidentally, was a block away from the Expo.

We picked up our bibs, bought a bunch of really cool swag–they had some awesome stuff there!–got all the information we needed on the buses that would drive us to the starting line at oh-God-o-clock the next morning, and by the early afternoon we were all wrapped up!

Danielle and Jose wanted to spend the rest of the day in San Francisco, but since The Lady and I had just come back from there we were loathe to make that drive two more times in the same day. Instead, we planned to meet up the next morning before parting ways; The Lady and I made our way to our hotel further up the road, which turned out to be a lovely inn about two blocks away from Cannery Row. So we took the opportunity to do a little bit of sight-seeing!

It was nice to get out and about, particularly since we knew we’d be spending all of the next day lounging, giving our legs as much rest as possible before the marathon.

Not too much rest, though–that Saturday morning was a group shake-out run with several Runner’s World reps, including none other than Bart Yasso!

You're jelly.

You’re jelly.

Fun fact: we actually got to meet him before the Pittsburgh marathon a few years back, but this was the first time we really got to run and chat with him. Wonderful guy with boundless energy who thrives on meeting new people, especially runners.

After the shake-out, we went back to our hotel, got cleaned up, and lounged the rest of the day. Bedtime was early, as wake-up was super early: around 3am.

Sunday: Race Day!

At this point, nearly two months out from the race, I honestly don’t remember how early it was that we woke up. But I do know the buses left sometime in the 3am range, so it was early. The bus ride itself was a good 45-60 minutes over Highway 1; very rolling. I somewhat dozed in and out; it was still pitch black out, so it’s not like I could really enjoy the scenery anyway.

We arrived at the starting line–seeming civilization in the middle of nowhere. Fortuitously enough, we encountered Danielle, and huddled together until the sun came up.

The start was right around 7am. The sun had only just started coming up an hour before, and the landscape as it came into view was, simply, breathtaking.

We had a few minutes to warm up (darting between runners) and generally attempt to shake out the butterflies, but soon enough, the starting time arrived. After a few announcements, the race director wished us good luck…and we were off!

Miles 1-5

The whole course was beautiful, but the first few miles almost felt like I was alone on the western coast of the United States. It was absolutely beautiful; there were giant trees to both sides of the road, killing the wind but also keeping out the rapidly rising sun. There were almost no crowds to speak of; the occasional house or lodge we passed by might’ve had a handful of people outside watching us go by, but other than that it was just the quiet pitter-pat of running feet punctuated by the occasional conversation between runners.

I loved it. Really helped me settle in, mentally. Plus I’m just kind of a nature freak: being by myself out in the great quiet embrace of Mother Nature is incredibly calming and soothing.

The road itself was, as advertised, rolling. The first 5 miles were a net downhill of 250ft, but there were certainly uphills as well as downhills on the winding road. We kept a fairly consistent sub-9 pace: 8:52, 8:40, 8:38, 8:44, 8:51.

Miles 5-10

With the exception of the last mile of this stretch, it was a significant net uphill. Gone were the cover of the trees; we had emerged along the California coastline, and the wind made its presence felt. It was absolutely beautiful; we could see the waves crashing on one side, and on the other the rolling hills complete with grazing cattle (we could even hear them; we imagined they were cheering us on). The Lady in particular recalled how there was a solid 2-mile steady climb during this stretch, where you could see the entire two miles; the road was a straight shot the whole way. Perhaps somewhat surprisingly, I felt pretty good. I had settled in nicely, and while our pace had slowed due to the climbs, I was enjoying myself.

Given that we weren’t aiming for any particular time goal, we stopped a couple of times to take pictures of the scenery.

We stayed solidly in mid-9s territory: 9:04, 9:03, 10:08, 9:25, 9:48.

Miles 10-15

Ok. Here’s where things got interesting. I’ll show you, and then describe it to you. Here’s the elevation chart as compiled by Strava from my GPS data of the race.

Screen Shot 2015-06-17 at 11.55.49 AM

That spike in the middle, ladies and gentlemen, is known as Hurricane Point, and this elevation chart isn’t exaggerating: it is indeed a straight climb for two miles, during which you ascend just about 500ft. It’s not rolling; it is, quite literally, a straight climb. Mile 10 is the worst–you gain over 300 of the total 500ft in just that one mile.

Thankfully, I had my game face on and chugged up the hill, feeling surprisingly good the whole time. The Lady stuck right with me, too.

Upon reaching the top of the hill, we thought about stopping for another photo op, but the wind up there was crazy. I don’t know how strong it actually was, but I do know that, in the small amount of time that my foot was off the ground when I’d lift it to take another step, the wind would blast it sideways. My bib rippled, crackling loud enough to make me worry it would get blown off. So we kept moving.

We got a bit of a reprieve with a fairly lengthy downhill. At precisely the 13.1 mile mark, we reached the famous Bixby Creek Bridge. Of course we stopped to take a few photos.

And yes, as per Big Sur tradition, there was a pianist on a grand piano here. Absolutely delightful.

Despite Hurricane Point, we still made pretty good time on this stretch, keeping our mid-9s pacing on average: 9:48, 10:28, 9:53, 8:46, 9:54.

Miles 15-20

We were still cruising pretty well. I was definitely feeling the fatigue creeping in, but I still felt strong. However, for whatever reason, my GI tract decided to stage a revolt at this point. At mile 16 I had to make an unscheduled pit stop (The Lady had made one several miles ago; we were making excellent time so far, given our frequent photo stops, pit stops, and the general hilly course), after which I felt immensely better. Hashtag runner problems.

This was also where the course started deviating more inland, away from the coast. Kind of sad, though it did mean the wind eased up a bit. However, the sun was starting to get pretty warm, and while we did move further inland, there wasn’t a corresponding increase in tree cover. Instead, the surrounding area seemed to turn into farmland. The shade was a bit spotty.

Still we pressed on at a pretty decent clip: 14:13 (pit stop), 9:33, 9:42, 9:46, 9:47.

Miles 20-25

You know “The Wall” that runners talk about, and the concept of “hitting” it? That’s pretty much what happened to me at mile 20. One minute I was fine, the next minute, I really, really wasn’t.

I call this maneuver the

I call this maneuver the “Final 10K Shuffle-Step”.

I wish I could say it got better, but it really didn’t. While this probably would have happened anyway, my sneaking suspicion is the head cold I mentioned at the beginning hit full force here. Marathons put a ton of stress on your body, and one of the ways that stress manifests is by shredding your immune system. Most of the time this isn’t too much of a problem, but if you’re already getting sick, running a marathon will kick the disease into overdrive.

I was having a hard time breathing without launching into coughing fits that had me doubled over. My legs wouldn’t cooperate. It was painful.

The Lady, incredibly, was hitting a stride. Where I evidently kept her in the game for the first part of the marathon, she was the single reason I kept pushing forward past the 20-mile mark. 11:29, 11:31, 10:57, 12:38, 10:55.

Final mile

I had an amusing revelation the day after Big Sur. We ended up driving by the finish line to meet up with Danielle and her husband before they left town. I recognized the finish, remembering the tents and the people cheering us those final agonizing miles. But as we drove past the finish line and into where miles 25 and 26 had been, I startled to realize:

I had no recollection of it whatsoever. Even on the drive back, when we were driving in the exact same direction along the course that we’d run–towards the finish–I couldn’t place the surroundings. They were completely unfamiliar to me.

That’s to illustrate that, while I don’t remember the course in that final 1.2-mile stretch, I vividly remember the pain I was in. Again, if not for The Lady’s gentle but constant encouragement, I don’t know how I would have dragged myself across the finish line.

Finishing time: 4:26:11 (according to the official Big Sur finisher’s book)

The immediate aftermath was painful. The lead in my legs began to set almost immediately after I stopped running, and it hurt. A lot. I think The Lady was honestly worried there was something wrong with me aside from the whole “just ran a marathon” thing. It took the better part of the ride back on the bus before the pain in my legs began subsiding.

We went back to the hotels, cleaned up, and rested. My legs, while completely beat, were functioning semi-normally by that evening. I couldn’t yet tell how bad my head cold was going to be; given how badly I knew I’d just trashed my immune system, I imagined the virus would be rampaging through my body virtually unchecked for the better part of the next 24 hours.

(turns out, that was prescient: it took about that time before things really got bad)

By that evening we were both feeling decently well rested–and HUNGRY–so we took a short walk to a nearby burger joint. It turned out to be perfect.

Photo Apr 26, 20 49 48

It was very much a local mom-and-pop establishment. We were even treated to a group of retired folks who had organized themselves into something of an orchestra, conducting a regular practice session in the middle of the restaurant. So not only did we have a warm, inviting atmosphere in which to chow down on burgers & fries, but music from adorable retirees as well. It was perfect.

We slept well that night.

Monday, Tuesday: Post-race

It turned out to be a brilliant decision on our part to sacrifice two work days for the purpose of easing ourselves back into civilization. It gave us time actually enjoy traveling.

Since our hotel was all of a few blocks from Cannery Row–and therefore the beach and the Monterey Aquarium–we spent plenty of time checking out both. It was a convenient way to stretch out our legs a bit, and let’s face: beaches and aquariums are awesome. We had a lovely time.

Monday late afternoon, we said goodbye to Monterey and road tripped back into San Francisco to spend the night with my college-friend-turned-badass-Bay-Area-developer Amanda and her roommate. We don’t get to see each other very often anymore–what with living on opposite coasts and all–so it was a treat to be able to hang out with her for a night and catch up.

Oh, and we got along just fine with her apartment’s third, and furry, inhabitant.

Meet Jake the Cuddle Monster. He will cuddle you to death.

Meet Jake the Cuddle Monster. He will cuddle you to death.

Come Tuesday morning, as Amanda was departing for work, we packed up as well, said our goodbyes, and headed for the airport and home.

Epilogue

This was one of the most bipolar marathon training sessions I can remember. Granted, I’ve only been through all of three (I guess, technically, four? I ran the 2014 AF half but trained as though it was the full) so I’m not exactly working with a large sample; each training session is likely to have its own “first”s and “most”s for a few more yet to come. But the move to Athens can’t be discounted entirely, either; we were here all of two months before we started training. Kind of hard to imagine there wouldn’t be some bumps in that particular road.

Also, I was coming down with a head cold four days before the race. And as predicted, about 48 hours after the race, my immune system had recovered enough to discover that my body was saturated with whatever virus it was and flipped every alarm switch to DEFCON 1. tl;dr I was the most miserable wreck all of Tuesday for the drive to the airport and the flight home, what with a runny nose, splitting headache (that ibuprofen didn’t even put a dent in), and general lethargy. In that light, it’s kind of amazing that broke down at mile 20 as opposed to, y’know, mile 1.

All that aside, it’s still tough for me to shake the disappointment with what appeared to be a second consecutive 20-mile breakdown. At both Marine Corps and now Big Sur, mile 20 has been a wall that has thus far been insurmountable; I’m rolling, until that crucial final 10K where the wheels abruptly fall off.

And yet…there’s this neat feature on Strava where it attempts to intelligently discern how much of your workout you actually spent in motion. Since I don’t stop my watch during races (why would you?), it had the data to come up with a guess of what my time would’ve been minus the 2 bathroom breaks and 3 photo ops. Any guesses?

A 9:47 min/mi pace (for reference, my average pace for my official time was 10:10 min/mi). Any idea what my current marathon PR pace is? 9:47 min/mi.

So discounting the bathroom stops and photo ops, I ran Big Sur–in all its crazy elevation changes, with a head cold, and after a relatively subpar training cycle–at the same pace as my PR.

That gives me a glimmer of optimism. It also means it’s time to get back to work.