Not much writing of much late, because there has been no running of late. I've wanted to rest my achilles as much as possible, just keep off it, with a hope that a couple of weeks rest (and perhaps a trip to the doctor) will start to see it right, rather than trying to run through it.
Here's hoping.
Nothing much else to report at this stage unfortunately.
Sunday, April 11, 2010
Tuesday, April 6, 2010
the proverbial broken record
Let's get one, fairly simple thing straight before we go any further with this running blog thing.
I'm dumb.
I'm not unintelligent, at least I don't think I am. But as a runner, as someone who should know better and chooses not to - I'm a bonafide, grade A moron.
I know I have sore achilles, and I know this because my tag cloud to the right has the word 'achilles' in a font size three times bigger than any other. I also know it because my calves are quite sore two days after a long run, and because when I tried to do a speed session this morning, I struggled and had to cut it short early. I know because every running stride on my right hand side causes me to realise that my achilles is pulling a little.
At least I cut my run this morning short and didn't run through the pain. Well, I mean, I did run through the pain for 1km, but at least I stopped after that. Well, I mean, I ran a little on the way home, but that's not really running now, is it?
There is something strange about the human condition that allows/encourages us to ignore things that we know are simply bad for us. Like eating a cheeseburger. I run, even when I know I shouldn't - I just do it anyway. And what's possibly worse is that i know its bad for me. And yet, persistence is a virtue apparently. Part of it is not allowing weakness to creep in. You know the voice. "If you don't run today, all of your work from before will be undone" - if you can imagine the voice in a cheesy 50's sitcom ghost voice, all the better for you.
I will go and see a sports doctor. I will at least try to convince myself that running 11km on Wednesday if I am not 100% is a bad idea.
Then again, I'll probably just run anyway.
I'm dumb.
I'm not unintelligent, at least I don't think I am. But as a runner, as someone who should know better and chooses not to - I'm a bonafide, grade A moron.
I know I have sore achilles, and I know this because my tag cloud to the right has the word 'achilles' in a font size three times bigger than any other. I also know it because my calves are quite sore two days after a long run, and because when I tried to do a speed session this morning, I struggled and had to cut it short early. I know because every running stride on my right hand side causes me to realise that my achilles is pulling a little.
At least I cut my run this morning short and didn't run through the pain. Well, I mean, I did run through the pain for 1km, but at least I stopped after that. Well, I mean, I ran a little on the way home, but that's not really running now, is it?
There is something strange about the human condition that allows/encourages us to ignore things that we know are simply bad for us. Like eating a cheeseburger. I run, even when I know I shouldn't - I just do it anyway. And what's possibly worse is that i know its bad for me. And yet, persistence is a virtue apparently. Part of it is not allowing weakness to creep in. You know the voice. "If you don't run today, all of your work from before will be undone" - if you can imagine the voice in a cheesy 50's sitcom ghost voice, all the better for you.
I will go and see a sports doctor. I will at least try to convince myself that running 11km on Wednesday if I am not 100% is a bad idea.
Then again, I'll probably just run anyway.
Sunday, April 4, 2010
technical difficulties
Today was one of those days that I planned to go one way, and ended up going another. Not that uncommon I suppose, but when you are planning to go for a jog, you don't really expect it to deviate *too* far from plan. Right?
The run itself was not too bad, not great, but fairly average. Truth is, I can't really say whether it was a good run or not, owing to issues that I had with my iPhone app - RunKeeper. I think that I ran around the 20km mark, though I'll never really know for sure I suppose. And it doesn't really matter either.
My first issue came when E called from New York to tell me that she had landed (this wasn't an issue mind, I just want to make that clear). I now know that if your phone rings while you are running, the application suspends its GPS and ceases timing. I had managed to run about 1km in the time that I was speaking to E, so that was a fair chunk missing right there.
When I re-started the activity on the application, it then decided not to play music for me any more, and my headphones simultaneously conked out, so I could barely hear the application prompting me for distances and paces. Which meant that I was basically running with my phone for no reason at this stage.
Periodically I would take the phone from my arm to check distances in order to ensure that I ran around the 21.1km that I had intended to run, and that worked to a degree. At around the 17km mark however (a time at which I was tracking ahead of schedule to run a PB for the Half Marathon distance), I must have stopped the application, because it ceased timing again.
So I don't have an accurate timing or distance measure for this morning, which made me kind of cranky; but it was user error I suppose. My achilles are feeling a bit sore now that I've had the chance to have a bath, stretch and Dencorub up a bit. My hips were quite sore as I was running, which is just another thing to keep an eye on.
Strength session tomorrow, but beers in the meantime at the folks place.
Extra note: If to prove my point; I have a somewhat sore throat from screaming at my computer, owing to the difficulty in posting the map above. Technology hates me today. I'm not going anywhere near the washing machine. Sounds like a good excuse to me.
The run itself was not too bad, not great, but fairly average. Truth is, I can't really say whether it was a good run or not, owing to issues that I had with my iPhone app - RunKeeper. I think that I ran around the 20km mark, though I'll never really know for sure I suppose. And it doesn't really matter either.
My first issue came when E called from New York to tell me that she had landed (this wasn't an issue mind, I just want to make that clear). I now know that if your phone rings while you are running, the application suspends its GPS and ceases timing. I had managed to run about 1km in the time that I was speaking to E, so that was a fair chunk missing right there.
When I re-started the activity on the application, it then decided not to play music for me any more, and my headphones simultaneously conked out, so I could barely hear the application prompting me for distances and paces. Which meant that I was basically running with my phone for no reason at this stage.
Periodically I would take the phone from my arm to check distances in order to ensure that I ran around the 21.1km that I had intended to run, and that worked to a degree. At around the 17km mark however (a time at which I was tracking ahead of schedule to run a PB for the Half Marathon distance), I must have stopped the application, because it ceased timing again.
So I don't have an accurate timing or distance measure for this morning, which made me kind of cranky; but it was user error I suppose. My achilles are feeling a bit sore now that I've had the chance to have a bath, stretch and Dencorub up a bit. My hips were quite sore as I was running, which is just another thing to keep an eye on.
Strength session tomorrow, but beers in the meantime at the folks place.
Extra note: If to prove my point; I have a somewhat sore throat from screaming at my computer, owing to the difficulty in posting the map above. Technology hates me today. I'm not going anywhere near the washing machine. Sounds like a good excuse to me.
Subscribe to:
Posts (Atom)
