Design.
Problem
What actually needs solving, and what does not.
Architecture
The shape of the system, decided before anything is written.
Infrastructure
Servers, network and storage sized to the real workload.
I design, build and run AI infrastructure, real-time platforms and automation—from first sketch to production.
Most technical work stalls between the whiteboard and the server. I stay responsible for the whole line.
Inside my approachWhat actually needs solving, and what does not.
The shape of the system, decided before anything is written.
Servers, network and storage sized to the real workload.
Services, APIs and the data model underneath them.
Dashboards and controls someone else can operate safely.
Models wired in only where they earn their place.
Repetitive work removed, with verification built in.
Health, alerting and honest failure states.
Live, owned, and still my responsibility afterwards.
Python · TypeScript · JavaScript · Bash
React · Responsive interfaces · Dashboards · Real-time UI
FastAPI · Node.js · REST APIs · WebSockets
Local LLM deployment · GGUF · Quantization · Agent architecture
Playwright · Browser automation · Workflow orchestration · Event-driven processes
Linux · Docker · Nginx · GPU servers
Architecture, infrastructure, code, deployment and the pager afterwards. Systems fail at the seams between people.
Automation reports what it thinks it did. Independently checking the resulting state is what makes it trustworthy.
Infrastructure only one person can run is a liability. The goal is an interface someone else can use safely.