Uses

Tools & stack

What I actually reach for when I build. Nothing aspirational — every tool below is behind a project that shipped or runs in production.

The through-line: prefer self-contained, portable tools. A lot of what I make runs with no backend, no install and no build step, so the stack skews toward vanilla JavaScript and the browser's own APIs — with modern React/Next.js and serverless where a real product needs them.

01Languages

02Frameworks & libraries

03Browser platform APIs

The reason "no backend" is possible at all. These do the heavy lifting in my single-file apps:

04Hosting & infrastructure

05AI & automation

06Testing & workflow

Need an internal tool that runs without IT approval?

Let's talk. If your team is drowning in spreadsheets, there is usually a self-contained tool that fixes it.

Get in touch