I updated the build project for this blog recently, as the engine used to generate it was updated. But doing that caused an issue which I think others might bump into. So here's an explanation of what I saw and how to fix it:
It's been a while coming, but over the last couple of months I've finally gone throught the process of migrating my blog content off WordPress and onto a statically hosted site. A few people have asked me why I'd go to the trouble of doing this, so while I'm having a festive break from proper Sitecore stuff, I thought I should write about my reasoning:
My QA team had a deployment issue recently, where Azure DevOps failed to successfully release to a couple of servers. The reason for the failure wasn't obvious to me immediately, so here's a quick write-up for Google, in the hope it saves some other people.
Outside of work I've been looking for non-Sitecore things to experiement with recently, and my eye was caught by a bit of interesting game development technology. I came across a discussion of using code to generate game data with a technique called "Wavefunction Collapse". It's a simple concept, but it has some interesting results, so I thought I'd have a go at an implementation myself.
After I presented at a couple of user groups recently, some people asked me about how I organised the video demos in my deck. It's a question I've been asked a few times over the years, so I figured this might be a good time to answer it...
While developers would love to avoid ever writing documentation or reports, it happens to us all. One of the most frustrating bits of this can be getting the formatting to work as you'd like in Word – and I got bitten by this recently. So, as a memory jogger for my future self, here's how to deal with misbehaving heading numbers:
Having spent some time deploying instances of Java for Solr servers recently, I came across two things that wasted my time. So...
I love that lead to some fun... So I moved eagerly to Let's Encrypt when the tooling supported Windows reasonably well, and set myself up with a certificate with multiple SANs authenticated via their "HTTP proofs" mechanism, and it all worked fine, despite it being a bit of a pain that I had to expose port 80 for sites I only wanted accessible via port 443.
But I realised recently that they now offer wildcard certs that would make my life simpler, and that there is now decent support for DNS-based proof-of-ownership. So recently I tried moving my server over to this model – and there was a bit of friction. Entirely PEBCAK though – so I'm writing this down for the next time I forget how DNS works 😉
When I wrote my first blog post here ** in February 2014 I definitely did not imagine still being at it 200 posts and five-and-a-bit years later. Originally I set myself a challenge of writing something once a week for a year, just to see if I could motivate myself to do it.
Honestly, I didn't really think I'd manage to keep it up for the entire twelve months, let alone still be here now – but somehow it's become part of my routine. I may have scaled down to a post every fortnight, as kids and other responsibilities took over more of my time, but the process of making myself notes about issues I encounter as I'm working, and then writing them up when I have free moments has become part of my working life now...
It struck me the other day, that I've now been a full-time remote worker for more than ten years. As the technology for working away from company offices slowly gets better, I'd like to hope this approach to work was getting more common. After all, it has the potential to save companies money and it has the potential to give you back a couple of hours of your day that you don't need to spend commuting.
So just in case anyone else is thinking about trying working this way, I thought I'd have a go at setting out some of the challenges I've had to address over the last decade.