The forecast for Sunday morning in Guildford didn’t look good on Friday evening. That it was going to be cold wasn’t really in question. Nor was the fact that a big weather front was going to be dumping moisture from the sky. The questions were whether that moisture was going to be falling as heavy rain or heavy snow – and whether there might be storm-force winds.
Normally, I’d only have a passing interest in Guildford’s weather, what with the Surrey town being about 25 miles south west of my house. But Guildford was also the location for the Hogs Back Road Race, an 11.7km run I’d signed up to run.
Of course, when I’d signed up, I had no idea what the weather would be like – aside from the general assumption that it might not be that pleasant, what with the race being held in Britain on the second week in December and all. But there’s not very pleasant, and there was the forecast for this weekend. With cold weather, heavy rain and/or snow, and potentially storm-force winds. Frankly, I wasn’t exactly looking forward to it, especially given the course included 147 metres of climbing – the clue is in the title, since the Hog’s Back is an elongated ridge on the North Downs in Surrey.
Incidentally, I’m entirely blaming my mate and fellow runner Matt for my entry: he’d signed up first and encouraged me to join him. It was also his idea to do the ridiculously hilly Treggy 7 in Cornwall. He’s a glutton for punishment, or something.
It didn’t help that I wasn’t feeling quite at full strength. I’d been suffering from some form of mild illness, which left me a bit short of energy. I made it to yesterday’s Kingston Parkrun, but didn’t exactly set a quick time. After a restful Saturday, I felt much improved by yesterday evening, if not quite at full strength. Well enough, though, that I didn’t think I could justify sitting out the Hogs Back Road Race on account of illness – even I knew I wasn’t going to be setting a blazing pace on it.
The question about the weather hung around for most of Saturday. The confusion was that there was a big cold front over Britain, but a milder front sweeping in. What nobody quite knew is where the heavy clouds would meet the cold front.
When my alarm went off at six am on Sunday morning, the noise of rain pouring down outside gave me the answer. There was no snow. Just rain. This was probably good news, on balance, since a heavy dumping of snow could have led to the event being cancelled. When I’d gone to bed on Saturday night, I’d a quick glimpse at the Twitter feed of AAT Events, which organised the race, just in case they’d postponed it preemptively.
— aat events (@allabouttri) December 9, 2017
They hadn’t, and heavy rain on Sunday morning in Richmond-upon-Thames was a sign that there was very unlikely to be snow in Guildford, either. Again, this was, in theory, good news, since it meant the race going ahead. Yet as I contemplated leaving my house a good hour before daylight, in near-freezing conditions and with rain pouring down, this didn’t exactly seem like a good thing.
I did question my sanity for still going ahead with this when I wasn’t feeling at full strength, especially on the drive out of south London and down the A3, which involved dodging substantial patches of standing water on the road.
It was still miserably wet when I parked up on the grounds of Loseley Park, a 16th Century manor house set in what I think are lovely grounds – but which were mostly wet and bleak during my visit. Thankfully, the rain did ease off – as the forecast suggested – before the start, but it returned for much of the race.
Still, it had rained so heavily that much of the route was sodden, with standing water all over the place. The Hogs Back Road Race course, as described on the event website, is: “90% road and 10% gravel track.” This seemed roughly true. But that description was followed by the line “no mud”, which emphatically was not true. The heavy rain had washed muck all over the gravel paths. At times, the choice was to trudge through standing water or mud. Nice.
All that climbing didn’t help either. Most of the uphill was thankfully in the first half of the event, and wasn’t as bad as I feared: the climbs were mostly long but steady, rather than being brutally steep – although a few uphill hairpins didn’t help.
That said, about halfway up the first hill I realised how little energy I really had, probably a combination of illness and my relative lack of enthusiasm. I found myself ticking into some form of ‘survival mode’, and I trudged through the rest of the event at a pace that was some way from my potential – even accounting for the cold, mud, rain and hills.
I was genuinely glad to reach the finish. And I was utterly thrilled that I had a car for the weekend that featured both heated seats and a heated steering wheel.
As I drove out of Loseley Park, fingers just thawing on a warming wheel, I decided I perhaps should have trusted my instincts and sat out the race.
Of course, then the runner in me kicked in. By the time I was home, I was cheered from the feeling of having conquered such a challenge, and of having pushed myself to do something despite my instincts not to.
There was extra cheer, too, from downloading the data from my Garmin GPS running watch. I mentioned before the race was a very unusual 11.7km distance. Partly that’s because of finding a course that starts and finishes in the same place. But it also seems to be so the Hogs Back Road Race looks like this…
Somehow, that made it all worthwhile.
— James Attwood (@Atters_J) December 10, 2017
Late Spring into early Summer is probably peak running season, in Britain at least. It’s when the nights are getting longer and conditions are, in theory at least, just about perfect for running: not too cold, not too hot, and relatively dry.
That’s the idea, anyway. Britain being Britain, nothing is certain. This year the weather has alternated between unusually warm and unusually cold with seemingly reckless abandon. And, Britain being Britain, it’s usually ended in a dreary grey halfway house.
But I digress. The point is that this time of year is just about the best time of the year for running. And that means there’s no shortage of races to choose from. The challenge is deciding which ones to do.
Do you do a handful of long races, or a lot of short ones? Do you return to events you’ve done before and really enjoyed, or pick ones you haven’t done before? It’s such idle consideration and searching of running event websites that often leads me to sign up to races without full consideration to my calendar. Which explains how, earlier this week, I ended up running two 10k races in two days.
Here’s my excuse. Last weekend was a Bank Holiday in the UK, and it seemed a good idea to spend my Monday off work contesting an event near Reading called the Shinfield 10k. Also last week was the Silverstone 10k, an enjoyable event that takes pace on a weekday evening and features two laps of the British Grand Prix circuit. As a big motorsport fan, it’s hard to resist – hence why this was the third year in a row I’d entered it.
I hadn’t fully looked at the dates before signing up, then realised they were in the same week. Not too much to worry about though, since the Shinfield 10k was on Monday morning, and the Silverstone 10k was on Wednesday evening. Plenty of time. Until, the night before the Shinfield 10k, I realised I was wrong about something: the Silverstone 10k was on the Tuesday evening…
So, inadvertently I faced the challenge of running two 10k races in two days. And once I realised I’d signed up to do it, it was an interesting challenge. I knew I could cope with the distance – after all, 20k is just short of a half-marathon distance, and I’ve proven that I can run a full marathon in one go.
Still, it was hard to know how my legs would react to being pushed twice in the space of 36 hours or so. And what tactic should I adopt? Run as fast as I can on both? Use the Monday morning 10k was a warm-up, and save myself for Tuesday night’s outing? Or push on Monday, and be prepared to coast on Tuesday night? Hmmmmm.
In the end, my plan was to set off on Monday morning’s Shinfield 10k at a decent pace, and see how I felt. I didn’t know the course, so I wasn’t sure what hills or challenges it might offer that could prevent a quick time.
It was certainly an interesting run. Because while Shinfield seems to be a relatively small town, it won’t be for long. There’s a massive housing development going on there, which forced organisers to revise the route for this year’s rate. Curiously, it went right through the development. Which meant that, as well as undulating country lanes, a few kilometres near the start and finished involved running on a semi-finished path in the middle of a massive, flattened space that will shortly become a huge building site.
Slightly odd then, but it was still an enjoyable semi-rural run. And in a field of pretty competitive club runners, I was happy to cross the line in 58th place, with a time of 40m 48s. That worked out at an average pace of 4m 03s per km. Decent.
The Silverstone 10k course could also be described as slightly odd, in that it takes place entirely on the racing circuit. As mentioned, I’m a huge motorsport fan, and jump at any chance to run on a race track: as well as Silverstone, I’ve also done runs that have taken in Castle Combe and Goodwood (and I’ve already signed up for a race at Thruxton later this year).
The Silverstone route starts on the old finish straight, and covers two laps of the old grand prix circuit (it skips out the new ‘Arena’ section). And it’s always good fun, even if the weather is somewhat unpredictable.
The first time I did the race, it absolutely poured down and I got completely soaked. Last year’s run, by contrast, was held on one of those absolutely beautiful English summer evenings. This year was a bit more mixed: while there was no rain, the grey clouds suggested it wasn’t far away, and there was a fairly stiff chilling breeze (a common hazard on Britain’s race circuits, given many are ex-World World Two airfields).
Again, I set off without really decided on a pace strategy, figuring I’d just see how my legs reacted – which turned out to be fairly well. While a bit achey before the start, once I was running they loosened up quickly, and for most of the run any effects of the previous day’s exertions didn’t figure.
That was until I turned onto the International pit straight on the second lap, with about 2km left to run. The wind had picked up by this stage, and I was running straight into it. I could feel it slow me down, and that extra effort seemed to prompt my legs to remember I’d run hard on them the day before. They suddenly began to feel very heavy.
Still, I tempered that slightly wobble, and managed to finish strong. Against a huge field of competitive club runners, I was pleased to come home 160th, with a time of 41m 14s.
Now, the 26s gap between my two finish times would suggest I was slower on the second half of my accidental back-to-back… but there’s a twist. Every time I’ve run it the Silverstone 10k course has, by measure of my Garmin GPS, been around 180 metres long. Sure enough, comparing the results on my watch suggests that the 26s difference was largely down to a longer course. In fact, my average pace per km on the Silverstone 10k turned out to be… 4m 03s. Exactly the same as I managed on the Shinfield 10k.
Now, does that suggest I pushed to the max on both races, or that I could have gone really fast if I’d focused on one? Hmmmmmm…
Anyway, the moral of those story? Well, it doesn’t really have one, to be honest. Other than this: it is possible to run two competitive 10k races on back-to-back days. But maybe it’s best to spread these things out a bit…
This is a story about a hat. A black woolly hat, to be precise.
As woolly hats go, it is as basic as they come. It doesn’t have a fancy patterned design. It doesn’t have a fancy brand label on it. It doesn’t any fancy thermal lining. It doesn’t have any design flairs, or floppy ear covers, or a strap to hold it in place. And it certainly isn’t topped with a brazen, bouncy bobble. It is a black woolly hat; nothing more, nothing less. As woolly hats go, it is utterly unremarkable.
I can’t tell you much about the hat. It doesn’t have a notable origin story: I found it at the bottom of a box in my house a few years back. It must have come from somewhere before it found its way into that box, but I certainly can’t remember buying it. I couldn’t even tell you which shop it might have come from: it is such a simple, basic woolly hat it doesn’t even have a care label.
In summary, it is a black woolly hat. Nothing more, nothing less. So how come it is a hat I can’t throw away?
For clarity, when I say it’s a hat I can’t throw away, that isn’t due to some sentimental attachment or particular fondness for it. What I mean is that it’s a hat I can’t throw away. Believe me, I’ve tried.
As best I can remember, the hat I can’t throw away made it’s competition debut pretty much exactly two years ago this weekend, on the Chilly 10k, held at Castle Combe Circuit in Wiltshire. The forecast for the day of the event was pretty typical for the time of year in Britain: a cold start with a fairly brisk wind, warming up a bit through the day. The sort of forecast that makes picking the right kit difficult.
The challenge was to wear enough warm clothes so that I wasn’t too cold at the start and in the early stages, but not over-dress so much that I became too hot late in the race when I was fully warmed up. I settled on a long-sleeved technical running top beneath a short-sleeved running T-shirt. But I was concerned about my head getting too hold. It seemed sensible to wear a hat for the cold, early part of the race – but I feared I wouldn’t need it later in the race when I warmed up.
I looked at my range of woolly hats, and none of them seemed to fit. I had some reasonably expensive ones with nice patterns and super-warm thermal lining. But they might prove too warm. And what would I do with it if I over-heated during the race? Pull it off my head and carry it? Didn’t seem like a good idea.
If I was going to start the race wearing a hat, I didn’t want to be burdened by it if I warmed up too much. Rather than carry it for most of the race, I’d rather just throw it away. But it seemed a real waste to pick a ‘nice’ hat and end up getting rid of it through overheating.
I found the answer at the bottom of a random box – and it was woolly, black, and utterly unremarkable. It was the perfect solution to my dilemma: the hat’s basic, simple construction meant I was less likely to get too hot in it quickly – and I could hardly have a sentimental attachment to a hat I couldn’t remember owning until I found it in a box.
The absolutely unremarkable nature of the hat made it the perfect solution. I’d wear it for the start of the race. If I overheated, I’d just pull it off my head and toss it in a bin whenever the opportunity arose.
Funny story: the hat kept me warm at the start, yet the weather never actually warmed up enough for me to throw the hat away. I finished the race with the hat very much still on my head.
Which meant I was able to wear it for the same reason again on the Kingston 10k the following weekend. And on many other subsequent races and long training runs since.
Essentially, if it’s cold enough to start the race or long run with a woolly hat on, the unremarkable black hat is my headgear of choice. A few times the hat has come off my head. Once, the wind suddenly picked up, I got cold again and I put it back on again a few hundred metres later; in most others case it was so close to the finish that it didn’t make sense to throw it away.
But I have actually thrown the hat away in two races. And yet still I own it. Eh?
The first was this year’s Hampton Court Palace Half Marathon. It was definitely woolly hat weather at the start, but after about five miles I’d warmed up so much the hat I whipped the hat from my head. Was it finally time to throw it away?
Not on this occasion. My Mum was visiting to cheer me on for the event. She’d come with me to the start at Hampton Court Palace, and we’d worked out that she was going to spectate near the palace gates when the race went back past there just after half-distance. So I decided to wait until then before throwing away the hat. As I reached the corner nearest the palace gates I spotted my mum, exactly where she said she’d be. Without breaking stride, I slung the hat in her direction. I wasn’t quite on target, but it was close enough for her to pick it up and return it to me at the finish.
That meant I still had the hat for this year’s London Marathon. Again, it was a cold start, but seemed likely to warm up. Perfect unremarkable woolly hat conditions. And, sure enough, about six miles in, I’d warmed up enough to take the hat off.
My brother came to the marathon to cheer me on, and we’d looked ahead to work out where he was going to try and spectate. His first spot was about seven miles in, in Greenwich just after the Cutty Sark. I knew which side of the road he’d be on, but he could have been anywhere within a half-mile or so stretch. Which the crowds at least three-deep in most places, it seemed unlikely I’d spot him.
Still, given when I’d removed the hat, it seemed silly not to leave it a bit before throwing it away, just in case. So I ran along, hat in hand, scanning the faces in the crowd, until – there he was. I spied my brother and, as I closed in and shouted some form of vaguely coherent greeting, I tossed the hat in his direction.
It wasn’t exactly an ideal situation for a hat hand-off. I was focused on running, the crowd left little room for a target window, and my brother had no idea I was about to throw him a hat, and was busy cheering me on and trying to take a photo.
As I ran on, I had no idea whether he’d even seen the hat being thrown in his direction, let alone grabbed it.
By the finish of the marathon, I was too exhausted to even remember the hat. After staggering through the finish area, finding my mum and brother and trying not to be overcome with emotion and/or exhaustion while celebrating, we limped on to a Pret near Trafalgar Square. After picking up a coffee, we couldn’t find anywhere to sit, so we headed over to a bench in Trafalgar Square.
By that point the heat I’d built up doing the marathon was rapidly fading, so I was quickly adding layers to try and keep warm. What I needed was something to stick on my head… and then, from his pocket, my brother produced the perfect solution: a black, woolly hat. An utterly unremarkable black woolly hat.
Of course, there is a weird twist to proceedings. The hat was pressed into service precisely because I had absolutely no emotional attachment to it. But not this hat has now served me so well on so many runs – and survived my repeated attempts to dispose on it – I’ve become quite attached to it.
So haven’t started as a hat that I can’t throw away, it’s now become a hat that I can’t throw away. Which, as the mid-November temperatures drop and I start to contemplate a season of cold weather running – starting with my third outing on the Castle Combe Chilly 10k tomorrow – I’m left with a dilemma. I’ve got a hat that’s ideal to wear for the conditions: warm and comfortable, but cheap enough to throw away if the weather warms up. But, if the time came, could I actually throw away a hat that’s served me so well? Hmmm…