C25K Diary Part 4

If you’d told me a year ago that I’d leave the house early on a Saturday to run in a park when it’s barely above freezing, I wouldn’t have believed you. And yet that’s what happened this last weekend.

A year ago I’d just started my Couch to 5km adventure and it feels like a lot has happened in that time. Since my last entry in March, I’ve managed to both increase my speed, become more consistent and actually run a full five kilometres. With hindsight, I can see that I did much right but a few things wrong. As before, I think it’s worth writing about both as a help for people starting in the same place as me and as a reminder for myself. Knowing that I had difficulty keeps me going on days where I feel I’m doing badly!

I left my last post having completed the C25K programme but not having actually run the full 5K. (The programme helps you run 5K or for thirty minutes. That’s small print for you.)

My initial plan was to gradually increase my speed until I could run the full 5km in thirty minutes. That’s what I did for a while until I realised that it was going to take me a long time! So for one week I changed tack and concentrated on distance rather than speed. By that point it was actually quite easy but I’m glad I did it, if only to tick a virtual check box.

In trying to improve my consistency, the main thing I think I’ve learned is that I’ve been a terrible judge of how tired I actually am. There’s a difference between “not feeling it” and not being capable of running the full duration. With the benefit of hindsight, I could almost certainly have pressed on with some of the later stages of the C25K programme and finished sooner. Which is not to say that I think I erred; being cautious meant that I avoided getting injured. Doing exercise was (is) a bigger goal than completing a 5km run.

Around the same time, I’d started hearing about something called Parkrun. The arrival of spring and the desire for a change from running on a treadmill in the gym made me open to a change, even if it meant turning up to a local park early on a Saturday.

While I liked the idea, I didn’t want to find that I couldn’t finish or that people would sneer at me for finishing last. Turns out I misjudged the atmosphere and how competitive it would be. But I didn’t know, and I spent a couple of weeks trying to run outside before I even attempted it.

After all that time in the gym, I found running outside to be quite challenging. I had to pace myself rather than have the treadmill “force” me to continue at a known speed. Harder still, I had to plot my route in advance!

Having spent the rest of the year mostly running outside, oddly I now find running on a treadmill to be a challenge.

Back to Parkrun. After a couple of weeks practicing outside I went to my local in Tooting. I think I was expecting a handful of sporty people wearing Lycra sprinting around. What I actually found was over five hundred people of all abilities. There were the athletes but there were also people with baby buggies, teenagers and pensioners. Not only was I not out of place, but I didn’t even come in last place. And not even that but it was a supportive crowd meaning that my fears of finishing last were utterly misplaced. It’s not a race, it’s only as competitive as you want it to be. Oh, and it’s incredibly well organised, mostly run by volunteers.

This wasn’t supposed to be an advert for Parkrun. (Still, you should consider doing it.)

Since early summer I’ve stuck to doing two or three runs a week outside. When I started the running, my not-running days I typically went swimming. Recently I’ve started alternating that with some resistance training. But the running is still the “backbone” of my exercise regime.

What next? Well, winter is on the way so I’m interested to see how motivated I am to keep running outside! I still have no grand goal, no major objective to run a marathon or reach any particular race time. This is partly because exercise is the real goal but mostly because I want to be realistic. I’ve taken nearly ten minutes off my time for running 5km over the summer but, without some serious effort that I’m not likely to ever put in, constant improvement from here is going to be a lot harder.

But I’m going to keep trying!

Factfulness

I didn’t mean to immediately buy Hans Rosling’s “Factfulness“. I saw it in a “recommended reads” list (both Bill Gates and Barak Obama suggested it, if I remember correctly), thought it sounded interesting and went to Amazon to add it to my wish list. Fat fingers meant that I tapped the “buy” button instead.

Anyway. As an antidote to all the bad news around at the moment, I decided to read it right away. The narrative that the world is getting worse by many measures, this book argues, is false. I want to believe that we’re progressing but the pictures on TV of Trump and Brexit, famine and war make it hard to accept.

It starts with a questionnaire and, without wishing to steal the book’s thunder, most people will do incredibly badly at it. Worse, in fact, than merely picking answers at random, or “the chimps” as the book calls it.

I’d like to think that I’m better informed than many, if not than the general public than some chimps, but I still did badly!

