Yes I ran it again. It is a lot of fun but still very strange. Chip-timed but no results published! Well, they are published but hidden. Here they are:
The leaflet that comes with the bib for the race says to use the QR code on the bib to view your results. That takes you to Girls on the Run Las Vegas who are receiving a donation thanks to the race. That’s great but I could not see the results there – there is a link to a 5K but it is not the AWS one.
Congratulations to 529 who was top with a time of 16:54. As for me, I was 136th – not bad out of 1089 and an improvement on last year by 36s.
AWS did provide finishers with a nice medal, a pair of socks, and a polaroid snap – how retro!
Note: this is a rather personal post and probably not interesting for most people.
2023 was a year of running for me but what next? For runners the marathon always beckons; the most famous races in the running calendar are marathons (London, Berlin, Boston, Chicago, New York and Tokyo) and I felt that if I was ever going to run one, it should be soon as I am an older runner.
In 2023 I ran two half marathons but I knew that a marathon was a much harder challenge. In February 2024 I signed up for the Abingdon Marathon, 20th October 2024. I chose Abingdon because it was flat, and somewhat familiar as I grew up near there and it was my late grandmother’s home.
My son gave me a book called Advanced Marathoning by Pete Pfitzinger and Scott Douglas and known affectionately as Pfitz in the running community. The preface says, “the runners for whom we wrote this book have goals such as setting a personal best, qualifying for Boston, or running faster than they did 10 years ago.” A bit ambitious for me but then again, I did want to run London one day and “good for age” looked like my best bet for getting in.
The book was excellent for me because it is science-based and the rationale for everything in it is explained in matter of fact terms. There are many ways to train for a marathon and our knowledge of how best to do it continues to evolve; but the schedules in this book are well proven. I picked the easiest training schedule which is called 18/55: an 18 week schedule in the which the maximum miles per week is 55. I counted back from my marathon date and put the mid-June starting week in my diary.
I had to pick a target pace since the schedule paces are derived from this. There were two factors. One, what was I capable of doing. Two, what did I need for London. I picked 8:30 per mile; somewhat arbitrary but I hoped it would work on both counts.
In a table of “sample long-run paces” on page 14 of the book, 8:30 is the slowest pace given for “marathon goal pace.” I felt therefore that I was picking the slowest pace which the authors felt was in scope for the book, though this is not explicit.
Incidentally I switched mentally from per KM pace to per mile pace because this book and many other marathon training guides and discussions primarily use per mile paces. The KM equivalent is always given but there is a bit of friction. I also came to prefer using the longer distance for my mental segments.
Note that you are not meant to start even the 18 week schedule from scratch. “These schedules are challenging right from the start and get harder as your marathon approaches,” say the authors. You need to be in what one might call half marathon fitness before you start.
Following the schedule
Although the schedule is 18/55 most weeks are fewer than 55 miles. The mean is about 40.5 miles. It is still a big commitment. Let’s say one averages about a 9:30 pace in the training; that is about 6:45 hours running per week, spread over 5 training sessions. Add on a bit of time for changing and showering and it is a lot to fit around a working week, and demanding for family and friends too.
When I trained for a half marathon I did so quite informally. A long run on Sunday and a daily jog, including parkrun on Saturday. I was sufficiently scared of the marathon that I decided to follow the schedule as closely as I could.
That said, I did not follow it exactly. For one thing, I carried on with parkrun and mostly ignored what the schedule offered for Saturdays. Second, I had races scheduled and these conflicted with the Sunday long runs. I worked around this either by adding a second run after the race (since the races were shorter than the scheduled long runs), or sometimes I just treated the race as the long run.
I did make sure to include four key long runs in the schedule. These were three 20 mile runs, and an 18 mile run with 14 miles at marathon pace. For most of these runs I actually did a bit more than the scheduled distance; it is quite hard to do them exactly unless you do the same route out and back and turn back home at half way. I preferred to do circular routes and in practice my longest run was between 22 and 23 miles.
I entered all the training runs as workouts on my Garmin. My “execution score” which measures how well I conformed to the scheduled pace was typically poor. One reason is that I live in a hilly area and it is hard to keep a pace. Second, I found it difficult to run slow enough for the recovery, warm up and cool down sections. Third, I found it hard to make the target pace especially early on in the training.
It sounds cruel, but the training runs often have you running at the fastest pace at the end of the run. The Pfitz “marathon pace” sessions for example get you to run say 5 miles at easy pace then 8 miles at marathon pace. The idea is to adapt your body to be able to maintain the pace when fatigued.
I was fortunate not to suffer much illness during the period. I picked up a bug when on holiday in July. I had to stop training for a few days but then resumed.
Core strength training and avoiding injury
Having suffered from plantar fasciitis and a second foot injury I was conscious of the risk during intensive training. There is a chapter in the Pfitz book called supplementary training and I regarded this as equally important as the training schedule. The reason is simple: if you do not do the core strength training you are likely to get injured, and if injured, you cannot train. A further benefit is that the strength training directly improves your running.
I followed the section called Core stability training and combined the exercises with others I had discovered, developing a workout that took around 40 minutes to complete, and doing this most days.
I did not experience any major issues with feet, calves or hamstrings during the training or indeed during the race and I feel that this is thanks to this exercise programme.
Tapering
The taper period in my schedule was the last three weeks. 20 mile run on the Sunday before, then a gradual reduction in mileage. Taper is known to be a difficult time and I had some little issues. One is that I had booked a half marathon race two weeks before, when the schedule said to do a 17 mile long run. I decided to run the half marathon as a training run, not at race pace.
The coach at my running club supported this, telling me an anecdote about a woman who missed qualifying for the commonwealth games after winning a half marathon two weeks before the marathon at which selection was decided. Her rival came second in the half, but won the second race and was duly selected.
I did not doubt the quality of the advice and started determined to run no faster than 8:15 per mile. With the race atmosphere and amongst the other runners I found myself running at 7:58. I slowed a little and did the second mile at 8:01. Then I was keeping pace with a friend from my club and chatting. He pulled ahead of me and I could not help myself, I stayed with him, then a few miles later passed in front. Mile 7 I did at 7:12. In the end I finished in 1:39:43 which was a half marathon PB for me – but what about the taper? What about my lack of self discipline?
After that I followed the taper schedule religiously, even skipping parkrun 8 days before the marathon because it was designated a rest day. It was a big change for me though, after 16 weeks of hard running. It felt like losing fitness.
In the week before the race, there was another issue. Weather. The forecast for 20th October was rain and strong winds, gusting up to 40 mph or so. The Great South Run in Portsmouth, scheduled for the same day, was cancelled. People signed up for Abingdon or the Yorkshire marathon (again same day) posted on Reddit about how to run in bad weather. It was hard not to be anxious. Perhaps the event would be called off, and all my training in vain. Perhaps a howling gale would make getting a good time impossible.
In the event, the weather was poor but not as bad as predicted. Phew.
The race
I did my best not to leave anything to chance. The day before, I ate a big spaghetti lunch before heading to the race hotel in Abingdon. Then a light evening meal with no alcohol, just a big glass of orange juice. On the morning, I got up at 6.00am and ate two bread rolls with jam. The idea is to go into the race well stocked up with the right kind of nutrition and well hydrated, but not to have toilet issues. Therefore one has breakfast three hours before the race.
I decided to run with minimum baggage. This meant leaving my smartphone behind, relying on the drink stations for water, and carrying only gels. I had running shorts with two deep pockets in which I stuffed 7 SIS isotonic gels, the same ones I had used in training – following the principle, nothing new on race day.
The course starts on the race track at Tilsley Park to the north of Abingdon. I arrived at about 7:45am and had a look round. It was somewhat bleak and the inflatable start/finish arch was not yet pumped up.
Tilsley park two hours before the start of Abingdon Marathon 2024
The venue was well organised though and complete with changing rooms. There was light rain but no gales. I got ready, and chatted to some of the other runners. The time slipped away; I had intended to do a short warm-up jog but a long queue for the bag drop meant I ran out of time. Headed to the track at around 8:45am; the sound system was not working very well and it was hard to hear the pre-race brief. The runners intending to finish in under 2:30 were encouraged to start near the front but any plans to sort other runners into pace groups seemed to be abandoned.
A few minutes later we were off. It is hard to describe but this was an emotional moment. I realise I am only a mid-pack club runner but 18 weeks intensive training leading up to this made it a big deal for me.
There was a little bit of congestion but this was a smallish race (fewer than 1000 runners in the end, some who had booked perhaps did not turn up because of the weather forecast) and it was not a big problem.
It did feel odd trying not to run too fast. Sam Murphy writes in her book Run your best marathon:
Research has shown that when marathon runners begin the race at a pace that is just 2 per cent quicker than their practised goal pace, they flounder over the final 6 miles. The reason this advice is so often repeated is because it is so rarely heeded.
Running a race induces something similar to flight or fight response where the stress of the occasion enables the body to out-perform. The race atmosphere and one’s determination to do a good time drives you to run as fast as you can; yet one knows that holding back is vital. It is a mental battle. “This feels peculiar, trying not to run too fast” I said to another runner and we chatted. A side-effect of deliberately slowing your pace is that you have more breath for talking.
But what was my target pace? I set it originally at 8:30. Calculators like VDOT said that based on my half marathon two weeks before, I could do 7:55 but I felt that was risky and over-optimistic. Nevertheless I had decided to try and go a bit faster than 8:30. I kept a close eye on my Garmin. If the pace went up above 8:15 I consciously slowed down. If it went below 8:30 I tried to speed up.
The race begins with a run east and then south into Abingdon. At about 5 miles I passed the house where my grandmother used to live, in the beautiful old town.
5 miles in, running past the house where my grandmother used to live in East St Helen’s St, Abingdon
Then you run out of town, and start a two-lap section where you run through a village, on into Milton business park, and back through a pretty village called Sutton Courtenay (where Eric Blair, also known as George Orwell, is buried).
The first 10 miles were a breeze. I chatted to another runner who said he was targeting a similar time to mine, around 3:40. Had he run a marathon before? Oh yes, he ran Manchester marathon in April in 3:18. You will be well ahead of me then, I said; but he thought he had not kept up his fitness. We ran together for bit, then he went ahead as expected. However he told me that I looked fit which was nice of him!
As it turned out I met him again in the latter part of the race and ended up finishing a minute or two ahead.
During the two lap section you see mile signs for the second lap as well as the first; that is, you see a sign for 16 when you are really on mile 8 etc. I do not know if this was part of the reason but miles 10 to 13 seemed to take ages and I was beginning to feel a bit of fatigue. I was keen to get half way, telling myself that it was downhill after that.
Mile 13 appeared eventually and I entered what Pfitz calls the “no-mans land of the marathon. You’re already fairly tired and still have a long way to go.” The book says that this is where you can easily lose pace; but I did not. The reason was that I was keen to pass 20 miles – the moment at which, some say, the marathon really begins.
I am not sure what it is about 20 miles but it is the point at which many runners find themselves having to slow down. Often they say they “hit the wall” though what runners mean by this varies. Sometimes it means literally being unable to run any further, more often it means losing pace or entering a run/walk phase.
Pfitz brilliantly calls the last 6 miles “the most rewarding part of the marathon … this is when your long runs, during which you worked hard over the last stages, will really pay off. Now, you’re free to see what you’ve got … this is the the stretch that poorly prepared marathoners fear and well prepared marathoners relish.”
I think this is brilliant because it sets you up mentally to look forward to the last 6 miles, if you have followed one of the book’s schedules, making it less likely that your pace will fail.
In my case mile 22 was my fastest mile, the only one under 8:00 according to the Garmin. In general though, while I did not really speed up, I did not slow down either.
The last two miles though were tough. I was extremely fatigued. Then again, I knew I was within reach of my goal time and determined not to stop now. I was also concentrating on not falling over. The Abingdon marathon is run mostly on open roads and you have to move between road and pavement, it would be easy to trip over a kerb when fatigued and your running form is slipping.
I passed the 25 mile sign. Then I was on a half-closed road and the marshalls were saying “not far now.” I entered Tilsley Park and then back onto the track. 600m to go. Tried to put in a little burst of speed at the end though there was nobody to overtake, or trying to overtake me. Then it was done, and a boy scout apologetically handed me my medal, not being tall enough to reach up and place it around my neck.
The finish
I placed 485 out of 995 finishers, and was 14th out of 44 in my age group 60-69. My time was 3:37:16 which is a pace of 8:18 per mile; however I feel a sense of achievement which is out of proportion to the actual result.
It may also be true that keeping pace right to the end means that I could have gone faster; it is difficult to know but perhaps, next time, I will risk holding back a little bit less in the early miles.
I have mixed feelings about this book, first published in 2012. Most runners want to run faster. But how? Julian Goater, 1981 National Cross Country champion, shares his insights in this title.
With a mixture of anecdote and specific training advice, he expands on six components of fitness: speed, suppleness, strength, stamina, skill and psychology. Some of his advice is uncontentious: do core strength training, for example, and do different types of training sessions including fartleks (short bursts of speed within a run), intervals, long runs and recovery runs. He is a enthusiast for cross country because “it gives you all-over, full-body fitness and resilience that will help you enormously when you run on quicker surfaces.”
All the above makes sense to me, but I am less sure about his advocacy of training twice a day. “To fit in the variety of training sessions you need, run twice a day most days,” he writes. This is not to get in more mileage overall, but more variety of short sessions.
Goater’s overall philosophy seems to me well summarised in a quote he references from Olympic gold medalist Sebastian Coe: “I’ve always felt that long, slow distance produces long, slow runners.” Goater feels that runners all too often get in plenty of miles but get too comfortable running at a steady pace and do not do enough speed work; and speed work, he says, must be above race pace otherwise it is useless. In fact it must be well above race pace. “To be effective, even your slowest speedwork should be done faster than your best pace for the distance below the one you are aiming for. If you are training for 10K, run your long sustained-speed repetitions at a faster pace than you can sustain for 5K,” he writes.
The author also states that “ideally, at least 80 percent of your running should be done at a comfortable cruising pace – but not just jogging.” So he is not recommending speedwork above all else.
I did enjoy the book and especially Goater’s recollections of Coe, David Bedford, Steve Cram and other runners of his day. I think it could help me to run faster, if only thanks to his insistence on purposeful training and encouragement to put in more effort.
That said, I note the lack of references to scientific studies of the impact of different types of training. Rather, Goater relies on his own experience as a runner and a coach.
A good book, but best read alongside other more rigorous training guides.
I like this book and recommend it, perhaps even for those not intending to run a marathon, or not yet.
Murphy is a runner and journalist, and takes the trouble to explain the science and to back up her statements with references to credible research. This is important because there are a surprising (to me) number of unresolved questions for those who want to optimize their running. Stretching, for example, before or after a run. “I’ve yet to find any evidence that stretching – of any kind – actually makes you run faster,” says Murphy. Does it reduce injury? “No clear effect,” she writes; but adds that there is evidence that if you think it helps, it does.
I would still call this matter of stretching unresolved. Julian Goater and Don Melvin, in their 2012 book The Art of Running Faster, have an entire chapter on the subject and say that “You do need to stretch – regularly … in my experience regular stretching is the key to avoiding injury.”
Murphy also has a down-to-earth section on how to choose trainers. “Many of the claims made about how shoes can protect or correct your feet are exaggerated or just plain wrong,” Murphy writes, with reference to research. She does confirm though that those super expensive carbon-fibre plate shoes are faster, but also notes some downsides. Comfort is the most important thing, she feels. I also like this great tip: when buying shoes, take out the insoles and stand on them. “Your whole foot should be within the boundary of the insole,” she says, otherwise you will have cramping which can be a disaster (it was for me).
The book takes the reader through the art and science of training, and then offers a set of training plans. She categorizes the plans as full throttle (training five days a week), steady state (mostly four days a week) and minimalist (mostly three days a week). In each category there are plans for experienced, and first timer. Runs are described as easy, tempo, marathon pace and so on; but you have to work out the exact pacing yourself, for which there is extensive guidance, as this depends on your capabilities and targets.
These schedules are not as demanding as those in the classic book Advanced Marathoning by Pete Pfitzinger and Scott Douglas, nor is Murphy’s book as technical. Experienced runners would likely benefit more from the Pfitzinger and Douglas book; yet having read both, I still found Run your best Marathon useful.
Where this title wins though is in its approachability, down to earth style, and coverage of those small details which experienced runners seem just to know, but rarely explain. This is especially true in the second half of the book, about practicalities, body maintenance, how to choose a race, and nutrition/hydration. There is advice on exactly what to eat and drink, and how much, even down to tips like how to drink while running, without choking or coughing. There is also a complete checklist of what you might need for race day, though I am not sure about the bin liner she suggests for keeping dry before the race!
The book is very approachable and especially suitable for those contemplating their first marathon (as I am). Much of it applies to other distances as well, certainly longer runs of 10 miles or more, and there is so much general running advice that it may be worth a read even for those who have no intention of subjecting their bodies to a gruelling 26.2 mile race.
I picked up this book, sub-titled “Adventures in late-life running”, because it seemed a good fit for my own situation, having taken up running as I approach retirement age.
It is not quite what I expected. Askwith’s first love is fell running, which he used to do intensively when younger. He recounts in the first chapter how he returned for a reunion fell run, now in his early sixties, and his reflections on the toll of age on his performance and that of his friends. 12 of them came for the reunion but only 4 actually ran, the others declaring themselves unfit for more than walks and socialising.
What we get in the subsequent chapters is a series of portraits of older runners, most much older than their sixties, backed up with interviews: why do they run in old age, how do they train, what is their story?
There are also interviews with experts on the subject of old age and fitness, and the whole book is punctuated with Askwith’s reflections on aging, mortality, and a few of his own recent experiences of running.
Curiously this is a book which I enjoyed less as it went on. Askwith’s constant self-deprecation becomes tiresome, and he seems almost unaware of the frustrating contradictions which he presents. How much should you train? Not too much and focus on HIIT (high intensity interval training) according to an interview with Peter Herbert. – you can read more about his approach here. Yet we also hear from the amazing Tommy Hughes a world record (for age) marathon runner and how he runs 20 miles a day in training. Or by contrast Angela Copson, who according to the book hardly trained at all for the 2007 London Marathon, other than running alongside her husband riding a bike, but achieved under four hours as a sixty year old woman.
It is all fairly confusing if you come to the book looking for advice on how to run well as an older person; and in fact you should look elsewhere for that kind of advice.
On the other hand, Askwith does put in the hard work of going out and interviewing numerous interesting older runners and for that, the book is well worth a read.
I started running nearly two years ago and until recently have been injury-free. In February I purchased some new running shoes, similar I thought to ones I had already. The first time I wore them I had some numbness in my left foot but put it down to wearing in. I wore them twice more; the second time they felt better, the third time I was training intensively and it was a disaster. I ran fast but was in pain walking home, mainly in my left foot.
Never again did I wear those shoes; but what had happened? I did some research and discovered that while the shoes I had bought were well rated in general, they were known to have a narrow toe box. Ouch.
I thought that having ditched the shoes all would be well. I continued to run and found that I got a bit of pain to begin with after which it felt fine. Unfortunately matters did not improve; the pain got worse, persisted longer, and I began to have issues walking as well. I realised I had a serious problem, from a running perspective at least. I suspected a thing called Plantar Fasciitis (misnamed because generally not an inflammation) which causes pain on the inside of your heel, where the plantar fascia, a strong piece of connective tissue, joins the heel.
I purchased orthotic insoles which helped to releive pain walking. I started cycling more, in order to keep fit while running less. And I also did a ton of research, discovering to my alarm that Plantar Fasciitis is notorious for lingering for months or even years; and that there appears to be no consensus about how to treat it.
It is a small problem in the context of many worse things that can happen but seeing my plans for a summer of running perhaps in tatters was not a good feeling.
The nadir for me was approximately one month after the injury. I attempted a 5K parkrun and just after 1.5K experienced such intense pain that I abandoned the run and limped to the bus stop. This was almost exactly one month after the injury began.
Plantar Fasciitis: things I learned
This is a common injury mainly affecting two groups of people: runners, and people who are on their feet a lot at work. It is somewhat more common in females but I am a typical sufferer being an older person who has ramped up their running relatively quickly.
While it is easy to diagnose likely plantar fasciitis, knowing exactly what is going on requires an MRI scan (I have not had one). I wanted to discover how to treat it and when I could get back to running; and discovered instead that neither question is easy to answer. In fact, I was surprised how much variation and contradiction there is out there.
Note: none of what follows is advice.
There seem to be two divergent approaches, one of which is focused on support, the argument being that resting the foot and wearing footwear that has heel cushioning and firm arch support will allow the foot to heal.
The other is focused on strengthening, the idea being that the problem occurs because of weakness in the foot and leg. Supporting the foot with insoles tends to make it weaker rather than stronger.
Regarding running with plantar fasciitis, there are arguments for not running until it is completely healed, or that it is OK to run provided the pain is only moderate and that it is no worse the next morning.
The risk of not running is that one loses fitness, though this can be mitigated by other types of activity such as cycling and swimming. The risk of running is that it could make the injury worse.
There are certain things though which are widely agreed. One is that the plantar fascia is just one part of a complex and wonderful system which includes toes, ankle, calves and glutes.
Until now I had taken my ability to walk and run for granted. I have always been a fast walker and assumed that my feet and legs would look after themselves. I now realise that they deserve some love and attention.
Although there is no consensus regarding orthotic insoles, there is reasonable agreement that stretching and strengthening exercises do speed healing.
How I have been treating my plantar fasciitis
Again, this is not advice, only a record of my own experience. I felt instinctively more drawn to the arguments for strengthening rather than support. I read every article and forum thread I could find, with particular interest in reports from others on what had worked for them. I even ventured into the hellhole of YouTube which of course has a million videos all promising quick relief – but it is always worth reading the comments.
I found the insoles did help early on, making walking less painful and running less risky, but resolved to wean myself off them as early as possible.
I obtained some minamalist barefoot-style shoes from Vivobarefoot. It was not just this post from the vendor; I saw other reports saying they were beneficial. Others said they made it worse. In general this is a big subject and merits a separate post; however note that I am not running in these shoes, only wearing them for day to day use. It took some adjustment but I find them comfortable.
I collected some exercises and did them intensively. They take about 25 minutes and I do them three or four times a day. They include:
Toe exercises. The big toe is part of the windlass system which includes the planter fascia.
Calf stretching exercises.
Glute strengthening exercises.
Using a resistance band to strengthen the toes and foot.
At first I thought nothing was changing. Three weeks later though, I noticed that I was much improved. I no longer found the first steps in the morning painful. I could walk almost normally. I even tried a tentative run without insoles and it went OK. I resolved not to run with pain higher than a 2 (on a 0-10 scale) and have followed it.
I am two months on from the injury now. I cannot say it is fully healed, but it is now mild and I am runnning almost as normal. I no longer use the insoles. I am keeping going with the exercises though; I do not know which of them is working, but something is helping. Or perhaps it would have got better anyway; it is never easy to be sure.
Some references
NICE (National Institute for Health and Care Excellence) clinical knowledge summary for plantar fasciitis. Recommends resting the foot, not walking barefoot, shoes with “good arch support and cushioned heels”, weight loss, symptomatic relief with an ice pack. Regarding insoles, states that “foot orthoses are widely recommended on the basis that they benefit foot posture and aid fascia healing. However, there is little evidence to support this.”
5 methods to manage plantar fasciitis – based on research though with limitations. Inconclusive but questions the benefits of strength training. Also found that custom-made insoles (much more expensive) are no more effective than off the shelf (cheap).
Detailed look at plantar fasciitis, what it is and how to treat it, from American Orthopaedic Foot and Ankle Society. States that “more than 90% of patients achieve symptomatic relief with 3-6 months of conservative treatment.” Advises that “stretching of the gastrocnemius muscle is a mainstay of treatment of PF.” Positive about insoles stating that “both prefabricated and custom-fitted orthotics have been shown to reduce pain and improve function in the short term with few risks or side effects” though note “short term.”
Can you run with Plantar Fasciitis – I quite like this thoughtful piece though it is inconclusive regarding the question posed in the title. Also quotes research which states, “At the moment there is limited evidence upon which to base clinical practice.”
I was a smartwatch holdout for many years, on the basis that the short battery life would be annoying (my previous watch had a 10 year battery) and that the utility of a smartwatch is limited; mainly I just need to know the time. The big feature of a smartwatch of course is health tracking but that was not something I felt I needed.
Two and half years ago I succumbed and bought an Apple Watch 7, partly to see what I had been missing, but it also nearly coincided with taking up running.
Apple Watch during a run
I used the Apple Watch from mid-2022 until January this year, to track my runs and monitor my fitness. If you are a runner you will know that you want to track your pace and distance as part of training, and if you have any interest in the data and science of running, then other things like heart rate zones, V̇O2 max and so on.
There is also the matter of listening to music while running. I enjoy this, though earbuds are controversial because of the need to pay attention to your surroundings especially on roads with traffic. I am a fan of bone conduction headphones which let you listen without blocking your ears at all; and UK Athletics, the official body for running, permits bone conduction headphones in races at the event organiser’s discretion.
The integration between the Apple Watch and iPhone is not as smooth as you might expect when it comes to music, or perhaps it is just a hard problem. If you have headphones paired to the iPhone you can control the music from the watch, but you will not get announcements about your pace and distance progress. The solution is to pair the headphones to the watch and not to the iPhone. Then you get both music and announcements, by default every km or mile (depending on preference) you are told your pace. There is also a buried setting that lets you set a playlist for workouts, that starts automatically when you start the workout and can play in random order. In case you have not found this setting, it is in the Watch app on the iPhone under Workout – Workout Playlist.
That all sounds good, but I gradually got frustrated with the Apple Watch for running. Here are the specific issues:
Starting a run (or other workout) is a matter of pressing the side button, selecting workout, scrolling to the workout you want (usually Outdoor Run for me), and tapping. Depending where you tap, you may be asked what type of run you want, open, goal-based, route, or all. Or it may just do a brief countdown and start. All sounds reasonable; but imagine that it is a cold wet day, you are wearing gloves, and about to start a race. Scrolling and tapping successfully is difficult with gloves and worse in the rain. All the above is fiddly, when what you want to do is just start the workout and get on with the race.
GPS accuracy I found not very good, especially early on when I had an iPhone SE. It would consistently under-report the distance so that a 5K race showed as 4.8K, for example. Apple Watch has GPS on board but version 7 and earlier use the GPS on the iPhone to save battery, when available. I replaced the iPhone and accuracy improved, so perhaps I was unlucky, but I still noticed anomalies from time to time. In fairness, it can be difficult with things like trail running under trees and so on.
Annoying bugs include the watch starting and ending run segments for no reason I could see, music volume resetting after a pace announcement, music playback occasionally not starting, and worst of all, the workout ending before the end of a race despite turning off the auto workout start and stop features (which never work reliably). Most of the time it worked but I never felt I could completely trust it.
Battery life is an issue. If you leave the default of the display being always on, the Watch 7 will barely last a day, and less than that if you run with music. It will do a half marathon if you start with a good charge but not a full marathon (not that I have done one); but I did find it running out of charge when training towards the end of the day. I gave up on sleep tracking because it was easiest just to stick the watch on the charger all night; with a bit of discipline you can charge it before heading to bed but of course that will mean it is not fully charged the next morning. I set the display to be off by default which improves matters a lot.
Most runners wear other types of watch, the most common being a Garmin. In January this year I decided to try a Garmin and got a Forerunner 265, a mid-range model.
Garmin differences and advantages
Garmin Forerunner 265
The Garmin has a button top right labelled Run. Press it and it searches for GPS; when found it goes green. Press it again and the run starts. Press it again and the run stops. It is easy to operate even with gloves and in rain; and touch control is disabled during workouts so there is no risk of inadvertent taps – which are a possible cause of some of the Apple Watch issues.
The second big improvement with the Garmin is the battery life, which is around a week. That means I can track my sleep and the watch is ready for a marathon (even though I am not). Battery life does reduce if used intensively, for example with GPS and music, but still a vast gain over Apple Watch.
Music is a bit of an issue on the Garmin if you use Apple Music, since it is not supported. The only solution is the old-school method of copying MP3s to the device. On Apple Garmin makes this difficult by insisting you use Garmin Express, which only recognizes the “iTunes” library, now Apple Music. I still have a ton of CDs ripped to FLAC and my solution is to select some FLAC files, copy them to a temporary location, convert them to MP3 (I used ffmpeg), add them to the Apple Music library, copy them across with Garmin Express, then remove them from the Apple Music library. There is probably an easier way.
On the plus side, music playback works really well and I do not get the volume issues I had with Apple Watch. Tracks are shuffled by default though the algorithm seems not quite as good as on Apple Watch, and tracks can repeat too soon. There is no auto-start. Controlling music is easy: just hold down the bottom left button and the music screen appears. As with Apple Watch, you get pace and distance announcements as well as music.
Fitness statistics are better on the Garmin. V̇O2 max and heart rate zones is an interesting one. V̇O2 max is an interesting statistic but not essential to know, but heart rate zones are important to training. All these figures depend on the “Maximum heart rate” (MHR) which is traditionally calculated as 220 minus age. However this formula is a crude way of calculating MHR as it assumes everyone is roughly the same, which is not the case.
Apple Watch gives you the option to enter your own MHR rather than use the formula. However it’s not that easy to find out and will change over time so that is not ideal.
The Garmin though will auto-detect your MHR which strikes me as a better approach. According to the docs:
Auto Detection can calculate your maximum heart rate value using performance data recorded by the watch during an activity. This value may differ from an observed lower value recorded by your watch as the feature can determine a different value based on a proprietary algorithm.
In my case I seem to have a higher than average MHR and as a result the Garmin is giving me more plausible data for heart rate zones and V̇O2 max. Note though that smartwatches are not reliable for this and as the Garmin docs also say “the most accurate method to measure your maximum heart rate is a graded maximum exercise test in a laboratory setting.” There is also a suggestion for calculating it with a running test.
I still think the Garmin auto detection is preferable to the Apple Watch approach. In practice the Garmin has given me a higher figure for both V̇O2 max and MHR.
The Garmin is more pro-active than Apple Watch in assessing your fitness and making recommendations. There are features like Training Readiness, Stress measurement, Body battery, and more. When you start a run, the Garmin will recommend a training run or recommend that you rest instead (you can disable this feature if you prefer). The Garmin will also assess the Training Effect of a run, divided into aerobic and anaerobic impact scores. Another interesting metric is recovery time which assesses how long you need to rest before another high intensity training effort. It is hard to say how reliable these various indicators are (and there are more that I have not mentioned) but I feel they have some value, and should improve in accuracy over time.
Apple Watch advantages
The Apple Watch is a general-purpose smartwatch, whereas the Garmin is a fitness watch and the Forerunner series designed specifically for running – so it is not surprising that the Garmin has advantages for runners.
The Apple Watch looks nicer and less geeky, and as you would expect integrates better with an iPhone. Features like Camera Remote are handy, as is turn by turn directions. You can dictate a message into the watch, which is not possible with the Garmin. I miss the integration with Apple Music.
Apple Watch workouts appear on the paired iPhone under Fitness. If you integrate with Strava you can choose which workouts to import from the Strava app. If you integrate the Garmin with Strava it either imports all, or none of your workouts. This is a nuisance as it clutters Strava to import every single little workout or repetition. The best workaround I have found is to import none, and then import the ones you want manually via export from the Garmin Connect web application. Another idea is to import all, and immediately delete the ones you do not want. Either way, Apple Watch is preferable in this respect.
Price-wise, a Forerunner 265 costs £429.99 which is more than a basic Apple Watch 9 at £399 and much more than Apple Watch SE at £219. The Apple Watch Ultra though, which I understand is better for fitness tracking, is much more expensive at £799. Even the high end Garmin Forerunner 965 is less, at £599.99. There are cheaper Garmins as well: the Forerunner 255 is apparently a decent choice at £299.99, with most of the features of the 265 but an inferior screen and no touch control.
Some reflections
I am writing from the perspective of a runner. I do not think you should consider a Garmin over an Apple Watch if you are not looking for a sports watch. Then again, I still feel that smartwatches have disappointing utility if you exclude the fitness/health tracking features.
That said, the Garmin does illustrate the advantages of physical buttons over touch control, and the greater efficiency of a custom embedded operating system over iOS (or strictly, Watch OS).
What is the Garmin OS? There are some clues in this 2020 interview with one of the developers, Brad Larson, who said it is “a full custom OS … OS is almost stretching it. It doesn’t support multiple processes, it does threading and memory management but it doesn’t multi-process, but that’s what’s necessary. Most of our codebase is still in C … we’ve been pushing for the UI framework which sits on top of everything to be C++.”
I do not know how much has changed since then but suspect it would be a disaster if Garmin were to adopt Android Wear OS, for example, with the inevitable bloat that would come with it.
It also seems to me that Apple could significantly improve its watch from a running perspective with a little effort, applying its corporate mind to simple things like the challenge of starting a workout in typical running conditions.
As of now, I recommend Garmin over Apple Watch for running, based on my experience.
I love the Runbritain rankings, other than that the site is not very reliable, because it gives you an indication of your running performance taking into account the conditions. If you run on a muddy course for example you will probably not get a good time, but the same is true for others. The Runbritain rankings take this into account so you can still get credit for your effort, in terms of a reduced handicap. I also like that only your five best performances are taken into account, so you can run slowly with a friend and not worry about harming your handicap (if indeed you ever worry about such things).
How does it work? I found it quite confusing. There is a video explainer by Tim Grose, one of the two leads for the team at Athletics Data that developed the rankings, but even this is not super clear in my opinion. The problem I think is that the normal view in the Runbritain ranking table for an athlete gives you, aside from the race name and time, two figures, SSS and vSSS. The SSS is the “Standard Scratch Score” and measure the state of the course, where zero is pretty much perfect and anything above 4 is fairly bad. 10 is the maximum and apparently it could be slightly negative though I have never seen that.
On a 5K such as a parkrun, each point is worth about half a minute so a score of 4 would mean most people are two minutes slower than they would be on a perfect course.
Second, the vSSS or virtual Standard Scratch Score shows how well you performed; this can be negative. More on this later.
These two figures though do not show you how the handicap is calculated. Handicaps run from maybe -10 (the lowest currently is -7) up to 54, based on golf handicaps, where lower is better. Imagine that you run a 5K parkrun in 25 minutes. This performance represents a basic handicap of 19.3 before adjustment, a figure calculated from senior age gradings but without looking at your age. Runbritain handicaps do not take account of age; they are purely about how fast you are in absolute terms. The exact table is not given though you could easily work it out.
This handicap is then adjusted based on two things, the SSS and the time penalty. The time penalty starts at -1.5 and gradually increases. To give an idea, an event one year ago has a time penalty of 2.5. So if you ran a 5K parkrun in 25 minutes today, and the SSS was 2.0, that would give you a handicap of:
19.3 -2.0 -1.5 = 15.8
If that event were a year ago it would come out at:
19.3 -2.0 + 2.5 = 19.8
Your final handicap is the average of your best 5 handicaps after adjustment.
Since the vSSS is not part of this calculation, why is it shown? Well, it is kind-of part of the calculation because of the way SSS is calculated. Runbritain rankings does not go round inspecting each course and judging its condition. Rather, its algorithm looks at the results and at how each athlete did versus their best time (best handicap). This figure is called MySSS. So if you equalled your best time it would be zero, if you improved on it (PB or Personal Best) it would be negative, and if you ran slower than your PB it would be positive.
The algorithm looks at the MySSS for all the athletes and the middle one (median) becomes the SSS. Then your vSSS is your MySSS less the SSS.
There may be some slight inaccuracies in the above description but I believe the gist of it is correct. Grose refers to things like “mildly progressive” that suggest some small further adjustments.
Any flaws in this approach? I can think of a few. One is that athletes tend to perform worse as they age, so their performance versus their best time will likely widen as the date of that “best time” recedes into the past. I am not sure that Runbritain rankings takes that into account and if it does, Grose does not mention it.
Another is that there are many reasons for slower performance that are not to do with course conditions, such as illness, parkrunning with a pram, tailwalking (going last to sweep up any runners who have difficulties), and more. This presumably is why Runbritain rankings uses the median MySSS and not the mean, to calculate the SSS, but it will never be perfect.
A third issue is that parkrun is not a race – well, some treat it as a race and try for their best time, others more as a social event with dogs, prams, and chatting to a friend as they run. Nothing wrong with either approach, but that will impact the SSS and implies that someone who tries their hardest in a parkrun may have too low a handicap.
Despite imperfections though the system does work and I find it reassuring, after getting a slow time in bad conditions, that the Runbritain rankings view may show it in a more positive light.
I am not sure exactly when I became a runner, nor for how long I will be one. But I am sure that when I think back over 2023 from a personal point of view, running is the first thing I think about.
Pic courtesy of Microsoft Paint Cocreator AI
Most of us discover the need for exercise at some point in our lives and for years I have been in the habit of doing a short daily workout, hardly even a workout, but based on the old 5BX plan which takes all of 11 minutes. 5BX includes running on the spot which is effective but quite boring. I replaced it with going out for an actual short run and omitting the jumping jacks.
Then a couple of things conspired to persuade me to do more running. It was partly a side-effect of lockdown, when my wife who was on furlough did the NHS Couch to 5K programme which was followed by an addiction to Parkrun, free 5K runs which take place every Saturday morning at numerous locations around the UK and some worldwide.
Second, an event called the Winchester Half Marathon passes our house and I found myself thinking that I would like to do it myself.
I decided that I might as well join in with the Parkrun and soon enjoyed the challenge of trying to improve my time week by week. That began in July 2022.
I was enjoying it enough that in April 2023 I booked myself into the Winchester Half for September. That gave me 6 months to train, more than enough. I increased my daily run to a 15 minute hilly run three times round the block near my home. I started doing a long run on Sunday mornings, working up from 8K to 10K to 12K and up to 20K, just short of the half marathon distance.
The Winchester Half is somewhat hilly so I booked for the flatter New Forest Half Marathon earlier in September as a practice. That went OK despite rain and I finished in 2:03:50. Winchester went a bit better and I did 1:58:27. Ambition fulfilled.
I was enjoying it too much to give up though, and since then have joined the local Winchester Running Club and booked for several more events next year. I also did the AWS re:Invent 5k in Las Vegas which was fun if a little odd in the way it was organized!
I have started running relatively late in life and wish I had done it earlier; but it is also fun to do something new. Often I meet people who tell me they also loved to run but had to stop due to injury, sometimes knees, sometimes something else. I do not think running is risk-free but I am convinced that it is more likely to do good than harm. I have just read Daniel Lieberman’s book Exercised; Lieberman is a professor of biological sciences and writes that “the negative effects of too much exercise appear to be ridiculously less than the negative effects of too little.”
Even the risk to knees is not clear-cut. “Physical activities like running that load joints repeatedly and heavily do not cause higher rates of osteoarthritis and may sometimes be protective,” writes Lieberman, referencing a 2008 study in the American Journal of Preventive Medicine.
There are consequences though. I have lost weight. My resting heart rate has slowed. And it is time-consuming, especially if one trains for the longer distances.
I realise though that I may not always be able to run. That for me is all the more reason to run while I can.
Sunrise over Las Vegas – at the re:Invent 5K run 2023
It happens that, a little later in life than most, I have taken up running, and during the recent AWS re:Invent in Las Vegas I was one of 978 attendees to take part in the official event 5K run.
If there were around 50,000 at the conference that would be nearly 2% of us which is not bad considering the first coaches to the venue left our hotel at 5.15am. The idea was that you could do the run and still make the keynote I guess – which I did.
I would not call myself an experienced runner but I have taken part in a few races and this one seemed to have all the trimmings. The run was up and down Frank Sinatra Drive, which was closed for the event, and the start and finish was at the Michelob ULTRA Arena at Mandalay Bay. Snacks and drinks were available; there was a warm-up; there was a bag drop; there was a guy who kept up an enthusiastic commentary both for the start and the finish. The race was chip timed.
We started in three waves, being fast-ish, medium, and run/walk. I started perhaps optimistically in the fast-ish group and did what for me was a decent time; it was a quick course with the only real impediments being two u-turns at the ends of the loop.
Overall a lot of fun and I am grateful to the organisers for arranging it (it does seem to be a regular re:Invent feature).
Here is where it gets a bit odd though. The event is pushed quite hard; it is a big focus at the community stand outside the registration/swag hall and elsewhere at the other official re:Invent hotels. It is also a charity event, supporting the Fred Hutchinson Cancer Center. All good; but I was surprised never to be officially told my result.
I was curious about it and eventually tracked down the results – I figured that with chip timing they were probably posted somewhere – and yes, here they are. You will notice though that no names are included, only the bib numbers. If you know your bib number you can look up your time. The QR code on the bib also links to the results. This was mine.
It seems that AWS do not really publish the results which would have disappointed me if I had been the first finisher who achieved an excellent time of 16:23 – well done 1116!
I can’t pretend to understand why one would organise a chip-timed race but then not publish the results. Perhaps in the interests of inclusivity one could give people an option to be anonymous but for most runners the time achieved is part of the fun. I think we were meant to be emailed our results but mine never came; but even if I had received an email, I would like to browse through the full table and see how I did overall.
