What I
run on

The Mac mini handles infrastructure: self-hosted services, runners, home lab workloads. The MacBook Pro is the dev machine I write code on.

The IDE for backend work: Java, Node, databases and the rest. Refactoring, debugging and code navigation I trust on a large codebase, and still where I read code an agent wrote before it goes anywhere.

The same JetBrains muscle memory for TypeScript and Angular. Where the web side of every app on the building page gets read, debugged and tidied.

My current favorite agent. Terminal-native, MCP integrations let it reach into the rest of the stack in ways that change how I work.

In regular rotation alongside Claude Code. I switch back and forth depending on the task; both have their strengths.

Local model runtime. Running open-weight models on Apple Silicon for tasks that don't need cloud: code review, summarization, home automation scripting.

TUI coding tool with plugin support. Pairs well with local models via llama.cpp when I want to keep things offline.

Desktop and web interface for OpenCode. Same agents, same local models, with a proper chat UI and sessions I can pick up from another device.

The SSH client on my Android phone. When I'm away from the desk it's how I check on a server, watch a deploy or run an install, reaching the machines over the tailnet rather than the open internet.

A small open-source VNC viewer for Android. When a terminal isn't enough it gives me the Mac's screen from my phone, again over Tailscale.

Docker and Linux VM management on Mac. Replaced Docker Desktop: faster, lighter, and doesn't demand your soul on startup.

Self-hosted Git. This site is deployed from a Gitea Actions runner on a Mac mini. Full control, no external dependencies for the pipeline.

The private network under all of it. Gitea, the runners and the home lab are reachable only over the tailnet, and a dev server on the laptop opens on a phone or tablet without exposing anything to the internet.

Several, each with one job: network monitoring, local services, automation endpoints.

For the things that can't live on-premise: external services, droplets that need a real IP, managed databases when warranted.

Self-hosted OpenID Connect provider with passkey sign-in. One identity across my apps: single sign-on for the family board, the party invites, the dairy analytics and the flashcards, and the token issuer behind the board's MCP server.

This site's host. Simple shared hosting for a static site that does exactly what it needs to.

The brain of the house. It's slowly replacing the corporate cloud apps I used to depend on with local automations I control.

Sensors, switches, plugs: a mix of brands unified under Home Assistant. Local protocols preferred over cloud-dependent alternatives.

Shifting away from streaming services toward local libraries. More control, no licensing surprises, no feature removals.

Home automation scripting and voice assistants backed by local llama.cpp models. The infrastructure obsession extends to the house.