Battle of Sedgemoor 10k: race report

In many ways, my last five months have been spent gearing up for this race. I didn't necessarily have a specific training plan laid out for it, but this was my focus race. During that time, I raced four other 10k events, and set two new PBs, inching my best time down from 47:25 to 47:00 to 46:40. But the Battle of Sedgemoor is known as a PB course, and I had my sights set on a significant new record: sub 45 minutes. Of my three resolutions for 2014, this was the only one I hadn't yet achieved.

Things started badly: a month or so ago I re-sprained my right ankle playing football, and I still haven't completely shaken the niggles off. A fortnight before the race, I hurt my left foot on a tempo run. Neither was particularly major, but between them they caused me to severely drop off my mileage in the couple of weeks before the race. I even considered taking painkillers for the race itself, but decided that I really didn't want to start down that road.

Onto race day: despite being my fifth 10k of the year, this race represented something new for me. This was the first time I would truly be racing as part of my club. Although I had done two other races since joining, there were no other club members at those races, so I was still on my own. This race had a new feel: at 9:30 we were meeting up in Taunton, to head over to Langport in convoy. This meant that at about 9:15 I had to frantically go to the petrol station to make sure I could make it to Langport!

Still, it wasn't that different: park, find race number, pin race number on, idle around, have club photo taken (okay, that was a bit different), wander over for pre-race briefing, head to start line.

So... I have a tree growing out of my head... (Photo: M. Lomax)

At the start line, disaster two struck. (To recap, disaster one was a couple of foot injuries.) Disaster two had the potential to be much, much worse. My Garmin simply would not find any GPS. This was an issue: on the back of my hand I had written pacing notes, but they would mean nothing if it didn't get some satellite signal. It's safe to say I was in a bit of a panic. Thankfully, another member of the club, Andy, was also aiming for 45 minutes, and another wasn't far behind, so I was able to initially judge my pacing off theirs to an extent.

I'd looked at the course profile before the race, and knew that the first mile to mile and a half of the race was a gentle climb. My plan had been to take this gently and then push on, but with no pacing data, I think the first kilometre was at sub 7 minute miles, and the second not much slower. Finally, about 2.5 km into the race, my Garmin started! It was useless as a stopwatch, but it allowed me to keep an eye on my pacing. I was still running with Andy, though typically one or the other of us was a few paces ahead. At the 4 km marker, I asked for a time check: 17:30: about 30 seconds quicker than I needed to be for 45 minutes. And looking at my pacing, I was still running quicker than I needed. I figured I was either doing pretty well, or was about to crash and burn.

At 4.5 km was the first drinks station: I took a plastic cup, just about managed to avoid spilling the whole thing. I then took a tiny sip, more to wet my mouth than actually drink anything, and dunked my hand into the water so I could splash my face. The next drinks station came up far too soon afterwards, at around 6 km, and I opted not to take another drink; a decision apparently shared by more or less everyone around me, as we all arrowed straight through the middle of the offering arms.

It was around this stage that I started to pull away from Andy; I knew that I was still running ahead of my target pace, and I was still a little worried about that, but I felt good, and let myself be dragged along by the other runners around me.

I must admit, I had forgotten about the incline at 7.5 km. I certainly wish the course had forgotten about it too: that hurt. Still, it is a fact that on a course that finishes more or less where it starts, any ups have corresponding downs, and the last kilometre was mostly downs. Although I hadn't had a real time-check since the 4 km mark, I knew my pace had been good since, and I could cruise the last kilometre, but on the other hand, I was still feeling pretty good, so I notched the pace up a little, which brought me close to the chap in front as I approached the finish funnel. Always one for a bit of a fast finish, I pushed to pass him through the funnel: unfortunately the cheering crowd let him know what was happening, and so he sped up. I ended up in a flat sprint; perhaps not the most sensible thing, but brilliant fun! I pipped him to the line (though our times were identical).

