Skip to content
Uses

Tools I keep close to the work.

A practical snapshot of my development defaults. Nothing exotic here: the setup is meant to make code easier to inspect, change, verify, and ship.

01

Editor

I keep the editor setup boring: fast project search, TypeScript feedback, formatting on command, and enough keyboard flow to move between code, notes, and terminal without drama.

02

Terminal

zsh on macOS, with small aliases and scripts for the commands I actually repeat. The goal is less ceremony around checks, builds, and local debugging.

03

Languages

TypeScript and JavaScript are the default for this site and most web-facing work. I prefer typed boundaries and plain data shapes when code has to survive handoffs.

04

Local development

This portfolio is a Next.js App Router project with npm scripts for development, builds, and formatting. I keep static pages static unless a runtime dependency earns its keep.

05

Deployment

I favor simple release paths: build locally, keep configuration explicit, and make deploy-time assumptions visible. Static-first pages reduce the number of things that can fail at request time.

06

AI/dev workflow

I use AI as a pair for codebase search, review, refactors, and first-pass drafts, but keep the source of truth in tests, builds, docs, and local verification.