Uses

What I build with.

A running list of the tools behind the work on the projects page. It skews practical: most of this was chosen because it let one person ship and maintain a real product, not because it was interesting.

Languages

What I reach for, and roughly when.

TypeScript: Anything with a browser attached. Strict mode, and I lean on the type system to make bad states unrepresentable rather than to decorate finished code.
Python: Backends, data work, and integrations. The BizAnalyzer and Melody Map backends are Python 3.11 on Cloud Functions.
R: Statistics and exploration, mostly tidyverse and Shiny. Still the fastest path from a question to a defensible chart.
SQL: The part of data work that never goes out of style.

Web

This site is built with exactly this stack, so it is a working sample.

Next.js: App Router, static export. I default to static until something genuinely needs a server, which is less often than it looks.
React: Server components where they help, client components where they earn it.
Tailwind CSS: v4, configured entirely in CSS. Design tokens live in one file so a rebrand is a config change.
Base UI: Unstyled accessible primitives via shadcn's CLI. Not Radix, which trips people up when they read the code.

Cloud and infrastructure

Small teams should not run servers they do not have to.

Firebase / Google Cloud: Hosting, Auth, Firestore, and Cloud Functions on 2diff.io and Melody Map. This site uses only the hosting half of it: static files, no backend at all.
AWS: Where the R Shiny applications live.
Stripe: Subscriptions and metered billing, wired through the Firebase extension on both SaaS products.

AI and automation

I treat model choice as an engineering decision, not a brand preference, and I design for the failure modes rather than the demo.

Claude, OpenAI, and Gemini APIs: All three in production behind one routing layer in BizAnalyzer, so a provider outage or a price change is a config change.
Claude Code: Most of my building now runs through an agent harness: specialist agents, path-gated rules, and guard hooks. This repo carries one.
Podium: The AI text agent I use for after-hours customer messages. Automation that a non-technical team actually adopted.

Data and reporting

Getting numbers out of systems people already pay for.

Power BI: Trend and exception dashboards, mostly from my supervisory-controls years.
Quarto: Reproducible reports and publishing. The previous version of this site was Quarto.
QuickBooks and ServiceFusion: Not glamorous, but this is where small-business data actually lives, and integrating with it honestly is most of the work.

Inspired by uses.tech, which collects pages like this one.