A race report catch-up: part one

So, it would be fair to say that I’ve got out of the habit of updating the blog with my race reports. Well, to be honest, I’ve just stopped writing pretty much anything on it. Which is annoying, as reading my blog reports from previous years is one of my most effective pre-race preparations. This year I’ve raced 11 times, and yet I’ve only put up 4 race reports. Now two of those were Yeovilton 5k races, which I don’t tend to write up properly, but that still leaves five whole races unrecorded.

With this in mind, I’m going to try and summarise my thoughts on each, going back over some short notes I made at the time and the Strava report.

Butleigh MT 10k – 19 March

This was another “new to me” Somerset Series race for 2017. It used to be 7 miles, but this year they dropped it down to 10k. Unfortunately, to make it this distance, the race had to loop some fields at the start and end of the course, which wasn’t great – I’m not convinced that it is important enough to make a race 10k that this looping was needed. But whatever.

I probably, definitely started the race too fast on the initial lap of the field, but wanted to make sure I was in a decent position to avoid having to wait to cross the stile out of the field, which became something of a bottleneck for those behind. We then entered another field (there were lots of the them) which was extremely boggy. Everyone was taking different lines, trying to find some firm ground, but there simply wasn’t any. I ended up tight against the fence on the right-hand side, which I’d initially worried was electric, but it turned out not to be!

At the end of this field, the course rose up towards the road, though we didn’t actually run on the road, but through the trees alongside it. This was apparently the local fly-tipping area too, which a range of furniture and tyres on offer. It wasn’t great terrain to run on, but thankfully I was following another runner, so was able to keep track of the track, so to speak. We dropped back downhill into the fields after this section, and were helpfully warned by the marshal “Careful as you go, very slippy.”

Pack running

He was right – I slipped over. Thankfully it was all just mud, so no harm done, and I barely even lost any time on those I could see ahead of me. I picked up the pace a bit down the hill, but a little more cautiously than normal after my fall. After a short stint back on the road, we turned off it again and up hill. I was passed by another Series regular, Graham, (no surprise there) as we climbed up, but I went back past him once we headed downhill again. For most of the last two miles, four of us ran close together, our positions switching around a few times.

Graham’s course knowledge helped a couple of times, but I was leading the group coming into the last mile. Until the bloody “main” road crossing, when I got held up by a car passing, and the group caught back up to me again!

After a few more twists and turns (and the bloody pointless lap of the field) I finished in a reasonable (given the course and conditions) 48:01. More importantly, I was around, or ahead of, those I considered competitors in the Series.

Yeovilton 5k – 10 May

After Butleigh, I had a couple more weeks of good running before illness (a sinus infection) and the arrival of my new son stymied my running for a while. I skipped the April edition of the Yeovilton 5k Series, and returned in May. My hope was for a time around 20:15. Last year I peaked at 19:13 in September, but I was obviously going to be well short of that. Rightly or wrongly (the latter) I headed out at sub-20 minute pace, ticking off 3:56 and 3:58 for the first two kilometres. Then the wheels fell off; 4:12 for the third kilometre followed by 4:25 and 4:22. My body had just given up on me, though I shouldn’t have been surprised. I finished in 20:48, more or less equivalent to my time at this race in May last year, when I ran 20:44. So, if nothing else, I knew I was in roughly the same place, and so could improve back to the same place as last year.

Wambrook Waddle 10k – 14 May

Lani probably had as much fun as I did at this one!

This race came on the Sunday following the Yeovilton race, and so I was feeling a mixture of disheartened by the 5k result, and confident that hopefully if I had more or less matched my 2016 5k performance, I could more or less match my 2016 Waddle performance. Which I guess I more or less did. I opted to follow the Nigel Baker Race Start TacticTM, which I admit probably isn’t the best long-term plan. It essentially involves doing a race with a downhill start, and then absolutely pegging it down the hill. It was great fun. It probably killed my legs. Unsurprisingly, I lost a lot of places on the subsequent uphill, though I had plenty of fun dropping back down it again after.

In essence, this race was categorised by me not really being mentally prepared for racing in the Somerset Series “lower down the pack”. I saw those that I had previously raced around, but they were way ahead of me, and it was difficult to deal with. I probably had a reasonable race considering my fitness levels, but it just felt like a bit of a fail. But if there is anywhere to do that, it’s the Wambrook Waddle, which remains a gem of a course – impossibly hard for a race that is only 10 kilometres long (though in fact, most of the work is done in the first 5k, it’s just that your legs are completely shot for the second half.) Again, my race time was more or less equivalent to what I ran in 2016 (about 20 seconds slower.)

