How I work
Day-job engineering: TypeScript, Astro, React, services that stay up, plus the odd Python or C# system. Agent and LLM pieces show up when they replace toil — orchestration, evaluations, guardrails.
If the brief is fuzzy, I will usually propose a small feasibility pass before anyone locks scope. When the deliverable is mostly pages and static content, I often reach for Astro and Cloudflare at the edge. For APIs, native clients, or existing stacks, the tooling follows the constraints of the project.
Interfaces & apps
Product and internal UI — scoped so you get something shippable, not a science project.
Websites & edge
Marketing sites, forms, lightweight server logic — good fit when speed and running cost matter.
Automation & agents
Workflows off spreadsheets; agents tied to tools and data you already trust.
Polyglot maintenance
Can read most stacks; happy to own a migration or pair until your team takes over.
Architecture notes
Short trade-off write-ups when you need a second pair of eyes before hiring a bench.
Vendor sanity check
Help translate sales demos into what is likely deliverable on your timeline.
Work together
Send a short brief — what you need, rough timeline, and your budget or range. Let's find out if we're the right fit together!