Blender Fox


Training in Quarantine - Day 11

#

Walking again, and spotted a pranged up car mid way around my walk. Seems like it's been there for a while....

Training in Quarantine - Day 10

#

Broken 10 days in Quarantine. Walked again today. Gloomy clouds, threatening rain this afternoon.

My heel still hurts when I put my shoe on. Perhaps I need to put a plaster on the cut until it heals...

Training in Quarantine - Day 9

#

Walk again. Did my 3k lap as always, on call, so didn't want to make too far a distance in case I get beeped (wasn't this time, thankfully)

Walked past a Sainsbury's that had a massive queue last time I went past them. There was no queue this time, even though it was still open, for some reason.

Decided to finally rasp and scrape my heel of hard skin, soak it in hot water, and then put some foot cream on it after a shower.

I'm writing this entry a day after it should have been written (forgot to log it yesterday) and my heels definitely feel better. Still a little crinky, but definitely not as bad as before.

Training in Quarantine - Day 8

#

Did my 3k walk again, I seemed to have reopened my heel wound again and left some blood stains on my duvet last night and my heel hurts a little when I walk on it. I can still run on it, though.

Training in Quarantine - Day 7

#

I'm on call for the first time since quarantine and lockdown started so decided to run just after finishing work.

Got half way around then got beeped by the office, messing up my pace, even though it wasn't an incident.

Still, in the time I had been running, according to Strava, I had averaged a 5:57 pace.

Training in Quarantine - Day 6

#

Another walk today in between rain and snow showers, and while we have workers outside out flat trying to fix a leaky mains.

Training in Quarantine - Day 5

#

Missed logging this yesterday. Another walk day -- didn't want to risk re-opening my wound. Seems okay for today though (Sunday)

Putting my heel in it....

#

I took my socks off after my exercise and I somehow managed to cut my heel...

Training in Quarantine - Day 4

#

Day 4, and decided to take it easy for a Friday and decided to walk the 3km I have been doing instead.

Training in Quarantine - Day 3

#

Day 3 in quarantine training. 2.97 km in 16:50, pace 5:39 min/km, and 0:02 min/km faster than the run 2 days ago, although I didn't really feel I worked as hard as two days ago. Strange.

Training in Quarantine - Day 2

#

Day 2 of quarantined training. Went the other way around my same route, and got a slightly lower distance count for some reason.....

Oh, well.

Ran at 5:34 min/km pace overall, with PB on this route at 5:26 min/km.

Being quarantined up does have it's benefits I guess, being forced to do stuff you never got a chance to do.

Training in Quarantine - Day 1

#

3.18 km in 5:41 min/km, which isn’t too bad considering my best time 5:24 min/km

London is in semi-lockdown right now with only a few valid reasons for someone to leave the house, such as exercise, work (where remote work isn’t possible), providing medical care to a vulnerable person, shopping for essential goods, or for other medical reasons.

 

Training

#

Ran through my local park today, to the sound of Eurobeat. The pace was fairly comfortable, and fast enough that I got an average pace of 5:40 min/km

Wasn't breaking any records with this run, but I was reminded with _annoying_ effectiveness, why I dislike running through the park: groups.

Having to slow down, stop, or run onto the waterlogged grass (waterlogged due to Storms Ciara, Dennis, and Jorge) because the groups are hogging the path is _really_ annoying, especially if you're trying to keep a specific pace.

Training

#

Decided to try my 5K route again today -- first time in a long while and I knew I wouldn't be able to last it (haven't run consistently for a long time), I made it 3.3K around the lap and then walked the rest of the way.

Spotify's running playlist helps, but it doesn't work in the same way as their old Running Mode used to, which I really miss.... :-(

My pace times were 6:15, 5:39, and 5:21. First 1km was slow for two reasons -- first to build up the speed slowly, and second, it was an uphill slog. Second k was fairly flat, and the 3rd k was downhill, but tried to keep the pace.

Training

#

Decided to up my distance today. Ran a larger circuit that took my past the local cinema and had a few slight inclines and a negative gradient towards the end (or a positive gradient if I go the other way around)

Pace was 6:10 min/km, and 4.37 km, though I probably could have gotten to 5 km if I had finished the last bit without dropping to walk.

Training

#

Raining today, so went to the new gym where I recently registered as a member (free since I'm a resident of the area, but then I'm only allowed to use that gym). As a consequence, instead of paying £8.75 to use the gym, I only have to pay £4.55.

Ran 4 km in 25:31, with the speed set at 9.5 km/h for the whole run.

Training

#

Running on Christmas Day ahead of the Xmas dinner tonight.

Nothing major, 5:36 pace, 3.23 km, but got frustrated with several groups of people blocking the entire footpath during my laps.

Training

#

Picked up my FitBit and reinstalled the running partner app on it and attempted to run 2km in a target of 15 mins. Did it in 11mins according to the app, but Strava logged it as 1.91km in 10:45. Strange, considering both are powered by the same data...

Training

#

First training entry for a while, I've been lacking in motivation recently to post anything.

Nothing major about today's run, just a quick lap around the park, 2.12km, 5:52 pace, way slower than the 5:22 PB I have.

Google to buy FitBit

#

Well, this is a bit of a surprise, but not too much a surprise.

Regular readers will know I'm a FitBit user and have been for a few years.

You'll also know that I'm an Android user, and Linux user.

So I just read this article, about Google acquiring FitBit. I'm curious to see how they incorporate FitBit and whether improve it or destroy it....

[www.engadget.com/2019/11/0...](https://www.engadget.com/2019/11/01/google-buys-fitbit/)

And a Press Release has just been found in my inbox:

[investor.fitbit.com/press/pre...](https://investor.fitbit.com/press/press-releases/press-release-details/2019/Fitbit-to-Be-Acquired-by-Google/default.aspx)

Training - 15th September 2019

#

Couple of days away from home and no time to run. Came back and did a 1.5 lap around the park.

Broke no records with this, and at 5:55, was slower than my last run of 5:27. Weather didn't help though, at nearly 25C

Training - 8th September 2019

#

Did another lap around the park, but went clockwise instead of anti-clockwise.

And beat my PB for that way around the park.

Pace was 5:22. Previous PB was 5:35.

Next task is to get to two laps around that park, which should take me to about 4-4.5km.

Training - 7th September 2019

#

A quick lap around the park. Felt fast and good, but it turns out I was a 5:27, 0:08 slower than my best time. But the chart looks good:

The pace/HR chart also looks okay. Speed (top line) drops at corners, as expected. The last drop is when I'm turning two corners, and I'm under trees, so the GPS probably dropped out.

The HR (bottom line) was fairly stable between 155 and 170 bpm.

Training - 31th August 2019

#

After several days of hot weather, it's cooled down enough for me to get running again. Did my 3k lap and stopped part way to check out the new Leisure Centre that's opened in New Barnet. 5:50 min/km pace.

Training - 25th August 2019

#

A hot day today, 30degC in fact, did one lap around the park, and the sweat was pouring, not from exertion, but from the heat.

Also I've noticed. Those dips you see in the chart? They are when I'm turning a sharp corner. I guess since I'm not sprinting through the corner, the GPS logs it as a slow speed. Interesting fact I'll have to bear in mind for future.

What's even more interesting, is that FitBit logs the run slightly differently

You can see the dips here too, but definitely not as extreme as the one in Strava.