What I use.

Daily driver. The fans never spin and the battery survives a full day of Claude Code sessions.

Training rig for SpatialDINO and follow-on cryo-ET work. FSDP across 8x H100 with NVLink + Infiniband.

One big panel beats two smaller ones for long context windows and large diffs.

Primary editor. Most of my code is now written in conversation, not in a buffer.

When I want a UI for tab-completion or quick edits across a few files.

fish for ergonomics, RTK to cut 60-90% of token spend on routine dev operations.

Long-lived sessions across remote training boxes and local agent runs.

The whiteboard for client discovery and architecture sketches. Nothing else has the same hand-drawn legibility.

Default for anything web. Strict mode is non-negotiable.

Research, ML, FastAPI services, glue scripts. Still the language of the field.

Distributed systems work. Boring, predictable concurrency.

Performance-critical CLIs (RTK). The compiler pays back the friction.

Apache Flink work. Not a love story, but the JVM is where the streaming runtime lives.

School. Still the cleanest way to learn what types should feel like.

Server components by default, edge when it matters. This site runs on it.

The default client runtime. Server Actions are finally usable.

Design tokens in the markup. Faster than naming things.

Async Python services with type-safe contracts. Default backend at Benmore.

When the client needs an admin and an ORM more than they need speed.

Training stack for SpatialDINO and everything cryo-ET adjacent.

Streaming runtime for the BU thesis on dynamic checkpointing.

Mobile for Cattle Logic. Offline-first ranches need a native shell.

Opus for hard reasoning, Sonnet for everything else. The split saves real money.

Authored the team skill library: planning, debugging, brainstorming, code review, frontend design.

My Rust CLI that intercepts Claude Code commands and rewrites them for token efficiency.

Backup editor when I want a graphical diff and tab-complete.

For comparing model behavior on the same prompt. Useful as a second opinion.

Deploy, edge functions, OG images. Zero-config for the frontend stack.

Payments for every Benmore engagement. Connect for marketplace flows.

Default storage. Boring is a feature.

Event streams between PCS microservices. The contract layer.

Embedded state for Flink and other streaming systems.

Error monitoring across web and mobile.

The only issue tracker that respects keyboard users.

Source of truth for code and reviews.

Hosting for arkashj.com and most client frontends.

Money in, money out.

Project management across Benmore engagements.

Long-form writing.

Older essays still live here.

Client comms. Pinned channels per engagement.