Ai

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. ...

The Register reported that UK entry-level tech roles fell 46 percent in 2024, with projections hitting 53 percent by the end of 2026, based on figures from the Institute of Student Employers. Most of the commentary points at AI as the cause, and AI is doing something, but the ladder into architecture has been eroding for over a decade and the AI piece is just the wave you can see right now. The earlier waves were quieter and they did most of the damage well before agents showed up. ...

The AI Builders Breakfast Before the main programme opened there was a smaller invite-only session called the AI Builders Breakfast, which I hadn’t known about when I wrote the pre-Summit piece and only found out about after. It ended up being the part of the day I got the most out of. The room was smaller than anything else I sat in all day and the conversations were about what’s actually hard rather than what’s being announced. ...

I’ve been to plenty of vendor events and briefings over the years but never an AWS Summit, so heading to London on Wednesday for the first time I genuinely don’t know what to expect. I’m planning to get there when doors open at 8am partly to beat the keynote crowds and partly because I’ve already had to make some hard choices about how the day runs. Picking the Sessions I had four sessions I wanted to attend: the keynote on agentic AI, a workshop on rapid prototyping with Kiro, a zero trust for AI security session, and a fast-track VMware migration workshop. Some run 2–3 hours, the zero trust session clashes directly with Kiro, and doing all of them would mean spending the entire day in rooms with no time to actually see any of it, so I’ve cut two. I’m skipping the keynote, which at my first AWS Summit feels like it should be a bigger deal than it is, and dropping the AI security session because it runs at the same time as Kiro and that’s not a close call. The keynote will be streamed and I’ll catch it later. The VMware workshop and Kiro are what I’m actually there for. ...

I came across AI Warehouse while studying for the AWS AI Practitioner cert through the Stephanie Maarek course. I lost a few hours on their YouTube channel watching reinforcement learning agents figure out games from scratch, and when I found they had a downloadable Windows simulator I wanted to try it myself. Their Red Light, Green Light scenario, the one from Squid Games, lets you run different shaped agents through the course and adjust the training parameters to see what changes. ...

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. The hard part of a migration is usually the stretch between a successful pilot and a real rollout. ...

I’ve held AWS certifications since 2019, starting with Cloud Practitioner and then working through Solutions Architect Associate, SysOps, Developer Associate, and Solutions Architect Professional within about a year (It was Covid year after all). I recertified the SA Pro in 2023 and passed the AI Practitioner in February this year. The SA Pro is due again, exam’s booked for end of June, so I’m back studying. My study method has been the same every time, which is watch a Stephane Maarek course on Udemy, make notes in OneNote as I go, grind practice exams. The notes are dense and compressed, topics separated by slashes, exam questions dropped in wherever they’re relevant. The formatting is all over the place because it’s written for speed of recall, not for anyone else to read. I’ve used this approach for every cert I’ve passed and never had a reason to change it. ...

I’m recertifying my AWS Solutions Architect Professional cert for the second time right now, so when I decided to build a personal site the temptation to go straight to Route53, CloudFront, S3, and Terraform was real. I asked ChatGPT, Claude, and Gemini what they thought before starting, and while they disagreed on a few things they all said to use GitHub Pages and not overthink the hosting. Gemini included a cost comparison that had an EKS cluster as one of the options at £150-200/month, which is overkill for basically any website, but it helped make the point that GitHub Pages with a custom domain was the obvious starting point. I could have spent weeks on infrastructure before writing a single post, or I could just start writing. ...

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. ...