Stack

Languages, frameworks, and cloud tools I use in production — with when I pick each one and why it fits the problem.

The right tool, not my favorite tool

I choose based on the problem, the timeline, and the budget — not on what I used last time. Go, GraphQL, Next.js, or Angular only earn a place when they fit the product.

Built for the traffic you'll actually have

I size decisions to real load and realistic growth. No over-engineering for scale that isn't coming, no corners cut where the UI will hurt later.

Aware of the investment

Every choice has a cost — money, time to market, and the people who maintain it after me. I weigh those before I write a line of code.

I adapt fast

Drop me into a new domain or an unfamiliar stack and I get productive quickly, then go deep enough to ship something sound — and keep the frontend team unblocked.

Tap a tool to see why I choose it and when

Backend

Where I'm most at home. I pick the language for the job and treat frameworks as interchangeable — the shape of the problem matters more than the logo on it.

Languages

Frameworks

ORMs & data access

Validation & schemas

APIs & realtime

How services and clients actually talk. I choose the contract style to match the client, the latency, and how tightly the two ends are coupled.

Databases & data

I model data carefully and write SQL by hand — deliberate, advanced queries, not whatever an ORM guesses. I choose the store based on access patterns and how it will scale.

Serverless & cloud

Where the code runs and what manages it for you — from full cloud providers to serverless platforms and backend-as-a-service.

JS runtime & toolchain

Picking the right runtime and package manager matters as much as the framework — I choose based on deploy target, team habits, and how fast we need to move.

Build tools & compilers

Fast feedback loops and predictable production output — I pick bundlers and compilers based on project size, ecosystem fit, and how much config the team wants to own.