Skip to main content

Uses

Tools reveal how someone thinks.

A curated snapshot of my working setup. Less about a perfect shopping list, more about habits underneath it: fast feedback, readable systems, repeatable environments, and clear communication.

Daily engineering

Tools I reach for when I need fast feedback and low-friction iteration.

VS CodeZedTypeScriptNode.jsAstroReactTailwind CSS

Systems and operations

Infrastructure tools that help me practice production habits outside a narrow app surface.

DockerKubernetesTerraformAWSAzureVercelSentry

Data and backend

Default toolbox for services, API work, persistence, and internal workflow systems.

PostgreSQLRedisMongoDBREST APIsGraphQL

Writing and teaching

Tools that turn engineering work into material other people can inspect and reuse.

MDXFigmaCleanShot XNotionGitHubYouTube

Principles

Setup should make work easier to inspect.

Principle 1

Prefer tools that shorten the loop between idea, code, review, and verification.

Principle 2

Keep the stack portable enough that a project can move from laptop to CI to hosting without drama.

Principle 3

Treat documentation, screenshots, and diagrams as part of the engineering system.

Principle 4

Do not confuse a fancy setup with a better setup; tools should stay out of the way.

More context

Setup is part of the work.

I write about migrations, local environments, and operating-system choices when they change how engineering feels day to day.

Read setup essay