Most migrations don’t start because someone planned one, they start because half the organisation is already using something unsanctioned and you’re formalising it before it turns into a compliance problem. I’ve seen that across different types of tech, and the failure mode is always the same: the pilot gets all the investment and the rollout gets whatever’s left, which is usually not much. That gap is the rollout version of the question I came back to in Better Than What It Replaces: is the new thing actually better for the person who has to use it? ...

I’m not a web developer I’m a senior technical architect and my day job is application compatibility, migration, and platform modernisation, figuring out why software breaks when you move it between platforms and fixing it. The tools I reach for are Sysinternals, WinDbg, and Process Hacker, not CSS and JavaScript. Building a website from scratch wasn’t exactly in my wheelhouse. I’ve wanted a personal site for years but kept putting it off because I didn’t want something that looked like it was built in 2003 on GeoCities (though I do miss the flame borders). I also didn’t want to just use Squarespace or WordPress because I wanted to understand the build. When I moved into a strategy role last year where thought leadership is actually part of the job, the timing finally made sense. AI tools had collapsed the barrier too. What would have taken me weeks of learning web development took about two weeks of evenings and weekends. ...