Teach your kids about road safety. Next time, the artic might not stop in time…
Final day of the Week 2 runs. Nothing major, same routine as the previous two, but decided to push the jog speed up a bit compared to yesterday.
Busy day tomorrow, so probably won’t be doing my run tomorrow.
Training today was in a hotel in Dublin so on Treadmill which screws up the tracking of the ZenLabs app. Second day of the Week 2 set of runs
Started Week 2 runs. This week, 5 min walk, then 6 sets of 90 secs jogging, then 2 mins walking, then 5 minutes cooldown. This schedule was more effort than last week and felt better :)
Continuing to work through ZenLabs’ 5k app. Today, W1D3, 5min walk then 1min run/1.5min walk x8 and then cooldown.
A cold run today – bumped into a group of runners in the local park also doing intervals and they invited me to join them. Politely declined as they were doing small laps, and I wanted to do the larger laps.
Today, W1D2, 5min walk then 1min run/1.5min walk x8 and then 5min cooldown.
My opinion of Apple and its practices has never been high. But this is just stupid.
Type in “1+2+3=” in an iOS 11 device’s calculator app, and you get 6 (correctly), but type it in quickly (as demonstrated in this video) and you get 24.
Sure, it’ll no doubt get patched soon and Apple will twist the incident to prove how fast they can push out updates compared to Android. But the point remains – how did such a bug make it past testing? And what OTHER, similarly stupid bugs that have yet to be detected, also make it past testing. And what if one of those bugs was in something fundamental? Something that breaks the functionality of the device? Something like the 1/1/1970 bug that would brick the device, or even the infamous “effective power” bug that would annoying reboot someone’s phone. Or even the famous crashsafari site that was only meant to crash safari but managed to crash the device too (originally, anyway).
OR, was there even ANY testing?
You must be logged in to post a comment.