Monthly Archives: January 2022

Spoileriffic thoughts on Wandavision

I got a recommendation from a friend to watch the first three episodes of Wandavision in a block. That suggestion was solid. It’s slllooowww to get going, especially, if you’re not bathed in American sitcom culture. Fiona and I watched the first episode together and didn’t get much out of it. We started the second, and she bailed before we reached the opening credits, feeling it was more of the same. As a matter of pacing, I think they needed to bring the red helicopter into the first episode, so there’s something there other than a 1950s sitcom of the kind that 2020s TV has left far behind for a reason.

In fact, I wonder whether the best way to watch this show isn’t just to skip episode 1 completely.

Continue reading

Let’s be clear. To be honest. Putting it simply

When writing, or indeed speaking, do not begin sentences with any of these phrases.

“Let’s be clear” admits that, up to this point, you have been obscure.

“To be honest” implies that you’ve been lying until now.

“Putting it simply” suggests you’ve been making it sound more complicated than it is.

Your writing and your speech should always be as clear, honest and simple as you can make it. Clarity, honesty and simplicity are not optional extras that you can use occasionally to decorate your communication.

From the depths of time: a 30-year-old bug with a funny explanation

It was 1990 or possibly 1991, and I was working for System Simulation on an Application for Windows 2 – which at that time was a rather exotic extra that a few adventurous people were running on top of their MS-DOS systems. There was no graphical development environment in those days: you’d compile your program using the command-line C compiler cl, and compile your resources (dialogue boxes, menus and suchlike) using the command-line resource compiler, rc.

Continue reading