Monthly Archives: February 2017

Marathon Training Update & Nike+

Early mornings can suck sometimes. Especially when you have to run on a holiday. 

But then you come across a view like the photo above and it’s all worth it. Very few others saw this site. All of time waited for me to witness this. 

My Nike+ training plan gave me a relatively light week last week but is stepping it up this week. 

I had several speed runs last week which I still find tough to get motivated for even though only last for half an hour at the most. 

I had two speed workouts; one that was 12×200 and another that was 8×400. All with short recovery times because the mornings were chilly. 

The Nike+ Running Club app on my phone has now broken one of the nice new features! It no longer repeats the info from the phone on your Apple watch. Twice this week it crashed on the watch but kept running on the phone. In fact, it never really started up properly. 

I had to delay my Friday long run as we decided to have a family breakfast and I couldn’t run after that! So I ended up going out on Sunday morning for a 12.75 miler in the temperate weather that hit this weekend. 50F is rather surprising for February. 

Later that day, Nike+ asked me to update my run programme and when it did this it put down a 12.5 mile run for Monday too. What a cow! I think “Nicki” (my name for the voice of the Nike+ app) has got it in for me. 😦

This week is going to be tough with the 12.5 miler today, a benchmark run, a 6 mile recovery run and then an 18.5 miler on Friday. 

I’m going to have to increase my food intake as I’m starting to feel like my legs are very heavy and underpowered. 

Advertisements

Nike+ Niggles Resolved

Mostly.

Last week Nike released an update for their Apple Watch and iPhone app. 

One of the major things that it fixed is something I had commented on in these pages before: when you start the run from your phone it doesn’t put any info on your watch! 

Thankfully, they seem to have resolved this along with putting some additional thought into the solution. 

For one thing, once you start the run on the phone and then get going , if the watch loses contact with the phone it will politely ask you if you wish to continue the run from your watch. Nicely done, Nike. 

Also, if you are running this way and you pass a distance milestone (each half-mile in my setup) it will announce the distance through your headphones that are connected to the phone, but also do a little chime on the watch so that you know you are progressing. 

All-in-all this was a nice update from Nike and I haven’t seen any new problems from it. 

On Friday morning I followed along with my running plan and completed a sixteen mile run. 

To do this on a Friday morning met hitting the streets right around five AM so I could complete it and still get into work on time. The picture above shows the view from my front window. 

It was very cold at 8F (that’s including the windchill; 20F actual) but it was beautiful out. The full moon illuminated the streets perfectly and was enhanced by the snow fall from the previous day; so, while it wasn’t quite full daylight, it was very easy to see without a flashlight. 

To get to sixteen miles I had to make up a new route as all my usual runs of that distance would take in State Parks or Trails and they were all covered in five inches of snow. 

So I concocted a route on the roads of Trooper and Skippack that gave me the necessary distance. An out and back route that wound through some pleasant neighbourhoods and skirted along the side of the Evansburg State Park. 

I wasn’t fast but a steady 8:35 pace was pretty good for that early in the morning and being so  dry thoroughly wrapped up (this makes it harder to run). The route had quite a lot of rolling hills, hence the elevation number above. Notice that t also has my heart rate recorded! 

The rest of Friday was a struggle as I was tired and very hungry(rungry). I didn’t help myself as I was in such a rush to get the run started that I didn’t eat beforehand and I only took half a Clif bar with me; oops. I managed not to eat too much junk though. Honestly. 

Nike+ Running Club Update #3

Another week goes by and more quirks are experienced.

Firstly, and perhaps most annoyingly, I had problems with the Apple Watch Nike+ during my long run last week. I was scheduled to run 13.5 miles (on a weekday morning which is, in itself, ridiculous) but at mile 5.5, the damn app just stopped working.

I tried to restart it on the watch but it came up as starting afresh. I didn’t have time to investigate too much as I wanted to complete my run, so I just started the app on my phone and continued for the remaining 8 miles. When I got home I checked in the log and it did at least still have the data for the first run. Phew. 

Then what do you do at the end? The training programme only lets you put one run towards the goal for the day. You cannot combine the efforts. So, after playing around a few times, I gave up and manually created an entry for the 13.5 miles and attributed that to the training plan.

On the Friday it had me doing a 4×400 meter speed run, with 4:30 mins recovery. It was only 21F outside that day so there is was no way that I was going to hang around in the cold for four and a half minutes between each set of reps. I did 1.5 mins and then started out again. This meant that by the last set I was pretty knackered. 

For the route, I found that the cul de sac behind my house was almost exactly 400m around the perimeter. The first run took 6:28… not too bad. The second was faster at 6:08 and then the following sets were back up at the 6:28.

Again, the speed run requires that you keep the phone in your hand so that you can press the button for the start and end of each rep. This makes me feel a little uneasy running hard with a cellphone in my hand.