Wells 10k – 28 May

I did actually do a full write-up on this race, which you can find here: Wells 10k: race report. In summary; felt tough, but managed to equal last year’s time.

Crewkerne 10k – 4 June

This was the final of the more or less back-to-back-to-back Somerset Series races, which featured three 10k events in four weeks. This was a return to a race that I last did in 2015, when I found it really, really tough. The race starts with a steep hill climb, then drops down just as steeply, and then undulates until it loops back around to do that hill in reverse once again. When I did this race in 2015, I’d done about 1,800 ft of elevation so far that year. This time, I’d done 17,300 ft. It’s fair to say that I’m a bit better prepared for hills these days. In fact, the whole race only has about 500 ft of climbing, which isn’t unusual for Somerset Series races.

My time of 44:03 was almost identical to my Wells time of 44:02 the week before, and gave me a lot more confidence. For whatever reason, I just felt strong on the hills, and quick on the descents. Sure, I was still a distance back from the pack of runners I felt I should be with – I could see them for most of the first half of the race before they got too far ahead of me. But I’d come to terms with that now, and knew that I was running for myself, and working my way back to where I had been. Even if I wasn’t there yet.

Right, that’s enough for the moment. I’ll follow this up with part two later on; another go at the Red Bull Steeplechase, the Quantock Beast and my second Yeovilton 5k of the year.

Let there be exercise

Starting out exercising is never an easy task. You need to find energy you aren’t used to spending. You need to find time you normally fill in other ways. And, for the vast majority of us, you need to accept that you won’t be very good at it to start with.

I’d made various comments about doing stretches or looking at post-natal exercise videos, but nothing was actually happening. Earmarking time and energy for yourself is not something that comes naturally to many mums with young children. The only thing for it, therefore, was to book myself onto a class where the time was committed and it would be harder to back out at the last minute.

Next decision – what sort of class to go for? Specific post-natal classes have the benefit of everything being tailored to what I currently need, and with specialist knowledge of potential issues. On the other hand, the buggy fitness class I’d done last time round no longer exists, and I also needed something in my week to be about me and not about being a mum. The ideal situation would be if the instructor at my favourite friendly exercise studio had completed her pre- and post-natal exercise instruction course. Which she has. Love it when a plan comes together.

And so it was that I found myself returning to Studio 22. I say returning – the Studio had actually moved location since I’d been last. The first thing I was asked was about my post-natal check (which I’d had just a few days before) and anything that might impact the exercises I was able to do. If you’re joining any exercise class post-natally and you aren’t asked about birth complications or how many weeks it’s been then you may want to consider going elsewhere until later in your recovery.

My chosen class of Ballet Fit has been a brilliant way back into exercise. It’s low impact, so I haven’t been worried about my joints. It helps with toning and strength. And it’s helping to re-build my virtually non-existent core. But most importantly it’s fun, which makes me want to exercise more.

There has been a fair bit of adjustment to make it work. Eating and drinking enough during the day is pretty crucial, as I’m less in control of my energy levels lately. There’s also the impact afterwards of tiredness and sore muscles. More than once, my leg aches have started while sat on the floor at a baby group the following morning, and getting up is just a little more tricky.

So exercise successfully started, but the big cloud of running was still looming over me. When people asked me I talked about my body not being ready, about possible joint pain, and about wanting to ease myself back in. But as I got closer to 12 weeks post-natal a bigger factor started to show. I was scared.

Scared of injuring myself. Scared of accidentally pushing too hard. Scared of how difficult it would be. Scared of the challenge of starting again. Even, weirdly, scared that I wouldn’t like it anymore.

With anything that you’re putting off for the wrong reasons, it’s handy to have a motivational deadline. In my case, an upcoming opportunity for child-free parkrun tourism. And so my Garmin was switched back on, my running shoes were dusted off, and Ben kicked me out the door. 1 mile of 1 minute running 1 minute walking. Not a lot really, but wow it felt good.

There’s a long way to go in my journey of post-natal recovery, but I’m really happy that I’ve made a start.

Wells 10k: race report

For the second year running I took part in the Wells 10k, another race in the Somerset Series. Although the larger field means that the race is unlikely to count for me,1 years of picking up injuries has taught me to get in all the races I can, while I can.

