Now, Nike suggest I drop out of the plan, uninstall the app, reboot, reinstall the app, then put a new one in, so I’ve done that, but that’s now reset my training plan, and Nike+ training plans always start on a Monday, so that means, no plan run today. :/
Interestingly, the last one caught my attention. Here’s the main description:
Recently two members of Team T3 did the same half marathon using the same training plan with the same app. They trained twice together and noticed one of them was recording about a mile less than the other each time. There was no way to test who was being short-changed in their preparation until race day, when one of them hadn’t done enough training and nearly died in the last couple of miles. Lesson: don’t trust apps, trust watches.
“Don’t trust apps, trust watches”? I kind of expected that. After all, a phone is not built to be used as a GPS receiver (even though it is a function), whereas a GPS watch is designed for that function. I have run with the Nike+ app and my SportWatch on at the same time, and have noticed a difference of around 0.2 to 0.25 km between the two. Most of the time the app clocks up more mileage than the watch, but I trust the watch more because it is a dedicated GPS receiver.
Added to calendar. I will probably do the same thing I did with Matt Smith. Watch the first couple of episodes to decide whether or not I like Peter Capaldi’s Doctor, then decide whether or not to stay watching thereafter.
Like it or not, Germany totally outclassed Brazil last night, and the goals came thick and fast. The commentators summarised it bluntly, and concisely after goal 3: "Brazil are being humbled, humiliated, and ripped apart". 5 goals in 30 minutes. I went to bed even before the first half had finished. From the sounds of it, some of the Brazilian fans felt the same way. There really wasn't any need to watch the rest of the match. Well, it looks like I missed 2 more goals by Germany and one consolation goal by Brazil.
But, interestingly, according to the Guardian, plenty of records fell during that match (taken from the referenced article):
179
Seconds between Germany’s second and fourth goals in Belo Horizonte
7
Germany are first side to score seven times in a World Cup semi-final
94
Years since Brazil lost by a six-goal margin (6-0 to Uruguay in 1920)
29
Minutes it took Germany to score five, the fastest ever at a World Cup
16
Goals scored by Miroslav Klose at World Cups, beating Ronaldo’s record
5
The amount of goals scored by England in the past two World Cups
223
Number of goals scored by Germany at World Cups. Brazil have 221
3-0
Brazil’s heaviest defeat at a World Cup before last night, in 1998
12
World Cup matches it took Thomas Müller to get to 10 goals
6
Number of assists provided by the Bayern player in those 12 games
0
Shots on target by Luiz Felipe Scolari’s side in the first half
69
Seconds between Toni Kroos’ two goals. Fastest in tournament history
Apparently, the most sought after language is Java. Not that surprising considering it powers quite a few things, including Android and anything running Android (well, to a point, I guess since it doesn't run Java in the same way that you would run the JVM on, say, your desktop.) Still, gives me a reason to brush up on it. And perhaps work towards a Java certification. I did have J2CP, but that was years ago, so I'm not sure if it is even valid any more.
Although it surprises me a little that Ruby and Perl aren't on this list.
I haven’t used the Nike+ Running app for a long time, since getting a SportWatch. However, I dug it back out after starting to use the Nike Training Club app (as it ties into the Running app to check you have done a running workout). Now, Nike have put in a coach with plans for 5K, 10K, Half Marathon, and Full Marathon distances. Interesting.
I’m starting off with the 5K, and using the Intermediate plan (aim to beat personal best)