A swampy blog of uncertainty, mud and mirth. Weaved together with lyrical reeds of true stories and imagined happenings. What is, may not. What's not, may be. Don't fall in.
Saturday, July 06, 2024
Winter words
Monday, June 10, 2024
Fifth
Monday, June 03, 2024
T minus 6 days
And in the blink of an eye, I have arrived six days out from my first marathon for 2024, the Kirikiriroa Marathon, which has organically become my "A" race. For the non-athletes out there, an "A race" is the main target race that your training is geared to peak you for, but that is not to say it is the only race that is amongst your training. Huntly Half was a "B race" for me, a race that was to be an indicator of progress. There are even races that you could regard as "C races", which are half-workout / half- race. Coatesville Half for me was a clear C race. Waterfront was intended to be a B race, but due to the niggle turned into a C race. All the parkruns are C races for me because I haven't been specifically training for them, either. So despite I've been making pleasing personal bests in the 5km and half marathon in the first half of the year, none of those are with distance specific training with them as an A race target. I say it has organically become an A race because the scheduled formed around it late last year despite having booked it much earlier.
Last year was my first time running the Kirikiriroa course and I did it with a 3:28-3:30 target. However, my lead-in was pestered by niggles and then I paced it poorly and ended with 3:34. Looking back, the goal was probably about right: my 10km time trial indicated a 3:29 time, and a half marathon time trial indicated a 3:23 time. Looking back at the paces on race day, I did all the same silly mistakes. My pace for the first third was actually as if I were aiming for a 3:14 finish. I slowed down in the middle phases but was still on track for a 3:25 time at the 30km mark (but as I was slowing it was not going to be likely). All of that shows that I had gone out far too fast, well beyond even what the most optimistic target required. Suddenly I'm not as disappointed by my actual 3:34, though I was in a world of pain for the last 12 km, as I did hold on to a vaguely acceptable time after the earlier stupidity.
This time round my Huntly Half effort indicates I should be able to run a 3:04 marathon which, based on my history, is almost unimaginably fast. It would be an 18 minute improvement on my personal best. But I feel like I've made a breakthrough in my running this year and things have been smoother than any other lead-in. Bearing in mind that Huntly was flat and Kirikiriroa has about 400m of ascents, I'll be strictly targeting 3:10 and if all goes well till the final 2.2km (after the last grinding slope) to make a clean finish below that. If things are more challenging, 3:15 would also be a pleasing B goal, which is still a 7 minute improvement on my best ever.
Those are all the training factors for success but external factors are looking quite good. So far, the extended weather forecast is for a warmer morning than the frosty start last year. Also, last year I was a bit stressed and overworked during that period of the race, whereas this year with a new Senior Teacher, and just one school to manage, I am feeling less distracted.
One final external factor is that I bought a new pair of carbon-plated racing shoes, also known as "super shoes". As mentioned before, these are de rigeur in racing these days. I found a sale pair of Saucony Endorphin Pro 3, which had recently been superseded by version 4 so the 3's were prime for the picking. I had only run 5km races and two half marathons (Coatesville and Waterfront) with my old pair of Saucony Endorphin Pro 2's so this would be my first marathon in super shoes. What effect could this have? Well, it could mean that my target pace will be easier to maintain and if I need to ramp up pace toward the end, it may not be as daunting as in normal training shoes. We'll see though.
Overall, for this last week of taper, I'm hoping just to feel fresh and able on the start line. My body, aside from a returning tightness in my right hamstring, feels great. My calf issue of a few weeks ago is all gone. I started my training with tight Achilles but there is no sign of them either. And the hip flexor discomfort I usually get at the later stages of a marathon haven't been evident in my training. This week will just being keeping everything pretty light, with lots of sleep and good nutrition. I have also decided to not have alcohol in this period, too, which will help with the resting and lowering any inflammation in my body. So all the controllable factors are in favour of a good run.
Sunday, May 19, 2024
The Huntly Half
As a race that I'd never run, the Huntly Half Marathon was mainly in my imagination till this morning. It had an evocative presence even from the assonance in its name. Its reputation was a fast, flat half marathon where PBs were made. Through the wonders of the running app, Strava, every year I could see others going down and running it with fast times; running great, John Walker, had won it several times.
I cannot think of a year, though, that I planned to run it. It always clashed a bit with other plans and ideas, or simply didn't occur to me. As alluded to in previous blogs, even my entry this morning was a bit of a side project. I just wanted a race three weeks before the marathon to estimate my fitness and pace. Also, I did want to see whether my 1:28:28 at Waterfront was really the best I could do, or whether my hamstring concerns had impacted it.
My training since Waterfront had been really good right up to this past week, when weather, a family health issue and general bad timing foiled my planned lead-in. Yesterday, I switched to my racing shoes on a "shake-out run" (the run you do the day before an event to keep things loose) but about 6km in my left calf became unusually tight. I ran on and started feeling the starting of pain and pulled the plug. This was not what I wanted the day before an event. I walked and rubbed it. Stretching seemed to make things worse so I just walked for about 20 minutes. I thought for a bit before deciding I'd try and run home. The whole way the calf was tight and on a few strides again I felt pain but not consistent pain. I threw in some pace and did not feel any worsening. I finally completed the test by running up the hill home and got in without trouble. Generally after symptoms like this, you'd have a day or three off to let things settle but with everything set to race in the morning it became a dilemma. In the end I decided to go down to Huntly and run, but with a mind that if it got sore I'd pull the plug and walk back. I decided not to wear the racing shoes and went with standard training shoes. These days, shoes can be the difference between a good run, a great run and a PB so carbon plated shoes are now de rigor, such as my racing shoes that I ran at the Waterfront Half. Here, I was going to run in conventional shoes.
I got there early and this is the best way to race. You have a double-hit of some portaloo action; you have your coffee; do a jog with a few strides; do general stretching and make your way to the start chute without trouble. And it was a great day to do so. There was some morning fog and an apparent overnight temperature of 2 degrees, but when I got there it was comfortable with the morning sun beaming down. In contrast to Auckland half marathons that have you starting 8am at the latest, Huntly started at 9am which was plenty of time for people to travel in to run and for the day to begin. My warm-up runs made me know that I'd be feeling the calf on the run, and when I tried pace I didn't feel like I was able to crank up speed.
Then a misfiring horn squealed and we were off. Gladly I settled into a pace but by the 4km mark, I realised, again, that my watch was not reporting pace correctly. I had thought I had been going a touch too slow but hadn't minded doing so in the early kilometres. But when I saw the marker and divided my time by four, I was at goal pace, or slightly faster. By the fifth kilometre, I casually inquired about the paces on all of the runners that were in our pack and got a multitude of answers. Fortunately, this rate had markers reliably every kilometre and visible so I tracked myself mainly through mathematics. My calf was tight and present in every step, as expected but did not hurt, even at what was a fast pace for me.
With the early jockeying for position out of the way, the packs and bursts therefrom became the rhythm of the race. My early pack fractured with someone I called Orange Guy burst forward and became a perpetual mark. Later from our pack, Frontrunner (which was written across the top of the back of his shirt) also broke, and then it was a small pack with me at the front. No one particularly pushed, and I was on pace. The plan is always to run your plan and then reel in runners ahead who did not plan well for their ability. And it happened first with Frontrunner. He had a very strong pace from about 4km-9km and then we just mobbed him. The course was an "out-and-back" with a turn at the halfway mark. I felt myself breaking away from my own pack in the kilometres before the turn and when I made it, I realised I had made a reasonable gap indeed and was closer to the Orange Guy than I was to them. I locked in a faster pace and surprisingly Orange Guy must have faded because within a minute I'd passed him, but still on my own. New marks were ahead, "Blackman" (at a distance he could only be a colour) and a female runner who was with him to form a minipack.
I might have thought I was going fast but another runner, possibly a later starter, "Wanganui", burst past me in a rush to finish. He passed the my two new marks but strangely seem to have slowed down to around my pace because he never really left my sight, about 100m ahead. The female runner stopped all together to take a gel. She must have been struggling and wanted some magic to get her groove back. The sugar from a gel takes quite some time to get into the system. Either way, I passed her in a blink and not long after passed Blackman. I trailed Wanganui for a while, around the same time I felt myself struggle a bit to maintain my pace and around the 19km mark, heard footfalls behind me. My tail kept with me before hitting the gas around the 20km. I tried unsuccessfully to stay with him but that pumped up my pace for the final stretch that brought me across the finishing mats at 1:27:23, a 1:05 improvement on Waterfront.
I went through the finish line and removed my tracking tag from my show, and soon as I rose from my crouch, my calf turned to stone. The runner who blew through finish line at 15km/hr one moment, limped slowly to collect his bag the next. Compared to Waterfront I held my speed for much longer and the pace fade was only a small loss of time. I won't be doing another half for quite some time as the two full marathons take precedence.
As for my calf, I think it's a temporary thing and I hope with rest and some treatment it resolves itself. It is a wonder that something that feels so debilitating one day cannot impact much a lifetime best performance the next day. I'm glad though. It is one for the scrapbook.
Monday, April 29, 2024
Believing in dreams
Thursday, April 25, 2024
Observing a day
Saturday, April 13, 2024
To live, to die
Sunday, April 07, 2024
On the water front
Sunday, March 24, 2024
Milestone
On Thursday, I crossed an interesting in my running, the "1000km for the year" mark. 1000km annually is not a big amount - for context, you can achieve it with just 20km a week and have two weeks to spare. In 2017, my first full year of running I was proud to break 2000km by New Years Eve. But with aspirations of being a 4000km a year runner, the 1000 mark is quite a critical one. In 2023 I crossed it almost right on pace, 1 April, which was a personal record. The years since 2017, 1000km has come up at a wide range of times:
2018 - 30 June
2019 - 6 April
2020 - 22 September
2021 - 27 June
2022 - Did not run 1000km
2023 - 1 April
2024 has so far been a wonderfully smooth start to the running year and on Thursday 21 March, I again crossed the 1000km for the year mark. Of course, it is an empty record if it doesn't confer any actual ability or potential with it. 2023's record did not translate into a faster marathon for me at either Kirikiriroa or North Shore, but the solid year that it was is probably the reason I performed well with my mile PB in December, Coatesville in February and the Hobsonville Point Parkrun.
Since my performance at Coatesville, I have been very solid. I shook off the niggles quickly and stacked three weeks of mileage over 100km and kept working on my speed. The Waterfront Half awaits me in two weeks where I hope to translate this work and training into something symbolic.
I've only done the Waterfront Half once before in 2019 (see here). It remains my Personal Best time for the half marathon distance, 1:29:58. That is a speed of 4:16/km, which though I more or less achieved that at Coatesville, daunts me numerically. Based on my fitness now though, I should be able to beat it by two minutes with an average pace of 4:10/km over 21.1km. It is one of the mentally difficult things about running that you are preparing for something you never do in training. Every peak performance is in effect a leap of faith. If I am to go under 1:28:00, from beginning to end I will need to be right on, or thereabouts, a pace I have not maintained for more than 10km at any time in my life. On my run yesterday, I ran a 3x2mile run - this is where within a long run there are three segments that are specifically faster for 2 miles - and the fastest of the three two mile segments, on the flattest part of the run, was run in just over 4:10 pace, and once it was done, I was pretty done, too. So 4:10/km stands in my mind as a challenge.
The secret sauce though is the taper. It is important for me mentally to think that the run yesterday was (a) a good run; (b) done while my body is still coming down from a fatiguing three big weeks; and that come race day, my body will be fresh and peaking, loaded with adrenalin and with fast people racing alongside me keeping me pegged to the target pace. That was the magic of Coatesville, too. In my head, a 1:30 on that course was not possible till I was on course, disbelieving my pace, and then still somehow managing to keep it going till (almost) the very end.
For perspective of what taper is looking like:
The week starting 26 February: 102km (6 days running)
The week starting 4 March: 114km (6 days running)
Last week: 115km (6 days running)
This week: 92km (5 days running)
Next week: 80km (5 days running)
Race week: 50km (4 days running), prior to the Sunday race day.
Fingers crossed that all works and my body rests well and is ready come 7 April.
Sunday, February 25, 2024
Another record falls
Sunday, February 18, 2024
Back on track
2023 was a strange year in my running. It on one hand was the year that I ran the most, 3850km, more than the 3,111km in 2019; yet on the other hand, a year where I ran only two events and did not run my best. To be clear, I wasn't looking for personal bests - I was looking for a consistent year of running, and had two goals: a mileage goal of 4,000km in the year (not achieved) and a climbing goal of 52,000m ascent for the year (achieved) and that good performances might be a by-product. When the mileage goal started to slip out of reach, I switched to a new goal: pace.
For most of the year, I had been noticeably slower at the fastest part of my range compared to other years. To put some numbers to it, at my best I could run 5km in less than 20 minutes, but in late 2023 I would not be able to go under 21 minutes; in a half marathon at my best I could go under 1 hour 30 minutes, but I would struggle to go under 1 hour 40 minutes in 2023. These margins might seem small but the work to get them down would usually take a long time. So, I switched to pace training in December. The implications of this are that mileage comes down a bit and very specific work-outs are used to sharpen up. Such an example might be 10x400m, or 3x2mile runs, where you run particular distances at fast paces with rests in between.
The surprising thing was that the fruit came quickly. I ran a mile in 5:49, a lifetime best. At the end of the year, I almost broke 20 minutes for the 5km park run (where humorously all runners had to squeeze past a van and its trailer on two parts of the route). My pace training continued into 2014 to prepare for my main target event, the Coatesville Half Marathon.
I have a lot of affection for this event. Early in my running in 2017, I ran the Coatesville Classic (8km), which I described here: Crypticity's abound: Comeback and then the Half in 2019 (Crypticity's abound: Mark). Quoting myself for brevity: "The Coatesville Half course is notorious. It is the hilliest course of the series with one significant incline at 3km, another at 10km, another at 14km and another at 16km." In 2019, I ran 1 hour 37 minutes, which was a solid performance in what would be my best year in running, so I was looking for the run this year to be a bit of a bellwether for the year ahead.
The lead-up through January was very good. In a time-trial I ran 1 hour 35 for a flat half marathon distance. On the Saturday eight days before the run, I ran two training runs that surprised me in pace that exceeded what I thought I was capable of, a 5x1mile and a 2x4mile. Unfortunately on the last one at the very end of the last 4 mile I felt a tightening in my hamstring and I jogged home very gently. I gave myself a two day rest and then did some light runs to test it out again. I felt OK so continued with my normal "week before" taper runs. And then we come to the day of the race.
After a poor night sleep, I woke naturally at 6:12am with a start. My shock at the time jolted my heart and mind into action. Somehow, my 5:30am alarm had not vibrated me awake. In fact, it claimed it had and was doing it every eight minutes, as if self-snoozing itself without any fuss. I had to leave by 6:30am to realistically get to the venue and be ready for the 7:30am race start, so I exploded out of bed, changed, coffeed and threw everything in a bag and left the driveway at 6:32am. So far no speeding tickets have been received, so my arrival in the Coatesville Pony Club car park at 7:07am can be said to have been smooth and without issue. I grabbed my racebib and then to the back of a very long queue for the portaloos. I tried my best to do some dynamic stretches while in the line, and then after a quick prep in the loo, jogged over to the middle of a tightly packed starting chute at 7:27am without any real warm-up.
Perhaps due to the adrenalinised chaotic start to the morning, I was much faster than my race plan, which was to aim for 4:30/km pace (which would have me on a 1 hour 35 min finish speed) until the downhill speedy finish and go sub 1:35. I had to first push through the mid-pack runners to the front 10% to find people of a similar pace, and that meant my speed at the start was a bit reckless. Fortunately for me there was an easily recognisable Zimbabwean female runner, Ketina, who usually is about my pace, so I used her as an initial measure where I needed to be and I caught up to her and dropped a bit of pace for the hill.
There began the very familiar pattern of my usual strategy: slow on this hills (letting my pace peers pace me) and then reeling them in on the flats before passing them on the downhills. Ketina disappeared after the first such iteration, and once I was at the top of the first hill, I sped up and didn't slow down. Looking at my watch, I was clearly in the 4:10-4:25/km range - too fast but feeling strangely comfortable. I kept going pulling past more pace peers to the halfway turn when I had a rather cruel realisation that I should have anticipated. My watch had measured my distance 200m short of what the marker was indicating. This was a problem because that meant I was going even faster than my watch was telling me. I could have been going 5 seconds per kilometre faster than I was reading off my watch.
For any race, the best indication of whether you are going too fast is your breathing (and also one of the best ways to know if your running companions might be entering into a struggle phase). I checked myself and thought I was still breathing quite evenly so I held my pace for the last few hills and then made the final turn onto the downhill home straight. It was then that I knew that it should be just a matter of cruising to the finish line, a certain PB, probably a couple of minutes under, and done on one of the more difficult courses.
It wasn't to be though. About 2km from the finish, I felt the tightness in my hamstring return. I couldn't but cut pace just a little; then, a pain radiated out from that point, and I shortened my gait and cut pace once more. By the time I had entered the Coatesville Domain I was not enjoying running and would have had a noticeable limp. Only one person passed me though and I got over the line at 1:30:12, my third fastest half marathon time.
For perspective, despite the niggle, I would say this is my best performance. My other two fastest times are 1:29:58 at the Waterfront Half, the flattest possible course. and 1:30:04 on the trickier Millwater Half. But none of them are like Coatesville. It's kind of amazing that after all these years though all three PBs are clustered within 14 seconds of each other after different 21.1km races.
I gave myself a break of four days from running and then ran 5km on Friday evening with hamstring sensations but no pain. This morning I ran 22km with only mild sensations that never amounted to anything and then a massage and some strengthening work. I hope the hamstring is just an oddity that with a bit of rehab I'll get back quickly onto a regular routine.
So the omens are bad/good. Bad that I picked up a niggle/weakness of some sort. But good in that I have the best foundation for a year of good performances. My next chances to race are:
- Hobsonville Point ParkRun 24/02/2024 (goal: under 19:30)
- Waterfront Half Marathon 07/04/2024 (goal: 1:27)
- Kirikiriroa Marathon 09/06/2024 (goal: under 3:20)
- North Shore Marathon 15/09/2024 (goal: under 3:15)
All with ideal training...
Sunday, November 19, 2023
“You’re not actually legally obliged to have an opinion.”
Thus spoke Bill Maher in his show Real Time. He claims that social media has forced individuals, and corporation, to feel like they need to have a thought and a stance on every current event, whether it be the Israel-Hamas conflict, the Russian invasion of Ukraine, the marital situation of Will Smith and Jada Pinkett Smith and Elon Musk's running of the app formerly known as Twitter. You could easily argue that any consumer of news was similarly exposed in pre-social media times. His point is that people for some topics it has become obligatory to have an opinion, even when there is no realistic need; worse, to not have an opinion, presumably in some circles, is to be not caring.
Having recently watched the New Zealand movie Uproar set in New Zealand at the time of the 1981 Springbok tour of New Zealand, you can imagine a time where this country was divided and those of an anti-tour opinion would see status quo or disinterested positions as actively supporting racism through a lack of a denouncement. But you could say that public opinion or making a bigger "scene" could trigger a symbolic cancellation of a tour or, more long term, political change locally, or even political change in South Africa. That was completely outside of the social media era but also it was a bit closer to home.
The topic of apartheid in South Africa was probably understood well enough by both sides. Pro-tour people justified themselves that sport should be separate from politics, and even could argue that if anything rapprochement through sport could lead to the ends of the anti-tour position. Uproar touches on the irony of that time that many of the anti-tour activists have been focussed on the South African apartheid and blind to racial discrimination at home.
The Israel-Palestine situation is one of the topics that Maher though was talking about, especially critical of university students in the US who protest against Israel in support of Palestine, without any condemnation of the 6 October attack by Hamas that "started" the current situation. Worse, the retaliation for the attacks have apparently reawakened the latent antisemitic tendencies in some parts of humanity. For New Zealand, while there are Israelis and Palestinians here (one of my colleagues of mine is half-Palestinian) and our Government at some stage will have to decide in what way it will support one or both sides, it seems strange to think that we must have a stance on the rights and the wrongs of it.
I regard myself reasonably knowledgeable on the history of the region where Palestine and Israel sit for an average guy but still I would not want to say any rights or wrong overall. The Hamas attack was abhorrent but the situation prior means that asymmetric attacks (and defence in the case of human shields) were always probable. The government elected by the Israeli people was unhelpful but expectable in the context. The government elected by the Palestine people was unhelpful but expectable in the context. Zoom back to President Clinton's attempt at Camp David, the decision by Arafat to reject the deal was unhelpful but expectable... and you can go back further and further in the karmic cycle. At the end of the day, choosing to support either side sounds like supporting a side in a toxic relationship for a couple who cannot separate or divorce, but may well kill each other. Any support is just based on limited knowledge of the rights and wrongs.
Tuesday, September 26, 2023
The magic ingredient
No, the magic ingredient is not alcohol despite the photo. I’ve had a breakfast of 肠粉 (rice rolls), 刀切糍 (not sure if there is a name for this) and 烧肉 (pork belly); then a lunch of fresh bamboo shoots fried with two kinds of pork, sautéed gaaichoy and two kinds of pork, friend together. It was something rather perfect. It might just be something latent in the crockery. But probably not. It is the taste of home.
Sunday, August 27, 2023
Strike three
The North Shore Marathon route is now equal with Auckland Marathon as the event I have done the most. The Auckland event starts with a bit of undulation through the Shore, a cruise along the motorway to the Bridge, then after the Bridge it is basically flat to St Helliers and back. The North Shore event is simpler: First you start along Milford Beach (beach section 1) then climb onto the road to Takapuna then run the full Takapuna Beach, then you climb out of there to Takapuna Grammar, then drop down to Narrow Neck Beach (fortunately not on the sand), then you climb out of there before dropping onto Cheltenham Beach for an interminable soft sand section, then you are rewarded with a climb up and around Northhead... and then you do it in reverse, and then back, then in reverse. Three beach sections time four, two Northheads. In some ways, it should be the easiest one to pace as you are fully aware of what is in store after you've only done a quarter... yet every time this event gets me.
My first attempt was in 2018 where I felt well trained and plunged in and started struggling after my second climb of Northhead (about 31km in), and even walked at around the 37km mark, and pulling into finish around 3:44. (My blog of it: Always crashing the same car)
Wednesday, August 09, 2023
Normies
Wednesday, July 19, 2023
Inevitability
2018 was the year when I fell four times on runs. The first was a pre-dawn fall in the Domain; a vehicle came up behind me with lights on and I moved to the verge, my own shadow making me oblivious about the drain I was about to put my foot in. That was interesting because I was fine apart from a bit of a graze at the time, but my knee swelled up a few hours later at work. Then there were the two minor falls on daytime long runs: one I was crossing a road while fiddling with my waist pouch and looking out for traffic; the middle of the road had a raised section which I clipped my foot on and had me in a heap in the middle as concerned motorists stopped on either side, but not grazes to show for it. Then less than a week later, my foot hit the base of a sign on a Great North Road footpath sending me again into the pavement but with some lost skin. Then what was the most catastrophic of the series, I was waiting for the Omaha Half to begin and jumped up onto a boardwalk only for my feet to slip out from under me and a heavy fall on my buttocks. I completed the run but the delayed effects of the fall put me out of running for some time; it took almost two months to get back to it. It was freakishly high to wonder whether I should really be out there running at all. Yet in all the years around it, 2016-2017 and 2019-2022, I only had one other fall, a wipe-out on gravel at a sharp corner in an event.
The forces of probability over a habitual action are worthy of us all to consider, just like speeding on a windy road, even one that you know, could eventually end in disaster. As a runner, and morning runner at that, there are many factors that raise the probability of a fall. There is visibility, which, even with the waistlamp I bought after the first fall in 2018, cannot illuminate every threat in a timely way. Little unevenness on the path is enough to catch a shoe and unbalance. Even with illumination, you can be dazzled by headlights, twilight can cause less visibility than in darkness, and rain or fog on glasses or in the lightbeam are dangers. The moisture factor boggles the mind: I don't know if it is shoe technology or sheer intuitive skill that means the many thousand footfalls on wet footpaths do not regularly result in slips. However, three of the four 2018 falls happened in broad daylight, some surfaces are perilous and distractions can lead to misfooting.
On the 29 July this year I had the fall that broke five straight years without hitting the ground. It was inevitable, thinking of the above, that I'd have another moment of grazed hands, but this felt almost unavoidable on a practical level: I entered a trap. On one of my regular pre-dawn loops I turned onto Portage Road crossing it earlier than usual. I would usually take a newer footpath on the outside by bus-stops but it hadn't yet started and traffic was coming, so I ran onto an older, inner footpath that passed businesses. It was a bit cracked and a copse of trees were to its side blocking street light illumination but I charged down it with only my own light. It was going to be tricky because I'd have a sharp right-hand turn at the end (so not to run onto the road) but not something I hadn't managed before. As I approached the turn my lamp revealed late that the end of the footpath was a stretch of shiny mud, but it was not like I hadn't run in mud before. I slowed and took it with caution but as soon as my first foot hit the mud it slide out and my momentum took me face first to the pavement, my hands fortunately bracing the impact. There was a half second of fright and then a half second to rise and run, and another half second for the burn on palms to register. I was still five kilometres from home and still had work ahead. The result once at home and in the light was several wounds, three on my hands, both elbows and a knee.
I ran the loop again in broad daylight and I can only conclude that running it if ten normal runners went through that path in the dark, at least five of them would come to grief. It allayed some worries; I knew it just had my number and now I had its.
Thursday, June 15, 2023
A river run through
Wednesday, June 07, 2023
Get a niggle on
Three more sleeps and I put on my shoes and run the Kirikiriroa Marathon, Kirikiriroa being the te reo Māori name of Hamilton, kirikiri being a term for gravel, and roa for long, so maybe it was a long gravel stretch, maybe by the riverside, which if so is now a sometimes paved and, yes, sometimes gravel path.
My path to the start line here there is a curly one. I had got the supercheap earlybird for 2020's edition, but got injured in the December of 2019, and then I had the blessing of the pandemic, the lockdown knocked the event and my entry back a year. 2020 was an average year of running but I still intended to run it when the postponed event of 2021 arose. Fortunately 2021 started very well with my running till a few weeks before, I sprained my ankle coming down Mt Eden. I forfeited my entry and when I eventually started to run again the rest of 2021 was rather uninspiring running-wise. I entered 2022's event more in hope than anything else, but in the Auckland Half-Marathon a few months before the event, I felt my Achilles flare up and it put me off training and knocked me out of running the 2022 Kirikiriroa event. Unfortunately/Fortunately, Omicron wave surged to New Zealand shores and in an abundance of confidence, they postponed the event, and all entries, to 2023. So my attempted entries were alternately stopped by pandemic, injury or both.
Saying it like that makes it sound like I'm always hurting myself, but there are long stretches of wellness in between. The dilemma of niggles and injuries is part and parcel of being a runner. Injuries can be accidents like the ankle sprain happen, but they can arise out of overuse such as my Achilles flare-up.
But niggles are a different kettle of fish. As you train and slowly stress your body more and more, parts of the body inevitably go through the adjustments and aches and pains arise. These can sometimes feel like injuries, but are not; or worse, may appear to be niggles but are actually the early signs of an injury. As such, there is a lot of anxiety when the first niggles appear. My training this year had its early minor niggles but my first moment of uncertainty was in late April when after the Concrete Monster run, I had some tightness near my knee that felt like a possible strain. I rested a few days and massaged the area and only via that did I realise it was not an issue of the tendons around the knee but a muscle knot deep in my quad. After releasing that knot, the issue disappeared. A definitive non-injury niggle. Two weeks later the hinge point of my left ankle felt sore after another challenging run. I rested it a couple of days before running again to the same issue, but while running I thought about a solution of using heel inserts temporarily, and also that my usual work shoe insoles had been swapped into the running shoes. After putting in the inserts (which I wore for two weeks) and changing the insoles, the feeling disappeared. Another niggle. And then just last week, after my last "fast" workout my right lower calf was tight. This time I more or less "ran through it" (i.e. I didn't change my training or add rests) and a few days later it resolved itself.
One of the key lessons from my many trips to physiotherapists is the wisdom of the "3/10" on the pain scale. Pain has various levels and though subjective, there is a descriptive spectrum that people use, and 3/10 is the highest degree of pain that one should persist in an activity, although depending on how the body part in question feels after and the next day. For many niggles and injuries, it is in fact better to be active and potentially taking your body to the 3/10 as a way of healing rather than rest. All of my niggles were in this zone and fortunately were nothing worse than an unhappy muscle or joint.
Even with the niggles, it has been a smooth training block more or less. But strangely I'm not 100% what time I should be aiming for for the marathon, I would say it's a broad aim for 3:28 and see how I feel at halfway, which is not how it should be as my MP (marathon pace) should have been something I had my training set around. This morning before one of the few runs this week, I also realised I hadn't even settled on which pair of shoes I should run in, an important consideration. I guess I've been distracted from the basic decision making for the race though clearly still going through the motions of what looks like good training. Almost four years since my last full marathon, I guess I should be just glad to finish the distance under my perennial target of 3:30 and do so with ease.




