This post has been in draft for some time and to be honest it’s been long enough now that I don’t know exactly what I had planned to write.

SO WHY WRITE IT? I hear you mumble. Well, that’s a good question, but it’s not how my OCD allows me to operate. There was a reason.

So for now, though, until my memory sorts itself out, I’ll just explore the topic a little, and maybe update it again in the future.

Initial thoughts on Hugo vs Wordpress

The move to Hugo from Wordpress was a long time coming but also a little impulsive. I’d used Wordpress for a long time and had become accustomed to its pros and cons. It’s too soon to talk confidently and about good or bad bits, so here are just some observations.

Also, it’s worth pointing out this quote that sits on the official Hugo forums which neatly encaptures the intended users of Hugo:

Migrating from Wordpress to Hugo

Important caveat: I am not a Hugo expert. I almost said not yet. But I doubt I ever will be. I am literally winging this. The main Hugo site is really good and far better than this site.

Migrating from Wordpress to Hugo was actually a reasonably straight-forward process. There are plenty of articles out there covering it and I was following this one and this one- which also does a nice job of why you might want to move to Hugo (or a static site) in the first place.

2022 update… with a fresh new look

OK bear with, this could take a while as I am currently writing this all in markdown. Or at least attempting to. I haven’t published in this way in at least 20 years since University days where it was popular to use LaTeX for typesetting scientific articles. For at least the last 10-15 years I’ve been using Wordpress as the CMS platform for this blog and, as we shall find out, for one reason or another I decided it was time for a change. So this may end up being a mini-series on how and why I moved my blog from Wordpress to Hugo and any experiences or observations along the way.

If you’re trying to configure Word Automation Services (esp. for use in the PDF Nintex tasks) then you may have used my previous post on the topic as a guide. Not seen it? It’s nice.

We recently upgraded a SharePoint environment but despite following the guide and configuring Word Automation Services and so on, workflows (or anything trying to use WAS) were failing with the error “there is no word services application proxy configured for this site collection”. All a bit odd because it all looked to be setup correctly.

It’s a Neff (aka Bosch) double oven with a slide-hide-door. Not sure of the exact model, but it looks like this.

About a year ago, it stopped working - on the CircoTherm setting only. All other heating modes were fine, and it would randomly occur sometime after switching it on but usually around 10 minutes. It would stop with some beeping and an error code - E6200 - on the screen.

Usual Googling turned up very little. You would think a fault code would be written down somewhere and exist - but there was nothing specific for this. In fact, all I found was this post on UK White Goods and this on Just Answer.

This was today:

Guernsey’s answer to a (half-)IronMan is the GraniteMan - a 70.3 style triathlon in Guernsey.

Here’s my bum.

Finished in a fairly respectable time. Well for me, anyway.

A story of when abandoned tech gets assimilated for undesirable purposes. AKA when I inadvertently created a massive open spam proxy. (Although in fairness I can also now say that I have created a site that was creating literally thousands of hits per minute… which is pretty huge.)

Let’s start with some excuses

(Warning: large amount of, shall we say, “scene-setting“.)

I don’t claim to be a web developer. Or certainly I don’t claim to be a very good one. Despite what some of my friends and family may think, it’s not what I do for a job. I know a little bit about a little bit but I am miles behind what some of the bigshots can do with the web nowadays.

Update: 06/01/2022

Just tried this all on macOS 12.0.1 (Monterey) and it was all fine. The only difference was that (a) Homebrew moaned that Xcode was out of date, so that needed a 12gb update, and (b) Powershell moaned about using stuff from an untrusted repository. In the end I trusted PSGallery by using:

Set-PSRepository -Name 'PSGallery' -InstallationPolicy Trusted

In fact the only real issue was the horrific shade of yellow that the highlighting decided to use for cmdlet names!

A vaguely tech-related philosophical-ish thought-piece.

Tedious irrelevant tech challenge #7582: I still buy music. On physical media. CD mainly.

Tedious philosophical quandry #29: are streaming services eroding our emotional connection with music?

I don’t know why I still buy physical media. The economics of it don’t really make sense when compared with all the kool-kidz streaming stuff that is available nowadays. I can buy one album for around a tenner. I can buy a month’s streaming service of near-infinite music for around a tenner.