Uses

Tools earn their place.

This is the current setup. Nothing here is a universal recommendation. It is simply what has survived daily use.

Computer

The hardware that disappears once the work starts.

Computer

My main development machine. It spends most of its time docked to one good display.

Input

A compact layout with Caps Lock acting as a navigation layer.

Editors and tools I reach for every day.

Editor

Fast startup, focused interface, and enough extension support for the languages I use.

Terminal

A native terminal with sensible defaults and no need for a week of configuration.

Package manager

Strict dependency handling and a shared content-addressed store.

The inspection kit for work that crosses a process boundary.

Browser

The CSS tooling is still the quickest way I know to understand a stubborn layout.

Network analysis

For the point where a request stops being an abstraction and becomes packets.

Tools for scenes, diagrams, and images that carry an explanation.

Mostly geometry nodes, simple lighting studies, and technical diagrams.

Interface design

Useful for testing hierarchy and rhythm before turning an idea into browser code.

A deliberately small production stack.

Deployment

The journal builds to portable HTML, CSS, and small opt-in interactive islands.