How I Build

I don't default to a single stack. I choose tools based on the problem, the product, and the constraints.

Node and TypeScript are my default backend stack. I reach for Go when a service benefits from low overhead, predictable performance, or a single deployable binary.

Postgres for anything relational, MongoDB where a document model genuinely fits better, not by default. Redis for message queues, caching, and ephemeral data.

Enough to build a clean interface without fighting the tooling to get there.

The right-sized model for the job. One model reasoning, a smaller one handling a task it fits better.

I choose deployment infrastructure based on workload, cost, and operational simplicity rather than forcing every project onto the same platform.

Already using agentic tool-calling in SiteStamp. Going deeper into RAG and persistent agent memory, while exploring Cloudflare Workers for smaller services.

I prefer explicit validation, isolated boundaries, and tests around the parts of a system that are actually worth protecting.

I keep the development workflow lightweight and reproducible, with fast package management, containerized environments, and automated CI.