Here’s an oddity. I took up running four years or so back as part of a general kick to become fitter, less fat and all together healthier. It’s clearly worked too. Not only can I now do things like run marathons quite quickly, but I’ve transformed my diet, cutting out masses of chocolatey, biscuity things and adding in lots of fruit and veg and salads and stuff.
The odd bit? Well, as counterintuitive as it seems, taking up running has helped reintroduce me to many of the sugary sweets and snacks I remember from my childhood but had long since moved on from, even in the worst of my ‘Fatters’ days.
Of course, this time there is some purpose to the sugary sweet things: it’s all about energy. If you’re going to run, you need energy: before, during and after. The science bit is that you need energy in easy-to-digest carbohydrate form so it will start working faster (I should add here, as should be obvious, that I’m not a trained sports scientist, so if you want the proper science best go look elsewhere).
That’s why the shelves of running shops and the like are full of those carbohydrate and energy-filled gels, all scientifically designed to get you energy quickly during exercise. And, well, it turns out that sweets such as jelly babies or jelly beans actually actually have a very similar mix of sugary carbohydrates.
Add to that the fact that race organisers like to give out treats to runners who’ve just finished a race – because if you don’t deserve a treat after a race, when do you? – and runners get plenty of opportunity to relive their childhood sweet-eating days without the guilt (well, with only a bit of guilt).
In fact, along with the almost inevitable banana (which I rarely eat, since I’ve already eaten one…), most races end with me walking away with a small bag of sweets that double as some fine childhood memories.
Here are some of the childhood sweets I’d almost forgotten about – and how suited they are to running.
A classic, although quite odd when you look at them through grown-up eyes. I mean, whose idea was to make multi-coloured sweets shaped like, well, babies? And why didn’t I realise during my childhood that eating Jelly Babies by starting with the head was all a bit sinister?
Still, there are few better sweets to eat during a long run. They’re practically the same make-up as most energy gels, but are a little more solid to chew on, if you like that sort of thing. And you can still actually taste them at that strange part of a marathon when your exhausted body start playing weird tricks with your mind.
In this case, of the Haribo variety. Fizzy cola bottle sweets are really quite sharp and tangy, which can make them something of an acquired taste when running (or, indeed, at other times). I’ve always been confused why fizzy cola bottles don’t really taste that much like actual cola, at least to me.
Incidentally, Haribo’s most popular product is its gummi bears, which also make decent running energy snacks. I find them a slightly tough chew than Jelly Babies which, for me, means they’re not so suited to mid-run chomping. A small packet makes a fine post-race pick-me-up, though.
You can get these in Britain now, but they’re probably more of an American thing. They certainly weren’t as common growing up, which makes me somewhat less nostalgic for them.
The big difference between Jelly Beans and Jelly Babies – aside from the fact they’re less intrinsically sinister by design – is that they have a hard outer shell, so they take a lot more chewing. If you like to take your time with your energy snacks, that’s a good thing.
In America, you can now buy Sport Beans, which are designed as mid-exercise performance snacks. I’ve a deep suspicion they’re essentially exactly the same as regular ones, albeit in slightly plainer flavours (there are some odd flavours of Jelly Beans…), but even so, my Texan marathon experiences have made me a fan. Mixing energy gels with a pack or two of Sport Beans gives me a good variety of energy sources during a run. I think.
A variant of the above, really, and I’ve done a few events in the last few months that have given them out post-race. I’ve found they’re less than ideal for such a purpose, because they’re huge, so you can’t fit them into your mouth all at once. Trying to manage biting a chunk off a jelly snake in a dazed post-race aftermath is quite a challenge.
Another childhood classic. The sugar coating on the outside sets them apart from Wine Gums, and also reminds you they’re not intrinsically healthy. A little hard for chewing while running.
Love Hearts may be the oddest sweets of all. They’ve got a distinctive texture for one thing: they’re hard, and powdery or chalky in texture. But that means you can chew or suck them quite successfully. And they’re not quite as sugary sharp as other sweets, which is a bit of a benefit in the aftermath of a run. Which is good, because mini packs of Love Hearts seem to be a frequent sweet-based giveaway at the end of races.
But really, Love Hearts are odd. Odder than Jelly Babies, even. Who devised a tablet-shaped, slightly powdery sweet, looked at it and decided that a way to improve it was to inscribe love-related messages such as ‘Kiss Me’, ‘U Rock’ and ‘All Yours’ on them?
Of course, this is only scraping the surface of the large childhood sweet tin. I’ll probably think of more soon – likely the next time I’m at the end of a race and there’s a goodby bag handed out. I may write about some more soon. Anyone got any childhood sweets they’ve particularly enjoyed reuniting with through running?
A short time back, on a cold but clear Sunday morning, I set out to do a long run. For all sorts of reasons, I’d decided I wanted to run for somewhere between two and two-and-a-half hours. I wasn’t overly concerned how fast I went, but I was interested to see what sort of pace I could sustain, and how long I could sustain it for.
I eventually settled on a route that followed the river path of the Thames from my home in Richmond-upon-Thames (well, technically I live in Ham, but Richmond-upon-Thames always sounds posher…) down through Kingston-upon-Thames to Hampton Court, where I’d cross the river, and headed up through Teddington and Twickenham to Richmond. At which point I’d cross back across the Thames and head back down the other side of it to my house.
About one hour and ten minutes into my run I was about halfway through my route, on the Thames path between Hampton Court Palace and Teddington, busily trying not to make a fool of myself downing an energy gel while running, when my Garmin GPS running watch beeped. And it wasn’t the good sort of beep, either – the beep that comes when you’ve reached whatever ‘lap’ you’ve set it to (normally one kilometre or mile, depending what sort of race/training I’m doing). No, this was the prolonged loud annoying beep that’s accompanied by a big box popping up on the display bearing the dreaded words: LOW BATTERY.
Now, this certainly wasn’t the first time I’ve been out running when my Garmin has started beeping battery warnings. It’s happened a few time, and it’s always quite annoying. Firstly, because that big ‘LOW BATTERY’ box stays on your screen until you press a button to make it disappear – but when you’re running, it’s actually quite tricky making sure you press the right button, and not accidentally stop timing, turn the light on or make your watch do some other crazy thing you didn’t previously know it could do.
It’s also annoying because you never really know how long you’ve got until the low battery becomes no battery, and the watch just stops working. It’s like when the fuel light comes on in your car, and you have to sort of guesstimate how long you’ve got before you run out of petrol. But while running, obviously.
Previously, I’ve been fortunate enough that my watch has only ever started beeping low battery warnings on relatively short training runs – the sort where it doesn’t really matter if it stops working or not. But on this occasion I was just over halfway into a long training run, where I was absolutely interested in how long I’d run for and how far I’d travelled. If my watch battery completely ran out, I wouldn’t know for sure. And, worse, I’d probably lose the data for the run so far.
So what to do? Well, there were two options. I could have detoured from my route and headed home sooner, which would have ruined my running distance goal, but would have at least allowed me to pretty much guaranteed I could finish the run before the battery was finished.
That option didn’t really appeal though: so option two it was. And that meant gamely pressing on, keeping my fingers crossed that I’d make it to the end of my planned run with enough battery for my GPS watch to keep working.
So that’s what I did, although it was somewhat distracting – not only because the LOW BATTERY warning screen and accompanying beep kept popping up on the screen at regular intervals, but also because I found myself gazing at my watch more intently than usual, trying to remember the finer details of my time, distance and pace, just in case the screen suddenly went blank. Like searching for a petrol station when your fuel light has been on for a good 30 miles or so, it was genuinely quite nerve wrecking.
But I made it though: just. When I went to plug my Garmin in to charge after the run, the display said it had 1% battery remaining. Close!
Of course, there’s a third reason that being distracted by my GPS running watch being low on battery is really very annoying – and that’s because the only person I’ve got to blame is myself, for forgetting to charge the thing before setting out on a long run…
Part of the problem is that my Garmin is now three years old or so, and as with many electronic devices the battery life just isn’t as good as it used to be. But that’s no real excuse for just forgetting to charge the thing.
Still, it could be worse: I could have forgotten to put it on altogether. Which is exactly what happened to me for a 10k race recently. More of which soon…