What this page is for
Some people like knowing what shapes a person's work. This page keeps that answer in one place instead of scattering it across build notes and side comments.
Uses / setup notes
What I use, and the kind of setup I keep coming back to.
This is not an exhaustive shopping list and it is not a private machine inventory. It is the public version: the stack I enjoy, the workflow habits I trust, and the kind of digital environment that helps me do calm, readable work.
What it avoids on purpose
No private account details, no over-specific hardware trail, and no pretending tools matter more than judgment. This is about working texture, not gear theater.
Current web stack
The site itself explains a lot about my taste.
The tools here are not random. I tend to like systems that stay fast by default, let the quiet parts stay quiet, and only spend complexity where the experience actually becomes better.
Astro first, React where it earns its keep.
I like content that ships as HTML first and interactive pieces that hydrate only when they are actually doing something useful. It keeps the reading experience fast and the playful parts intentional.
Cloudflare for the current runtime shape.
Pages, Workers, and Durable Objects are a good match for the current site because they let the visitor globe feel alive without turning everything into a heavy always-on app.
Three.js and Globe.gl when the interface should feel tactile.
I enjoy web graphics when they help a site feel memorable, not when they exist to bully the page into becoming a tech demo.
Work habits
The tools matter less than the defaults around them.
A lot of the feeling of good work comes from habits: small deploys, honest notes, readable writing, and feedback loops that stay short enough to keep momentum.
Plain text, Markdown, and notes that stay legible later.
I keep returning to formats that do not fight me. If an idea matters, I want it to survive copy-paste, version control, and my future self opening it months later.
Local checks first, small commits, clear change sets.
I trust a workflow more when it makes mistakes easy to spot early. Fast local feedback and tidy change boundaries are still more useful than dramatic release rituals.
Short updates, screenshots, and plain-language reasoning.
I like collaboration that leaves a readable trail. A good note should help the next person understand the decision, not just prove that a meeting happened.
Soft dark interfaces over sterile dashboard chrome.
I like warm dark themes, rounded edges, expressive type, and small playful details. If a digital space feels a little inhabited, I usually trust it more.
Low clutter, readable surfaces, and room to think.
I do better in setups that reduce noise instead of pretending noise is energy. Calm is not the opposite of ambition. It is often what lets the work stay precise.
No gear-flex page hidden inside this one.
I enjoy good tools, but I do not think credibility comes from collecting expensive nouns. The interesting part is still what the tools let you make.
Related pages
If you want the tools, the thinking, and the person from different angles.
The uses page explains the environment. These other pages explain the collaboration style, the design rationale, and the experiments themselves.