In all the excitement, I hadn't actually looked at the finishing clock: having crossed the line and been handed my medal, I'd found a spot in which I didn't think anyone would mind too much if I threw up (I didn't, as it turned out) and then got a cup of water. By the time I glanced back, it showed 44:05. I'd done it!

Looking at this, it's possible that the other chap didn't put quite
as much effort into his finish as I did. (Photo: M. Lomax)

I returned to the finish line in time to see Andy come through in just under 45 minutes, which meant that I didn't have to feel guilty about possibly dragging him along too quickly at the start! From there, our club runners came through regularly, and set a dizzying array of PBs.

As the photo shows, my time was actually sub-44: 43:44 in fact, almost a three minute improvement on my previous 10k best, and significantly quicker than I was aiming for. Maybe running without any pacing information at all for those first 2.5 km, and then only limited information helped me: I've suspected for a while that the mental aspect of "But I can't run that fast!" when I look at my pacing might have been holding me back. Recently Sarah (@littlerunnergal) posted, or at least re-tweeted, something about running "naked", and maybe there is some benefit in it. That said, I'm still planning on taking my Garmin along to my next race.

Shiny medal!

But for now, there are four months of the year left, and I've achieved all of my targets for the year already. Should I relax a bit and just run for the fun of it, or should I set new targets and go about hitting them?

Distance vs. Speed

In what is quite possibly the most eagerly anticipated contest since the 2009 release of Monsters vs. Aliens, I have been considering the pros and cons of trying to run quickly against trying to run further. Although there is an element of general musing about the question, it is also key to planning out my targets for next year. If what I actually want to do is run really quickly, a marathon probably isn't the best plan.

First, a little background: I did my first half-marathon in March this year, and am running my second one in October. Other than that all of my races have been at the 10k distance. Before this year, I'd only passed 10 km a handful of times in training runs - including one 10 mile run which crocked me and stopped me running for the next four months.

Me halfway around my fastest parkrun.

My fastest time is currently from Longrun Meadow parkrun, 21:06. Based on this a few formulas tell me that I should be able to run roughly a 1:37:00 half-marathon. My target time in October is 1:45:00: if I achieve that, the corresponding 5k time would be about 22:50. I understand the differences:

• I've run over 30 parkruns, and do so most weeks, while I've only done the one half-marathon.
• All of my runs are 5 km or more, whereas I've never trained over 13.1 miles.
• The predictions are completely different stages of development: parkrun has honed my 5k PB, I'm still learning about HM pacing.

On Twitter, the majority of the @UKRunChat community are aiming to run further and further: lots are signed up for the Brighton Marathon, which I think is the first (and possibly last) marathon for many, while plenty of others are looking at ultras. This has created a lot of peer pressure (not necessarily negatively) to push myself to run further too. To this end, I pencilled the Robin Hood Marathon into my 2015 calendar, despite the fact that I never really planned on running a marathon quite yet.

The thing is, as I've mentioned before, I love running fast. Running for ages? Not so much. So, I'm coming to the conclusion that for next year at least, I might enjoy my running more if I just continue to focus on shorter distances, with a few half-marathons thrown in. To reflect this, my training would have much more speed-work: threshold runs, intervals, and any "junk mile" runs would involve fartleks. Hill sprints are difficult in Taunton, although there's a few places I can go to run them, it's just a matter of getting there!

All that said, I'm not completely decided yet: is this just an element of laziness or nervousness about stepping up my distances? I think that it's just making sure then when I do step up I'm prepared and confident at the shorter stuff. I figure that marathon runners peak later in life, so while I'm still (sort of) young I can focus on running as fast as I ruddy can. I'm even considering running on a track, perhaps not racing though; I've seen @runmapporun's times, and they scare me!

As you might be able to tell though, I'm still a little unsure about it all: part of me says I can do both, but getting the balance of speed and distance, while maintaining a sensible run/life balance seems a bit too much manage.

What are your goals at the moment: speed, distance, or both?

What advice can you offer me, what has worked for you?