My body is still suffering a bit from the birth of my second child. Okay, I mean, clearly not as much as Lolly’s body is suffering (she wrote a bit about this, here), but the lack of sleep has still had an impact on my training. The combination of not being at my best and the undulations of the course, meant that I was never going to get an especially great time. With that in mind, I opted to take the race a little bit easier, so that I would be able to run a third lap of the course to get my weekly distance up, which should help me in the weeks to come.

As usual, the evening before the race I did a little bit of research: I looked over my Strava and blog from last year. It was a very hot day last year for the race, and after heading off fast (partly because I thought I might have a shot at a PB) my race fell apart when I hit the hill for the first time. Looking at this, I decided that – shock horror – I should try taking it a bit easier on the first lap to see what I could do on the second.2

Race day came around, and as usual at the moment, I hadn’t had enough sleep. This manifested itself in the usual way lately; sinus issues. At this point, a sane person might decide that on this Bank Holiday weekend, a little bit more sleep might help knock these issues on the head. A runner just has a few more sips of water, because water basically cures everything.

A post shared by Ben Timpson (@bentimmo) on

Now, although the hot weather from the week leading up to the race had broken with storms, it was still pretty warm out there. Interestingly, Garmin reckons it was 15.0°C last year, and 17.2°C this year, but I’m convinced it was hotter last year.

So: to my gentle start. Ahem. Roughly 400 metres into the race, I was flying along at about 5:55 min/mile. I was aiming for 7:00 min/mile. By the end of the first kilometre, I’d managed to slow myself down to a 6:26 mine/mile pace. All in all, my pacing strategy didn’t seem to be working. But, with a bit of concentration, and a lot of ‘but everyone is flying past me, this must be far far too slow’, I managed to drag myself down to a reasonable 6:47 for the first mile, before 7:02 for the second mile.

Those were the two reasonably flat miles. Mile three is pretty much up and over Constitution Hill, and proof that you lose more than you gain from a hill. Though in fact a 7:24 split wasn’t awful, and I kept running the whole way up, so small victories! We ran through the well supported area near the start/finish before starting the lap again. Around this point in the race, I just lost focus. There was no real reason for it: I wasn’t particularly struggling, but my mind just started to wander, and my pace dropped off to a 7:19 mile. It would have been even worse, but for the fact that I noticed it and consciously kicked on towards the end of the mile. It just goes to show how important race focus is. My next mile mirrored my first lap effort: miles two and five were more or less the same section, and I posted 7:02 again on the second lap.

So, just that hill to go again…

And yeah, it felt tougher second time around. BUT – I was more consistent this year than last; the Strava segment for the hill had a difference of 7 seconds between laps, while last year I was 16 seconds slower on the second lap.3 I started to push on the downhill. And then one thing led to another, and I was basically starting a hard finish with more or less a kilometre of the race left: Stretching my legs out down the hill, matching the runner beside me to start with before easing ahead of him. Turn into the path behind the Bishop’s Palace, and my pace dropped a touch, until another runner started to catch up behind me. I let him sit on my shoulder, pressing us both on until we turned again into the finishing straight. He strode ahead of me, but it wasn’t time to push yet. He was ahead by one, two paces, and then with just the last 20 or so metres left, I accelerated past him for a much faster finish than I’d planned; shocked to see the clock displaying more or less the same finishing time as last year.

By no means had I been in great form this time last year, but I’d been on an upward trend, and I felt pretty strong when I posted 44:08. This year, my baseline is stronger after my training last autumn, and some reasonably consistent running since then, only really broken by my sinusitis and my little boy arriving. So I guess that this year’s 44:06 shouldn’t be that much of a surprise, and it certainly gives me some confidence going forwards that I can get myself back to where I think I should be.

Oh, and yes… I headed out for that third lap as I’d planned. And felt smug in my 10 miles for the day. Right until I found out that @craig1854 had run the 12 km back to his house after the race…

Next up: Crewkerne 10k (Sunday 4 June. Yes, that’s next weekend.) Yeovilton 5k (Wednesday 14 June)

Notes

1. In the Somerset Series, you have to complete eight races to qualify, and then only your best eight count.

2. Let’s be honest, this should pretty much be my plan in every race.

3. For those interested, last year I did 2:52 and 3:08, this year I did 2:59 and 3:06.

Laying the Foundations

