I build complete products, and I build them fast.

How I work

Full products, not fragments

Front end, database schema, admin interface, auth, deployment, DNS. Projects usually stall in the gaps between specialists — those gaps aren't there when one person carries the whole thing.

Speed from tooling, not corner-cutting

Modern tooling has genuinely collapsed the mechanical part of building software. What it hasn't collapsed is deciding what to build and modelling it correctly, which is where the time should go instead.

I work in manufacturing

My day job is on the industrial side, not in software. I know what a changeover costs, why the schedule lives in a spreadsheet, and why the gap between what a system reports and what's actually on the floor is where the money goes. That context is unusual in someone who also writes the code.

Boring where it counts

Constraints in the database. Fail closed at trust boundaries. Static files where nothing needs a server. No dependency for something a few lines can do. The interesting decisions are worth agonising over; the infrastructure should be dull.