Skip to main content

2019 is Here

So, 2019 is here and it's going to be a big one.

Since I started at Scott Logic last year I am getting much fitter. being just about 10.5 Km door to door it's an easy cycle (or will be once I get fit again). Also there are lots of us who like to go running at lunchtime. Well, they go running, I just try to keep up, and mostly just watch their backs head off into the distance. Of course trying to keep up will get me fitter and faster in the long run (I keep telling myself that).

Last year, I finally got back into triathlons and I am now looking at which races I will be participating in this year (notice I don't say competing in, which would be a misnomer, I only compete to not come last!)

Many years ago (around 2007) I attempted to complete the Ironman 70.3 at Wimbleball. I failed. I was far too slow on the bike leg and ran out of time. That was the first race I had not managed to finish.

This year I am thinking about trying my hand at another middle distance race (same distance as an Ironman 70.3 without the branding). It has to be between Aug 2019 and Aug 2020 as I want to complete the distance before I turn 'cough'. Oh, sorry you didn't catch that?, never mind. Is this a mid life crisis? too late for that I'm afraid.

Anyway, back to the triathlons.

This limits my choice of race. It will take at least six months of training to get myself to a stage where I may be able to complete the distances in the times allowed. Also I don't want to travel too far. so I looked through the list of available races and whittled it down to the following three:
  • Woburn Abbey Triathlon in September
  • Ironman 70.3 Weymouth in September
  • Immortal Half in June
Each race has it's own advantages.

The Immortal is the same course I failed on last time (although no longer being organised by Ironman), so completing that course would be great. The disadvantage of this course is that it is quite hilly with 5000 feet of climbing on the bike (if only I'd looked at that before entering last time!)

The Ironman 70.3 is quite flat with only 800 feet of climbing on the bike, but costs a lot to enter.

The Woburner (as the Woburn triathlon is called) is 9 months away, doesn't have too much climbing (1500 feet on the bike) and is in 220 magazine's list of 8 of the UKs best half Ironmans for beginners.

 I think that I have settled on the Woburner, although this might change as I create my training plan.
Labels:

Comments

Post a Comment

Popular posts from this blog

Triathlon Training in the new year

So, my 2019 training has got off to a good start. I'm running regularly and my knees seem to be holding up. I've got a training plan to get me to a middle distance triathlon in September and I am managing the run distances I have set myself. I need to find some longer cycling routes to work and ones with a few hills too, but that shouldn't be a problem. my weekly cycling distance is okay, I just need to move to get my ebike to be doing less of the work. last week I did use my normal commuter bicycle and managed the whole four days as well as my runs, so that was a really good sign. Swimming won't be an issue, I have always found that to be the easy part of a triathlon (not that I'm fast, but I can keep going, and I did manage to swim the distance within the cut off time when I tried the ironman 70.3 last time) The main worry about going longer is my knees. I've got a 10K booked in late January which will test my knees out and I'm hoping that they hold ...
Post a Comment
Read more

Creating a Watch Face for Android Wear OS 2

Step 1 - Setup my watch for development I have wanted to create a watch face for android wear for a while, but as no new watches were being released my old Moto 360 watch running wear os 1.0 got out of date and I stopped using it. For Christmas 2018 I got a new wear os watch running wear os 2.2 (android os 8.0.0). it has a round 400 x 400 screen and I decided to finally get round to creating myself a custom watch face for it. The first thing I do with all my android devices is to enable developer options. if you don't know how to do that then you can find the method using a google search. I won't give it hear as it opens up all sorts of options that could make android become slow/unusable. Once I had developer options enabled, I turned on USB debugging. This watch (as opposed to my old Moto 360) has a USB connection to the computer, so I don't have to use WiFi debugging (which has to be set up for each debugging session). now on to the watch face creation. St...
Post a Comment
Read more

Windows Subsystem for Linux Internals

Background Windows Subsystem for Linux was developed by Microsoft to enable command line programs compiled for the Linux operating system to be executed on Windows. To explain the architecture I would like to show the evolution of OS design and how that has enabled this subsystem to be built. Dark Ages (or Back in the Day) Microsoft's MS-DOS was quite primitive in its design (compared to today's OS's). It is a single user OS that can execute one process at a time. DOS had an application programming interface to allow user programs to access some hardware in a device independent way, but only for character-based applications. This allowed applications to display graphical elements emulated with text characters as these screenshots of Microsoft word for DOS show: This is Microsoft Word version 1. To use these programs you had to remember key combinations to bring up the menus and used the cursor keys to navigate around the screen. If the a...
Post a Comment
Read more