It’s fair to say that I didn’t enjoy the end of pregnancy. The exhaustion, aches and uncertainty really got to me. Still, everyone assured me that I looked like I would give birth early… Or at least earlier than the first time (2 days over)… You can imagine how grumpy I was for the 7 days after the due date before things kicked off. Many apologies and thanks to those who had to put up with me in that time.

Still, at least things managed to start off by themselves the night before I was booked in for a stretch and sweep (if you don’t know what that is, retain your ignorance and just know I was pleased to skip it). The next morning, after much hysteria and entonox, we had a healthy baby boy. And my body felt completely and utterly drained.

So my road to physical recovery started with plenty of food and drink, and grabbing bits of sleep whenever I could. The sleep part being significantly harder when you live with a newborn baby. Structured exercise felt like a lifetime away.

One of the best decisions I made near the end of pregnancy was to buy a stretchy wrap. This has proved invaluable in being able to get stuff done, and look after a small child, while a baby is happily asleep. His love for being tucked up in the wrap has also meant getting out for a walk is really easy. Making the effort to walk places, or to just go for a wander along the river or canal, has been a big boost both physically and mentally.

And, yes, I do always look tired.

In terms of formal exercise, the only thing I’ve made an effort with so far is pelvic floor exercises. If I don’t get that right then I can say goodbye to any high impact exercise in future. I’m also starting to do some gentle postnatal core exercises. Because it currently feels like I have zero core muscles.

And the plan for the future? Well I’m starting to get a little more sleep now (I hope that doesn’t jinx it) which should make it easier to go for longer and more purposeful walks. I also want to set some time aside for postnatal yoga to help me strengthen up. While part of me would love to try running already, I know that I’m not strong enough yet and it just wouldn’t be worth it. I can’t expect my body to get back to racing PBs if I don’t get the foundations right first.

Big Cheese: race report

NOTE: Apologies for this being a little very late. I ran this at the start of March, and I’m posting this exactly two months later. In my defence, in the mean time, we’ve had a little boy, and he’s filled a lot of our time. I’ve got another race report, for the Butleigh MT race, to catch up on too, and then a couple of ideas for other stuff. I’ve also got quite a few races coming up. So we’ll see how well I do on keeping up with writing!

A while back, I decided to ditch my plans to race the Bideford Half Marathon and switch to the Big Cheese instead. The link above explains the reasons in full, but essentially I didn’t want the pressure of the training while Lolly was getting more and more tired due to her parasite pregnancy.

Along with the Exmoor Stagger in both 2015 and 2016, and the Red Bull Steeplechase last year, this would be my fourth “ultra-half”. In addition to the distance element (the Stagger was around 16 miles, and I got 14.4 miles into the Steeplechase before being eliminated) each of these races is made much more challenging due to the terrain and elevation. The Big Cheese actually isn’t so bad as the others; a mere 2,000 ft compared to climbing in excess of 3,000 ft for each of the others. (For reference, Scafell Pike stands roughly 3,200 ft above sea-level.) So… 2,000 ft… should be a doddle, eh?

My club mate, Iain, had done the race last year, and it basically killed him (though he was doing it the week after the Grizzly, which itself came a week after the Bideford Half). Meanwhile, Matt reported that a couple of his club-mates described it as essentially “not too bad”.

It was.

The trip from the race HQ to the race start was around a mile, so made for a handy warm-up. I had ummed and ahhed for a while about what to wear; the forecast was for a complete mix of weather, and the race directors had recommended, though not enforced, us to wear a waterproof. (As a fell race, they could have instituted mandatory kit.)

The race begins with a climb up, and up, and up, which lasts just over a mile. I was content to drop down to a walk reasonably early on – there was plenty more to come, and there was no sense in destroying my legs on the first climb when there would be over 14 miles left to go! Still, it was a bit demoralising letting people stream past me, and my legs felt pretty tired anyway! But hill climbing is still the weakest aspect of my running (a symptom of doing most of my running in Taunton town) so I just have to accept that I’m going to lose some positions on hills. That first mile was actually my slowest of the whole race, and included 615 ft of elevation!

