i'm writing this from a browser tab. no IDE installed. no local dev environment. no laptop that matters. just a web terminal connected to a server in germany, and a claude subscription.
the server is a hetzner box. 64GB ram, ubuntu, sitting in a data center somewhere in europe. i'm sitting in mazunte, oaxaca, watching geckos climb the wall at 3am. between us there's a caddy reverse proxy, a tmux session, and claude code running directly on the machine.
let me say that again because it still trips me up. claude is on the server. not on my laptop. not in some cloud IDE. on the same box where the sites live, where the databases run, where the backups happen. it reads the files. it writes the code. it deploys. it commits and pushes. all from a conversation in a terminal.
the setup is almost embarrassingly simple. a $20/month claude subscription. claude code installed on the server. a tmux session to keep it alive. a web terminal to connect from anywhere. that's it. no API costs. no token counting. no infrastructure beyond what already exists.
i open a browser. i type. things get built.
last week i shipped a full analytics dashboard, a git server, a media library, and an arcade — all from my phone while my kid was napping. the week before that, a task board, a log viewer, a status page. 75+ sites running. 29 docker containers. all managed through conversation.
people ask me what my stack is. i tell them it's a conversation. they think i'm being abstract. i'm being literal.
the old workflow was: open IDE, read code, think, type, run, debug, deploy. the new workflow is: say what you want, watch it happen, course correct. same intellectual work. completely different interface. the keyboard went from the primary tool to a secondary one. my voice — what i want to exist — is the primary tool now.
this is not about AI replacing engineers. i'm the engineer. i know what to build, how things connect, what's going to break at 4am. claude doesn't have that. what claude has is perfect memory of every file on the server, zero ego about rewriting something for the fourth time, and the ability to hold context across an entire infrastructure while i think out loud.
it's a pair programming session where your partner has read every file and never gets tired.
the thing nobody talks about is how this changes the relationship with building itself. when the friction drops this low, you stop planning so much. you stop hoarding ideas in notion boards. you just... build the thing. see if it lives. if it doesn't, you built it in twenty minutes, so who cares.
shipping imperfect things as spiritual practice. i wrote that once. i meant it more than i knew.
there's something about sitting in the jungle, barefoot, talking to a machine in a data center 9,000 kilometers away, and watching a website appear — that makes you realize the old gatekeeping is over. you don't need the setup. you don't need the team. you don't need the runway. you need clarity about what wants to exist, and a terminal.
the server is the studio. the terminal is the instrument. the subscription is the rent. everything else is just typing.