The book continues with a list of errors that we all make, examples of them and how to spot and avoid them in the future. It sounds dry but it isn’t. Hans Rosling is humble, keen to draw attention both to where he made mistakes and where he made a difference. If anything, his modesty often sounds misplaced. I think it’s fair to say that he had more achievements than failures.

“I don’t tell you not to worry. I tell you to worry about the right things.”

The curse of this book, if there is one, is that we all think we’re well informed and that we don’t need to read it. The numbers show that we’re wrong. I hope that doesn’t make it the least read, most important book I’ve picked this year!

Apple Watch Series 4


This was going to be my first thoughts on the new Apple Watch, posted about a day after I unboxed it. But then life got in the way and I’ve now been using it for a week. What I’d planned to be a little more than a “hot take” is now probably a little closer to an actual review!

From the picture above you can see what I was using before. It’s not an Apple Watch, it’s not a competing smart watch. It doesn’t even have a battery. (To be clear, my new watch isn’t a replacement. I still plan to wear the Marloe.)

I’ll be honest: until recently I wasn’t very interested in the Apple Watch. It was too big, didn’t look nice enough, was another thing to recharge every night and none of the things it did were compelling enough to overcome those annoyances.

Here’s the thing. The Series 4 is still too big — about twice as thick as the Marloe — and doesn’t look as good as a traditional watch. But I’ve been on a health kick for the last year, so partly I bought it as a new gadget, a reward for keeping going for twelve months, and partly, because of that, the health features became compelling enough.

As you’d expect for Apple, the hardware looks great and is well presented. The finish is beautiful, the controls click and rotate in a satisfying way. I found it odd that it came without the strap attached but I was able to get it up and running pretty quickly.

I’ve read about the Watch before but I’ve never got beyond playing around with one in a store. It surprised me how complicated it is. By which don’t mean it’s hard to use, rather that there are a lot of choices to make. Choices that you probably won’t know the answer to.

The new Infographic watch faces sound great, but what am I supposed to do with eight complications? Not having used the Watch before, I don’t know the best way of accessing apps versus having the information available instantly on the watch face. Should I use the app swarm? The most recently used list? Complications? Notifications? Then you find that some complications only appear in some locations. How am I supposed to know this stuff? It’s confusing. I’m sure I’ll figure this stuff out but I feel information overload just as I’m trying to play with my new toy. (Having started writing a Watch app I think I understand it better, but should I have to?)

I guess I was expecting an iPhone OS 1.0-type experience — just the bare minimum — but I suppose that’s an unfair comparison and an unfair expectation. We’re now at watchOS 5, so it’s had time to evolve. And in hardware terms the Watch is way faster than than the first few iPhones. (It is incredible that you can get a dual core 64-bit CPU on your wrist!)

Having waited until now to get a Watch, I’ve also seen features that I was concerned about. The main one: the not-always-on screen. Would I forever be wiggling my wrist to see the time?

No, is the short answer. It’s not 100% successful turning the screen on at the right times but it’s pretty close. The problems I’ve had have been more along the lines of the screen not staying switched on for quite long enough. Maybe I was too slow to read a notification, or I was showing my wife something neat, but I do occasionally find myself wiggle my wrist around just as I feared. Fortunately the times it happen lead me to think that, as I use the watch more, these occasions will happen less and less. I could be wrong, but I think this will work out fine.

Another example of complexity: if I want to go running, what app do I start? Strava is the obvious one. That’s what I use on my phone. But what about the Workouts app? Do I need that instead? As well? One of the features that attracted my to the S4 was the ability to see my pace for the last kilometre… but how do I get that while recording my GPS trail? Clearly this isn’t an insurmountable problem, but it’s one without an obvious solution. Some experimentation will be needed.

However, putting the niggles and unexpected complexity aside, how has it been? My experience in this first week has been great. Being able to quickly glance at notifications without pulling out my phone has been very handy. Walking around a strange city with it tapping my wrist with the directions is way more convenient, as are the notifications telling me which gate my flight boards. And being able to record a run without clutching my phone or have it strapped to my arm is surprisingly liberating.

I’ve heard people say that Watch apps are not great. Maybe that’s true on average but I’ve been impressed with Strava and, especially, Overcast.

All these things are slight reductions in friction or increases in convenience and are not necessarily compelling alone but when you add it all up it’s impressive. On paper, I thought the features were nice but not quite worth the asking price. I would still say it’s a luxury rather than a must have but the utility is certainly there.