After a mile, or just over, things levelled off to an extent and the terrain got trickier as we dropped down into Rowberrow Bottom. I started to gain some places back on the steeper sections of the descent and paused briefly at the first drinks station. Of course, when you’re in anywhere described as “Bottom”, there’s only really one way left for you to go: up. We were now heading towards Beacon Batch, over Black Down. But of course, nothing is that simple. After a run/walk tactic up the initial hill, we took a sharp left and dropped back down the hill rather than taking a direct route to the peak of Beacon Batch. The descent was a treacherous mix of flooded moorland that was of variable quality, but it was nigh on impossible to judge it by look. It was interchangeably slippy mud, sticky mud and lake. I was running pretty quickly to start with (it was a downhill – duh!) but in order to keep my balance, I kept finding myself going quicker and quicker. I probably looked like a pretty cocky so-and-so, practically sprinting through some of the worst terrain of the course. Had I fallen (and it was probably about 50-50) I’d have looked like a right tit.

‘Shit, there’s a camera, make it look like you’re having fun!’

After a short spell of this, the terrain solidified somewhat and took on a more technical aspect before we started climbing again. Along here the ground got silly, just excessively slippy. It was impossible to find a “good” route through it, you had to be content with finding a route that didn’t place you on your arse. This was pretty much the story of the first half of the race – you were either climbing a hill, descending a hill, or struggling through horrific underfoot conditions. The race website has this to say about what shoes to wear:

“It’s likely to be pretty muddy so off road trainers are an advantage but you will be able to get around fine in normal trainers.”

I mean… sure, you would be ABLE to get around in normal trainers. But I doubt it was fine. It wasn’t fine in my trail shoes. But still, whatever.

I made a fair fist of trying to keep running through the bottom part of the climb, but after a switchback, when I noted that I was closer to Matt than I had expected, things got more difficult. The hill got steeper, we’d turned to face the wind, and the mud was still pretty bad too. I dropped to a walk for pretty much the entire climb up to Beacon Batch, the highest point on the Mendip Hills. Thankfully what goes up must come back down, and most of the following four miles was downhill, although after about 400 metres the path had turned into a rocky river, as it had presumably provided a handy run-off for the rain of the previous week. Down this section I heard one runner behind me stumble and fall, though there were other runners around him, and I’m pretty sure he got up and continued okay.

The next mile was predominantly a gentle downhill along the road, which was a nice change in some ways, although it was tough on the legs in trail shoes at that point of the race. We then turned back off the road down through some former mine workings along Velvet Bottom. The path remained pretty good, and this was one of the quickest stretches of the race, though there were a few tricky drops from plateau to plateau.

And then… the worst section of the entire race. It was probably only around 500 metres, but it was steep, with horrible footing, and 11 miles into the race. While trying to negotiate slippy lumps of rock underfoot, you also had to make sure you didn’t get clothes-lined by an low-hanging tree. Still, as I say, it was only a short section. And best of all: it was the final climb, just a few miles and 700 ft of descent left!

The course mostly levelled out for the next mile and a half, before dropping in a reasonably steep, long downhill towards the finish. Even on tired legs, this played to my strengths at an ideal time: a downhill finish lets me get past a few people who then don’t get a corresponding uphill to regain their place. (Technically, I guess, the mammoth climb at the start of the race was the corresponding climb. So ha, we’re all even!) The terrain varied a little bit on the descent, being a decent even path in some places, difficult stony track in others, before the final half-mile stretch along the road.

Overall I come home in 2:11:35 for 39th overall, although that was partly due to a group of runners that had been ahead of me going the wrong way. Considering my relative lack of training, I was well chuffed. And best of all, afterwards – the free cake and cup of tea!

The whole race was organised really well. Number pick up was easy and straightforward, there was a bag drop at race HQ, along with changing rooms and showers (always nice after a muddy trail race!) The route was well signed and the marshals were all friendly and encouraging – which given the inclement weather, particularly on the top of the hills, was much appreciated. All in all, this is a race that has joined my ever-growing list of “want to run every year” races. In fact, I’m starting to run out of weekends in the year…

Babcary Road Race: race report

Coming into this year, I’d done all but five of the nineteen Somerset Series races over the past few years. Most of the ones that I hadn’t done came early in the year when I’m typically sat at home moping about an injury, rather than getting out and racing. So this year, I’ve been taking every opportunity to get out and do the unknowns. Babcary was one of those. Described as “undulating” on their website, the race also had an unusual distance of 7.5 miles. After a bit of research, I managed to find an elevation profile so that I knew what I was heading into.

