Long-form thought on AI-assisted development, agent mode, DevOps philosophy, and what changes when the human is three abstraction levels above the code. Some essays lean technical, some lean philosophical; they share the systems-engineering frame.
88 posts • Page 3 of 5
The subscription is the small line. The real meter is the time you spend feeding context, checking output, catching the confident mistake, and cleaning up the work that looked finished. That hidden labor has a name now: botsitting.
If AWS is math and Kubernetes is physics, then discourse is the physics of other minds, the same live, empirical, pushes-back system, except the matter is a person and the latency is a blank stare. Why the studio and the arena are two different rooms, why the second one floods you, and how to build the faculty that levels the field.
AI is strong in one place and confidently wrong half a step over, and from the inside the two feel identical. The real skill is not prompting. It is knowing when to delegate, when to steer, when to verify, and when to think alone.
The invoice for AI is the cheap part: a seat and some tokens. The real bill arrives in four ledgers: financial, attention, coordination, and development. Why AI makes the individual feel fast while the organization barely moves.
My head does not run in a line, it runs in branches. A tool arrived that does the exact part I cannot do and amplifies the exact part I already do too much. On building with an agent when your attention has its own ideas.
AWS is taught as two hundred services. Underneath it is a handful of primitives, and every service is a frozen answer to a distributed-systems trade-off. The map I built studying for the SAA-C03, and the two questions that decode any new AWS service.
I could already make sound. I could not name it, and you cannot ask for a thing you cannot name. So I asked my music engine for a map. This is that map: sound built in altitudes, and the words that let you climb it.
Thirty-three repositories, and I cannot hold more than two in my head. How one instruction file per repo turns multi-repo agent work into routing, and why I keep refactoring those files.
A static site has no server to check a password, which is fine right up until the day you need one. My staging site is the problem in miniature. It is a full mirror of production, except it also carr...
Tesseract could not read a word of it. I have years of handwritten journals, the actual paper kind, and I wanted them on this site. The obvious first move is optical character recognition, and the ob...
Every post on this Astro site is precompiled into one committed TypeScript file at build time. Why I read the markdown once instead of on every page, and the sync cost that comes with it.
A shell script catches every em dash on this blog. The real AI tells live in register, which no regex can see: what I lint for, what I read aloud for, and why a blocklist deletes real voice.
A strict Content-Security-Policy on a static site allowlists inline scripts by hash. Change one script, forget to update the hash, and every page renders blank. The incident that taught me, and the deploy guard that ends it.
Agent mode and autonomous mode get used interchangeably and they are not the same thing. The difference is who closes the loop: you, after every task, or the system, running many steps before anyone looks.
Not a tools list. The tools keep changing; what changed underneath is where the hours go: specs in the morning, batch review in the afternoon, and the judgment work that never left.
The code got cheap. The review did not. Here is the review workflow I actually use when AI agents write most of the diff: three passes, an adversarial second agent, and the discipline of reading what ships.
A field report from inside sustained agent-mode work: the heat behind the eyes, the way speed bends your sense of time, what it costs the body, and the practice that lets you build at the frontier anyway.
A manual for building software with an AI agent: the setup, the loop, context management, and the Claude Code and Copilot commands I use every day. Written like the old Linux HOWTOs.
AI took the typing, and the cost of software engineering did not go away. It moved from the hands to the head and got heavier. The new scarce resource is your attention, and the new discipline is managing it.
DevOps was always a feedback loop. The one worth building now runs on the system itself, so every failure and every change makes the next one cheaper and safer.