I ran out of usage in Claude on an afternoon and wanted to carry on working in ChatGPT, which I already use most days for Codex, but I quickly realised the two aren’t set up the same way. The surface comparison is easy. The harder part is what actually survives the move from one tool to another. ...
Back in May I wrote about asking ChatGPT and Claude where to put my circulator fan in my study. Last week the question was less relaxed and burning. The UK broke its June temperature record three days running, my study is a small room with the sun aimed straight at it, and I went back to both models to see if they could help. What came back read well and annoyingly didn’t work. Both kept telling me to aim the air just above my head, which puts the column over you, and when I said it wasn’t working they’d tell me to nudge it up a little more and that I was nearly there, pointing me the whole time at a placement that wasn’t going to achieve what they calculated. ...
The biggest change in chat models over the last two years is not the one most articles focus on. It is that they can now actually look at things. Image input went from a feature you would test once and forget about to something I use weekly without thinking about it, and the gap between describing a problem in words and just showing the model what you are looking at turns out to be much bigger than I expected. The first time it really landed for me was a few years ago when I started feeding ChatGPT photos of error screens and bits of hardware I could not be bothered to describe. By the time photo-based questions felt routine I had built up enough trust in ChatGPT specifically that vision tasks became one of the things I would default to it for, even as Claude took over for almost everything else I do. ...
The biggest change I made for this AWS recert isn’t which AI I’m using, it’s that I moved my study notes out of OneNote and into Notion. Back in March I wrote about studying with custom GPTs for the AI Practitioner. The note-creation GPT had grown a system prompt that read like a software spec, the coaching one had stayed simple and useful, and the post ended with me saying I’d try Claude as a study partner for the SA Pro and figure out whether to move my notes out of OneNote. ...
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. ...