I wasn’t injured, but I was still moping – a string of colds had struck me down (too over the top??) through the start of the year, I was really struggling to string two decent weeks of training together. Babcary itself came at the end of another cold, albeit one that I tried to ignore and just run through. With mixed success. At the race, I met up with Nigel, who briefed me a bit about the course (he has a ridiculous memory for courses; he can do one once and then relate the whole thing in detail the following year). I did a short recce of the start of the course as my warm-up, heading out for about three-quarters of a mile before doubling back, confirming what Nigel had told me: it was a long uphill drag to start the race.

If I looked (and felt?) like this at the start, you can only guess how I was at the end…

Forewarned is forearmed, and so I planned a gentle start to the race. Turns out (no shit) that everyone else had the same plan – especially the leaders, who made a very sedate start. So much for my plan of having a bit more in the tank after not wrecking myself on the first hill. I swear runners are never normally this sensible…

The course lived up to its description of undulating: it never really levelled off. A gentle descent replaced the first climb, before itself switching to another steady uphill. Throughout the race there were no awful climbs, but merely a continuing series of ups and downs that prevented you from ever finding a proper pace and rhythm.

The race went generally as I might have expected: I was slightly further down the field than I would have liked (but better than I worried I might be) and I mostly lost time to those around me on the climbs, and made it back on the descents. I started to struggle towards the end of the race, slightly negating a downhill finish that should have suited me well, but overall I was happy enough with my performance given how the year had started.

There wasn’t much time to rest and recover though; my next race, The Big Cheese (15 miles of hills and mud) was the following Sunday…

Easing back up to distance again

After my recent bouts of cold bugs, my mileage took something of a hit. I set myself a target of running 1,200 miles this year, and I was really hoping that I could actually manage 100 miles each and every month. (Possibly an optimistic target with baby #2 on the way in March/April.) Unfortunately, I failed at the first hurdle, only accruing 63 miles in January, and not running at all for the final 10 days of the month. I’ve only missed the first 3 days of February, but to avoid injury after a spell off, I’m easing back into my mileage.

First, a parkrun and a 6.5 mile Sunday run. Then a 17-mile week in which my furthest single run was 7.1 miles. This last week, I’ve been away from home with a work training course, which is always a little difficult. I was easily able to find somewhere to run – I was staying in a hotel just off the seafront in Worthing, and as far as I can tell, the road runs beside the sea for miles and miles in each direction. In fact, I’d been tempted to run to (or back from) Brighton one day, getting the train in the other direction, but my training ran quite late each day, and so it was never convenient unfortunately. Still, I managed 14 miles during the week, and another 11 miles at the weekend took me up to 25. I’d have preferred a longer ‘long run’ than 8 miles, but I was constrained by both my weekly mileage target of 25, and a twinge in my knee that had bothered me towards the end of the working week. It disappeared over the weekend though, so I assume it was either the old trainers I’d worn in Worthing for my runs, or just the different forces on my knee during the training.

In two weeks time, I’ve got the Big Cheese race, a 15-mile mostly trail course, which I’m a bit concerned about. I’ve only run beyond ten miles once since Christmas, and haven’t been out on the trails much either. And unfortunately, I can’t do much to improve that next Sunday, when I’m also racing; at the Babcary 7.5 mile road race. Still, I’m hoping for a 30 mile week, and I’ll see how I’m doing after that.

Stopping and starting again

Traditionally, at this time of year, I’m not running much. In January 2015, I only managed 18 miles after somehow contriving to injure my knee during a gentle 10 mile run with my running club. In January 2016, I hit the heady heights of 38 miles, after falling on the coastal path and contriving to convert a dead leg into a knee injury.

In actual fact, both injuries were more or less caused by the same thing: in 2015, I was trying to come back and stack too many miles back in too soon after a lay-off due to a cold. I’d barely ran in two weeks, and then ran 13 miles in two days. It was a bad idea. In 2016, I probably ran too much too soon after getting a dead leg, and put undue stress on my knee. So, yeah, I have something of a history of impatience. In 2015, I didn’t get running properly until around May, while in 2016, it was April.

Which has left me a little nervous at the moment: after running 122 miles in December, January was pretty stop-start. Twenty miles the first week, then a cold limited me to 6 the week after. Then I was right back up to 30, before another cold put me out for the better part of two weeks.

Rocking my cow cowl through the puddles at parkrun

I started running again yesterday, at parkrun, and managed a reasonably sedate pace through the puddles. Normally, I try to run-commute to parkrun, but this week I wanted to keep the mileage down, so drove. Today, I headed out for a gentle six miles around the route of one of our club’s race routes (next weekend; sign up here!)

I always find it difficult coming back from an injury or illness. All the advice says to drop your mileage and then gradually build it back up again. But there is very little guidance on how much to drop your mileage – if I normally run 30 miles a week, it would be pretty unreasonable to come back with just 10 miles per week, but clearly coming straight back at 30 isn’t a good idea either. In consultation with my physio, we reckon 20 miles should be about right this coming week, and then build sensibly from there.

Hopefully this year I can manage to avoid serious injury…

Training update (or How I changed my mind and my target)

My plans were pretty set for this spring. After my successful half marathon training for Bristol last autumn, I was going to try and push on and see what improvements I could make this spring at the Bideford Half Marathon. The race was carefully chosen to be about a month before Lolly’s pop date, so hopefully my training and her pregnancy wouldn’t clash too badly.

Which was great, in theory. But pregnancies don’t happen in theory, and nor do training plans. In order to follow a similar training plan to last time, I had to start on 12 December, the week after the Bovington Half Marathon. Even though I took a bit of a shortcut in that race, I’d still pushed myself pretty hard (harder than I’d realised, in fact) and my body was pretty broken. That week was also the week that I was meant to be running my 100th parkrun, which didn’t really fit with the plan. In the end, rather than the 31 miles called for by my training plan, I did 8.7.

Bovington was a good race, but it didn’t leave me in great shape to start a training plan.

The next couple of weeks went better: 32.6 and 34.6 miles. But if you scratch below the surface, things weren’t so rosy. These were the two weeks around Christmas, and between work and the celebrations, my running wasn’t too strong. I abandoned a lactate threshold run halfway through, my long run the first week was split into pieces because 1) it was Christmas Day and 2) there was a parkrun. The second week, I had the Chard Flyer instead, and with the foul weather, I didn’t add any extra miles in.

