I'm an analyst, web at the core. My work is about the website and the people who use it: customer data, and making that site better, more accessible and more secure. I pull insight out of the tools and turn it into better decisions.
Alongside that, I build with AI - not in theory, but in practice.
This site is my workshop. Not a CV of job titles, but the things I actually make: an AI assistant that runs my task list, automations that run day and night on my own server, a knowledge base that makes two years of AI conversations searchable.
What I build has to be two things at once: it has to actually run, and I have to be able to explain it. I work at a large public-sector organization, and there you quickly learn that "it works" is only half the story. The other half is being able to show what's running, why you trust it, and where the limits are. That habit is in everything on this site: I measure instead of believe, I don't let AI do the math where a calculator belongs, and nothing goes live without me seeing it first. What that looks like in practice: How I keep my AI in check.
In an AI world you don't show where you worked, but how you think. That's what I try to do here: every project is an artifact, not a bullet point. Successes and downsides included.
