So after the irrational decision making and mild euphoria that accompanied signing up to do a marathon – some time in a land far,far away – and with the excuses of December excess and family celebrations behind me – I found myself at week 1 of training for the marathon.
AKA when shit got real – although I am way too polite to use that kind of colourful language 😉
So it is January 9 and a full 4 months or 19 weeks or 131 days till May 21. By any measurement , quite some time till I have to stand on the start line and ask the question “why I am doing this ?”
Knowing that it is both a serious undertaking and one that I am taking seriously, I was quite excited to read what Sally had in store for me.
Earlier Sally had asked casually – “so you have a Garmin do you?” – to which I replied that no, I did not own a Garmin and actually had a bit of a fear of sports watches.
I tried one a while back but could never understand how to set pace, time, distance, the final frontier – whatever – and furthermore I could not read the screen when I was wearing my contact lenses and as to changing the time when the clocks went forward in Spring – well that was never going to happen!
I am fond of a bit of statistical insight – loving as I do counting the miles covered using my Nike+ app and I am partial to some gadgets, but as my family will testify, I do have some ‘issues’ around technology.
Added to this – when I did run with a sports watch and heart rate monitor, it was constantly beep, beep, beeping at me in a panicky kind of way and I could never get my heart rate into a range that did not suggest I was about to keel off my perch.
But – it turns out that as part of the marathon training we are going to share data and Sally will then adapt my training plan for the following week, depending on how well or badly I am progressing.
She will watch my heart beating,and my little legs running from afar, and be my very own spy in the cab. In the nicest possible way, big sister will be watching me .
So I bought a Garmin.
I could easily write a whole separate post on the subject of the vortex you can descend into when trying to choose a branded sports watch – but let’s leave that for another time.
Back to training. Week 1 plan asked me to do as a start -10 steady miles wearing Garmin and HR monitor – to set a benchmark. I was not too fazed by the prospect of the distance, particularly as the term ‘steady’ sounds nice and cosy, but with hindsight, it might have been a smarter move to go for a short test run wearing the Garmin to get the hang of the controls before attempting ten miles.
Instead I took delivery of the Garmin at around 11am – spent an hour and a bit waiting for it to fully charge then set out on my run.
Sports watches have got better than I remembered and the Garmin Forerunner 25 does look quite smart – if you like that kind of thing. Importantly it has a nice clear face with big numbers and reasonably straightforward interface and menu.
Having never used a Garmin or completed this kind of techno enabled test before – I was not sure if it was OK to stop or if stopping would mess up the readings sent to Sally, or even worse end the run before 10 miles. And if I was pausing it all over the place as I tend to do on my regular weekend meanderings, Sally might think I was fitter, and faster than I really am.
And as this was the first time I was using the watch, I was not completely sure what button to use to stop and start it again !
Having this fear of technology did provide an unusual incentive to just keep running and at a decent pace. I had to abandon my usual whimsical pauses for photos or observations, as this was a serious training exercise 🙂 So I was very pleased to see that after 5 and bit miles I was managing an average pace of just over 9 min mi – fast for me.
But at the turning point I took a risk and pressed the stop button- which it turns out does pause the recording, so I took a few minutes to eat a disgusting gel and then did the return 5 miles. I had opted for a known route – an out into the wind gradual incline , followed by a downhill with wind behind you, return leg.
On the return leg I felt I was properly running like a proper runner – and with the wind at my back and endorphins buzzing I was visualising breezing or at least managing to get through the marathon 26.2 miles ( after some decent training obviously). It was a good feeling to be fit enough to manage 10 miles at an OK pace having been mostly doing shorter runs in December.
Euphorically I reached the 10 mile distance and triumphantly pressed the stop button – kind of hoping for a cheer , but definitely expecting to see some kind of summary of stats. I was keen to see if my heart was working ( even tho obviously it was 😉 and my inner running nerd was firing up to get my report card of pace, cadence, elevation and the like.
But instead of a list of accomplishments – the screen went a bit funny and pixellated and the numbers were all mangled, the display was frozen and no amount of button pressing was making any difference. Even when I got back to the house – the screen was still set in the same way.
Looking on the Garmin support page – it helpfully suggested ‘if screen has frozen try resetting it – but THIS MAY RESULT IN A LOSS OF DATA
Luckily I was also wearing my Nike+ app – so proof that those miles really did happen,even if I still did not know if my heart was working as it should.
So 10 mile run done ✔️- but I did kind of fail the first attempt of training with technology and I sense this may be a recurring theme of this adventure.