At this point, I decided that with the Stoke Stampede coming up, that although my training hadn’t been ideal, I would treat it as base training for eight weeks of proper training after. Except that I got a cold. So what would have been the first of those eight weeks involved two runs, totalling 6.1 miles.

Not how an ideal training period would look.

Alongside all of this was Lolly’s developing parasite pregnancy. Unsurprisingly, she has been getting more and more tired, and after her Christmas Eve parkrun, she really struggled for the rest of the day. It became apparent to me that a heavy training plan that would leave me tired at times would not combine well with a pregnancy that was clearing leaving Lolly pretty tired.

And so, plans have changed. I’m not going to run Bideford at all, but instead do Cheddar RC’s ‘The Big Cheese’, a 15-mile trail race. Admittedly, switching from a reasonably flat, road, half marathon, to a hilly, muddy, 15-mile race does not at first glance appear like taking a step down. But in reality, the long runs will probably be around the same distance, and I’m not so concerned about the pace. Sure, I want to do well, but there isn’t the pressure to be pushing myself up to and over my limit. As a consequence, there isn’t the pressure to push myself so hard while I’m training. I still want to do a good variety of sessions; intervals, long runs, tempo runs and some recovery stuff too. But I will be more able to tone them down and keep a better balance with home life. Which given I have two rooms to redecorate (amongst other things) can only be a good thing…

Chard Flyer: race report

As the first race of the Somerset Series each year (and let’s face it, being on New Year’s Day, there will never be one earlier…) this race has been on my radar for a while. Two years ago I signed up for it but was ill and so didn’t run. Last year, I was more interested in running a parkrun double. Truth be told, this year I was more interested in running a parkrun double too, but as Lolly wrote about in her last post, she got too pregnant, and we realised it wasn’t going to be a sensible idea.

So what are the pros and cons of running on New Year’s Day?:

  • Con – New Year’s Eve. Staying up until after midnight drinking is hardly great race preparation.
  • Pro – New Year’s Eve. If you don’t stay up until after midnight drinking, you’ll probably do better than most.
  • Con – New Year’s Eve. That means if you want to do well, you might have to avoid staying up until after midnight and drinking.
  • Pro – You get to clock up some miles on the first day of the new year, which is a great way to start.
  • Con – Christmas. All that food and drink and merriness is not great race preparation. And, with no disrespect to the Chard Flyer, if you’re taking Christmas easy to prepare for this race, you’re probably doing life wrong.

