About

I'm a software engineer who has worn a few other titles on the way: process engineer, systems engineer, and now software architect. The job was always the same underneath — find the actual problem, then design the smallest system that removes it. The title just describes the altitude.

I started shipping software long before AI tooling existed, and I work in manufacturing by day — an industry where a wrong assumption becomes scrap you can hold in your hand. That background shapes how I build: understand the domain first, design on paper, verify with evidence. The case files on this site each start with a real problem from a real domain — PCB pre-production, UK building regulations, animal welfare, trading card games — because dropping into an unfamiliar industry and building the right tool for it is the part of the job I'm best at.

These days I multiply myself with AI agent fleets — up to a dozen working in parallel under scoped briefs while I architect, review, and verify. I'm open about that, and because I've done this work without the tools, I can tell when the output is wrong. How that works in practice is on the How I work page.

The stack is usually C#/.NET and Blazor with hand-rolled rendering — raw WebGL, Canvas2D, Web Audio — and as few dependencies as I can get away with, often none. When I want to understand something, I build it: the grid, the terminal framework, the MQTT client, the synthesiser. The leftovers live in the Lab (try the theme switcher in the nav while you're here — that's home-built too).

Contact: andrewwigman2@gmail.com