After about a week of reading my own AI digest every morning, two things were obviously wrong with it. There was no Microsoft. There was no “AI-native work” angle — Mollick, GitHub Copilot announcements, the whole practitioner discourse — just absent. The first few days I assumed I was misremembering. Then I counted, across four days × roughly fourteen developments per day, the number tagged vendor:microsoft: zero. The number that talked about how AI changes how teams work: also zero.
Adding a Data Disk Without Touching Docker
The root disk on my Azure VM was at 84% (24G of 30G), and I’d been quietly ignoring it for a couple of weeks. Time to fix it. The interesting parts weren’t the partitioning — they were figuring out who was actually eating the space, picking a layout that didn’t require reconfiguring any daemons, and then discovering a check on the status dashboard that had been “working” by coincidence.
Letting Claude Code Run Unattended
The thing nobody warns you about with Claude Code is the babysitting. You hand it a 40-step refactor, walk away to make coffee, come back to a prompt asking permission to run npm test — for the third time. By the time the task is done, half the wall-clock time was the agent waiting for me, not the other way around.
There are four ways to fix this, and the right one depends on how much trust you want to give and how isolated your environment is.
How I Deployed This Site
This is the very first real post on the site, and it felt only fitting to write about how the site itself was put together. Nothing here is novel — it is the boring, classic recipe — but writing it down forces me to be honest about every choice I made.
What's Running on This Server
A map of every public-facing system on ai-native.japaneast.cloudapp.azure.com, why each one exists, and how they’re wired together. Updated 2026-05-07 after HTTPS, an AI-feed portal, a service catalog at /, and a couple of small relocations.