Back

Uses

The tools and objects that currently earn a place in my day. I like things that reduce friction, make careful work easier, and quietly get out of the way.

Services

Where most of my work lands, gets reviewed, and eventually turns into a release.
My default place for small sites and frontend experiments because deployment disappears into the background.

Tech

Still the UI model I reach for when I want components, state, and product surface area to stay understandable.
The quiet safety net. It makes refactors calmer and forces useful conversations with future me.
Keeps tests closer to what people actually do in the interface.
My favorite tool for proving that important flows still work after everything compiles.
One less thing for humans to negotiate in code review.
Still shows up in a lot of the codebases I care about and know well.
Fast enough for sketching, precise enough for production, and easy to read once the patterns settle.
Useful when I want solid primitives without adopting a whole design system wholesale.

Editor

My daily editor right now. Fast enough to stay out of the way, helpful enough to change how I work.
Low-contrast enough for long sessions without making the code feel muddy.
Readable, compact, and familiar. I notice it most when I have to use something else.

Browser extensions

Keeps the web quiet enough to think.
Password management is not a place where I want personality. I want boring reliability.
A small mercy when debugging APIs directly in the browser.
Makes GitHub feel a little more like an editor when I am reading unfamiliar code.
Good for getting oriented quickly, especially when I want sources close at hand.
Still one of the fastest ways to understand what a React tree is really doing.
Helpful when performance feels off and I want a visual clue before digging deeper.
A pile of tiny GitHub improvements that I miss immediately on a fresh browser.
Useful when cache state starts hiding in the walls.

Desktop apps

The grown-up drawer for secrets, license keys, and all the things I do not want in my head.
My default browser at the moment, mostly because search and browsing feel closer together.
The model I reach for when I want a careful second mind on writing, code, or messy thinking.
Most useful when I want an agent to hold a codebase in view and work through a change with me.
Where I go to inspect intent, test layout ideas, and argue gently with spacing.
Quick recordings for bug reports, demos, and explaining what words would make slower.
Keeps external monitor brightness from becoming a daily annoyance.
A private place for notes that are not ready to become documents.
The launcher, calculator, clipboard, and tiny automation surface I use without thinking.
Where most open-source coordination and work chatter happens.
Mostly for focus blocks, walks, and the occasional playlist rabbit hole.
My default database client when I need to inspect data without making it a ceremony.
A terminal that feels tuned for command history, sharing, and long-running work.
Useful when a team still works through handoff specs and design assets.
Not glamorous, but dependable enough for distributed work.

Hardware

Motorized standing desk
I switch positions when focus starts getting stale. The movement helps.
Ergonomic chair
A boring investment that pays rent every day I sit down to work.
14 Core M4 Max / 14 Core GPU / 36 GB RAM / 1 TB SSD. Small enough to carry, strong enough to disappear.
Dual 27 inch 4K monitors on an arm. Space for code, browser, docs, and one thing too many.
Low-profile enough for daily use, tactile enough to make typing feel deliberate.
Comfortable, boringly good, and hard to replace once the shortcuts settle into muscle memory.
For calls, focus, and softening noisy rooms without making a production of it.
Mostly communication, photos, notes, and being reachable without being at the desk.
Paper slows my thinking down in a good way, especially for planning and rough sketches.
Travel insurance for devices. Heavy, useful, and usually worth carrying.