How not to be a boy

I’m not generally big on memoirs or autobiographies, but I’ve liked a lot of things Robert Webb has done and the title “How not to be a boy” worked for me.

There’s a lot I can relate to in here. I may not have wanted to be an actor or comedian but there are definite parallels to people, like myself, who were not interested in “boys” things like football. While that’s not necessary in a memoir, it did make the more rant-y, less autobiographical parts make sense to me.

One of the things that most people wonder when they watch Peep Show is, how much of the characters are, well, characters and how much is the actor. This book doesn’t really help. There are paragraphs where you can totally imagine it coming from Jeremy. Is that Webb playing to his audience or is it really him? We still don’t know.

I guess it’s good to know that there are people out there like you, who don’t fit the social norms of what a real man is supposed to be. In that sense, maybe it’s a bit late for me (like the book for introverts, Quiet, I already know that!) but it might have been helpful to a teenage me. Then again, when I was that young I probably would never have watched Peep Show or That Mitchell and Webb Look, and therefore wouldn’t be interested in this book. A catch-22…

Overall, it’s mostly well written, there’s a narrative connecting it all together (unlike many memoirs), but I wouldn’t say that it’s “must read.”

iOS 12

As I’ve done for the past few years, here are a few thoughts on the new version of iOS that will be heading to your phone in a few days. Usual caveats: my usage patterns are probably different to yours, I have a 6s and iPad mini, not whatever weird and wonderful hardware you have. I’ve been using the beta on my iPad since early August and on my iPhone since late August.

The good

  • Stable. I’ve had a couple of minor glitches but, honestly, there have been worse release versions. (They have been fixing new APIs and suchlike so I’m not saying they should have released earlier. But I am saying that the GM version should be pretty solid.)
  • Performance. As advertised, it works well on my far-from-new devices, probably better than iOS 11. I didn’t buy into the whole battery-gate scandal but if this is the result I’m happy with it.
  • Siri suggestions. I’ve not seen the full benefits yet, since I’ve not finished writing my own and haven’t been running anyone else’s beta software. But even just with Apple’s suggestions it’s nice. I go to the gym and it suggests my “gym” notes document. I think this is going to be big when more apps support it.
  • Do not disturb. I already used it a lot and now it’s better. DND until the current meeting and DND until I leave the current location are both super useful.

The bad

  • Nothing. Really. Sure, there are things that I would change or do differently, but there’s nothing that I would really look at and say “That’s worse than iOS 11.” If you’re okay with iOS 11 there’s no good reason not to update.

The ugly

  • What’s with the time and battery indicator being jammed in the very top left and right of the iPad screen? What a waste of space.

Final words

You’ll note that “Screentime,” Apple’s answer to the accusations that people are spending too much time on their devices, is not on the list. I don’t have anything bad to say about it, but I didn’t find it very useful. I have my smartphone addiction under control. I could stop any time I want to…

Pro is not a useful label

Here is goes again. Apple announces new MacBook Pros (or there are rumours about a new Mac mini pro) and the hoards pile on it saying it’s not a “Pro” machine. But what does that actually mean?

Traditionally the label “pro” is short for professional and is used to describe people who make their living using the tool. Sadly that definition is so ridiculously broad that it’s not terribly useful. What does a video editor, a writer, a 3D modeller and a software developer have in common?

Nothing.

Some need a fast CPU, others lots of memory, or storage or ports or GPU. Others just like the “best.”

And that’s the problem. We have to stop fixating on it being short for “professional.” It’s a marketing term, nothing more. It doesn’t mean anything beyond “expensive.” Just because it’s missing a feature that you’ve grown accustomed to does not mean that it’s not usable by professionals. Maybe it makes it unusable by you but that’s not the same thing at all.

If you work on a computer, buy the one the best meets your current and anticipated future needs. Whether that’s a MacBook or a Mac Pro, a Mac mini or an iMac Pro, even a Windows PC, the name doesn’t matter.

And if none of the computers in Apple’s current line up meet your requirements, that might legitimately be a problem. But, it’s not a new problem — Apple has had a relatively limited range since at least the late 90’s — and that still has nothing to do with the name.

Photography, opinions and other random ramblings by Stephen Darlington