I actually ticked the ‘pro’ box for New Year’s Eve – having a toddler, and being sad, meant that I was tucked up in bed at home before 10, rather than partying hard through the night. My race morning didn’t start especially well though. Despite assuring Lolly more than once that I wouldn’t forget anything, particularly my Garmin, even though I was leaving my preparation to the last minute, I forgot my Garmin. Thankfully, rather than being of the ‘I told you…’ persuasion, my loving wife instead undertook an hour’s round-trip to bring me said watch. Much to the disgruntlement of our daughter, who quite specifically declared that she wanted to stay at home, and didn’t want to watch Daddy running.

Posing with the club

We had a decent club turnout for this race, which also forms the first of our Club Championship, and so there were plenty of people to mingle and chat with before and after the race. My main concern before the race was how many layers to wear – it was pretty damn cold and wet, but I tend to overheat in races. Initially I went for the club vest over t-shirt approach, but a particularly heavy shower saw me run back to the car to switch to a long-sleeve base layer instead. This, it turns out, was the wrong decision.

Anyway, as usual, I’ve blathered on for ages before even getting to the run itself, so I’ll get on with it. I knew that the first couple of miles were mostly downhill, then there was a tough uphill, and then it was mostly flat with a gentle climb at the end. So I planned to take it reasonably easy early on, and use my energy in the second half of the race.

Ha, like that ever happens! I covered the first two kilometres in under eight minutes, as we descended down out of Chard and alongside the reservoir which we were to loop around. Ostensibly, this is a road race, but a lot of the course is along tarmac paths and back roads that aren’t necessarily in the best condition underfoot. It’s definitely a course for road shoes, but you have to have your wits about you. The race follows route 33 of the National Cycle Network, which runs along the path of the old Taunton-Chard railway line.

We scaled about 15 steps to climb back to the road, and then the hill began. I’d done my research before the race, and so I knew that the ascent went on for about two kilometres, and so settled myself in for the long haul. Being a Somerset Series race, there were plenty of people around that I recognised, and I felt that I was in about the right place, but I didn’t mind if a few of the went past me up the hill – it isn’t my biggest strength, and I’d rather save my energy. (Genuinely, this time.)

As it turned out, with the exception of one particularly good climber, we all stayed pretty much in position with few significant gains made by anyone. One slight annoyance on this hill was the marshal who declared “drinks at the top” while we were about a quarter of the way up. I know he didn’t mean it to, but it sort of suggested that it wasn’t going to be much further to said drinks, even though it really was. The hill had a small false summit about three-quarters of the way up, which was a little disheartening, but soon we crested the hill and were able to take on some water.

This being a road race, I hadn’t really expected my recent trail downhill specialism to have any effect, but it turned out that the Chard Flyer has a particularly steep downhill section, and though it is on road, it was that steep that it played to my advantage. I passed a fair few people on the half mile descent, but mostly, I just enjoyed it!

Unfortunately, there was still about two and a half miles of the race left. The course remained mostly flat as we passed the reservoir on the other side along some paths that gave the course a nice off-road feel, though the terrain remained solid and friendly. I was beginning to struggle now; the ‘easy first half, reap gains in second half tactic’ having fallen by the wayside during the first half. Which was a shame, because I’d have quite liked that plan in the second half…

This picture does somewhat oversell the race scenery…

As it must, given that we’d dropped down towards the reservoir at the start, the end of the race climbed back up into Chard, twisting and turning a little through industrial estates, residential streets, and some paths. I wasn’t really aware of anyone that close ahead or behind me by this stage (quite a familiar feeling late on during Somerset Series races) so it was hard to judge my effort levels. Other than to say that I didn’t feel like I wanted to put much more in! Still, I soon recognised that we were back near where I had parked, and therefore the finish line. A little spurt got me to the end, though it wasn’t enough to overhaul the runner that I had finally caught sight of ahead of me.

In the end, I finished in 42:06, good enough for 26th, and sort of a new PB. Sort of because, 1) I’m not completely sure that it was full distance – my watch said 9.8 km, though obviously GPS isn’t all that accurate. 2) During the Bristol Half Marathon, my first 10 km was somewhere in the region of 41:30, and my overall average pace during that race was quicker than my average pace in this race. So, yes, it was a PB time for a 10k race. But also, I can do better. Which is good. The Stoke Stampede the following weekend was supposed to give me a shot at proving that (and maybe, just maybe sneaking in under 40 minutes) but unfortunately, I had a cold, and didn’t run.

Me, looking gorgeous, at the end.