Too much nerdery took place from Monday February 20 to Sunday March 5. Fortunately, be the end of that period, we found ourselves here:
The view from the shark lookout all the way to Hangklip.
For a technical report, I thought it would be handy going from Emacs orgmode (where all my lab notes live in any case) to PDF via LaTeX.
The week of Monday February 13 to Sunday February 19, 2017 might have appeared to be really pretty boring to any inter-dimensional and also more mundane onlookers.
(I mention both groups, because I’m almost sure I would have detected the second group watching, whereas the first group, being interdimensional, would probably have been able to escape detection. As far as I know, nobody watched.)
I just went through my orgmode journals. They are filled with a mix of notes on the following mostly very nerdy and quite boring topics.
It turns out that when you, or one of your offspring, accidentally drop an Apple TV 4 remote from about a metre, the lovely touch surface shatters almost exactly like the screen of a smartphone:
Unfortunately, you now have to purchase a new remote, which over here is going to cost more than half of what the whole Apple TV unit, including remote, cost initially.
This WHV is all about the weeks from Monday January 30 to Sunday February 12, 2017. I’ve mostly been in heads-down mode on two projects, so this post will be shorter than is usually the case.
I had my very first beer after the 30-day long Experiment Alcohol Zero (EAZ) on Friday, February 3. It was a good one:
EAZ has taught me that it would not be the worst idea to limit alcohol consumption slightly more.
I’ve been spending some time doing research on the relative (perceived) performance of flagship Android phones compared to iPhones. I will probably not write the extended post I was planning to, as it seems that it’s hard to answer this question scientifically, and, perhaps more importantly, it makes people Very Very Angry.
I would still like to leave you with some interesting reading material. Hence this quick note.
From this discussion post (December 2016) by CodingHorror, aka Jeff Atwood, one of the two founders of the whole StackOverflow empire, where he measures the relative performance of his discourse web-app, the following choice quote:
Today it happened again.
A Lie Can Travel Halfway Around the World While the Truth Is Putting On Its Shoes
(quote not by Mark Twain, origin quite interesting)
Someone on facebook forwarded an article that was full of badly written and utterly unsubstantiated conspiracy theories about topic X. (topic X could be anything: politics, health, whatever)
To me, it was instantly clear that the article was 100%, undiluted, hogwash.
Now you probably think that I must have decades of experience separating the internet wheat from the chaff.
Monday January 16 to Sunday January 29 of the year 2017 yielded the following possibly mention-worthy tidbits:
On Saturday, January 21, we had the privilege of seeing Herman van Veen perform live at the Oude Libertas Theatre. The previous time was a magical night many years ago in the Royal Theatre Carré in Amsterdam.
Herman van Veen is a living, extremely active and up to date legend. To most Dutch people you’ll ever meet he is a formidable part of their rich cultural landscape.
Update 2017-05-02: As reported by Kjetil in the comments, if you update the Health apps in the GEAR category of Galaxy Apps, this should fix the problem without having to change your phone’s language. I’m keeping the rest of the post here as a record of events.
This is a really short note to help other people trying to get their broken Samsung Gear Fit 2 voice “guide at intervals” to work.
WELL HELLO THERE FRIENDS FROM THE BLOGOSPHERE!
It’s definitely time to get out a Weekly Head Voices, so that we can all feel nicely up to date. This post covers the period from Monday December 5, 2016 to Sunday January 15, 2017, which is ever so slightly *cough* later than average.
My excuse is: SUMMER HOLIDAY.
If you have not yet read my 2016 to 2017 transition post, this is a gentle reminder to make some time to do so. There’s some backyard philosophy in that post that you might find useful.
For the past few runs, I noticed that my Gear Fit 2 would only lock onto GPS after more than 0.5 km. By “noticed”, I of course mean “got super frustrated with and considered briefly throwing the gadget onto the ground and arranging for its utter disintegration through repeated jumping on it”.
Besides losing the first 0.5 km of my run data, the pacing information, delivered via synthesised voice, would be wildly inaccurate for the rest of my run.