My workbench

Tools I use as a front-end developer

A small, opinionated set of tools I reach for when building marketing sites, useful little products, and other internet projects. This is the real stack, not a drawer full of software I opened once in 2022.

The short list

What I build with

Updated as the stack changes.

01 · Framework

Next.js

My default for websites that need to be quick, content-friendly, and not painful to maintain six months later.

Why it stays: The App Router, server rendering, and sensible deployment story make it a practical fit for marketing sites and small products.

02 · Language

TypeScript

JavaScript, but with fewer avoidable mysteries hiding in the console at 4:57 PM.

Why it stays: It makes refactors safer and component contracts clearer, especially once a site grows beyond a few pages.

03 · UI library

React

The component layer underneath most of the sites and little internet corners I build.

Why it stays: It is still the best balance of flexibility, ecosystem, and familiar patterns for the work I do.

04 · Hosting

Vercel

Where I deploy Next.js sites when I want preview URLs, sensible defaults, and a boringly reliable path to production.

Why it stays: Preview deployments make review much easier, and the platform removes a lot of infrastructure ceremony for the kinds of sites I build.

05 · Design

Figma

For working through layout, visual systems, and the small details that make a site feel intentional rather than assembled.

Why it stays: It gives design and development a shared source of truth before the browser becomes the place where every decision gets made twice.

06 · Version control

GitHub

The place where projects live, changes are reviewed, and future-me can work out what past-me was thinking.

Why it stays: Issues, pull requests, and a good commit history keep client work and side projects understandable over time.

How I choose

Fewer tools, fewer weird surprises

The goal is not an elaborate productivity ritual. It is a stable, understandable setup that leaves more room for the part people can actually see and use.

  • Use the smallest tool that solves the actual problem.
  • Prefer a clear handoff over a clever setup only I understand.
  • Keep the stack close to what the next person can maintain.

A note on links

I only recommend tools I would use myself. Some links may become affiliate links in the future; if they do, this page will say so clearly before you click. Recommendations will stay independent.

See the small things I make