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.
87 posts • Page 1 of 5
I built the smallest loop that could be wrong, to watch a law from Ashby do work. The loop was wrong twice before it was evidence, the law turned out not to apply, and the real cluster already knew the fix. All of it measured, and explained from the ground up.
Most of my essays had gone missing from the page that lists them, on production, and every check passed. The same week turned up five more checks on this site that could not fail. What they had in common.
I let an AI run a music and film studio for a month: render, master, verify, repeat. It mostly worked. Everything that went wrong went wrong the same way: a number that was not measuring what I thought it measured.
The founding papers were too steep and so were my own primers. So here are the gentler ways in: stories and a game to test the water, an hour of free reading, then a shelf of books.
I opened the first paper on my cybernetics reading list and bounced. I had no map of the domain, so I stopped and built one: a primer for every work, in print and audio.
An agent can check a quote for me. It cannot read for me. So before I open Ashby, Wiener and the 1943 paper, here is the list, and what I expect to find, written down first.
I once wrote that our minds run on the same hardware as every other animal and that something rewrote the software. I think the software is culture, the oldest information technology we have.
Change the drag constant in my arcade game by one part in a hundred million and twelve recorded runs stop matching. That strictness is the foundation the replays, the scoreboard, the co-op and the releases all stand on.
A vision model read the top of my notebook page and filed it under a date eight years off, calmly. One reader cannot flag what it is sure of. So now two models read every page, and I look only where they disagree.
One of my health checks stayed red for eleven weeks by reading its own failure. A loop is the special case of a trajectory, the path that happens to close, and a life does not.
I read a hundred-page atlas of a kingdom I will only ever rent, then logged in and walked it. On studying a territory with a map in one hand, why the first thing the kingdom teaches is to take off the crown, and how it ended at 799.
My AWS exam deck scored 26 percent. I printed the whole study system as a paper packet, studied it one day, and the same review scored 47. Six weeks later the exam came back 799. Why a page is a place.
Development environments lie in two directions. Clone production and it is too expensive to use. Mock it and it is confidently wrong. Here is a third option, and a working hybrid lab that joins a Kubernetes cluster on my laptop to a real Windows host behind a real AWS load balancer for about nine cents an hour.
Three weeks ago I wrote about a script called hello, the one warm door into my system. I kept pulling the thread and the door turned out to be the outermost loop, the one that asks whether the whole thing can still become useful. This is what I found standing behind a greeting: cybernetics, nested watchers, and the rule that intelligence never gets its own hands.
I failed another practice exam today. Same score as my best one, and my best is still a fail. But I finished in half the time and it felt easy in a way it never has, and I think the number is the last thing that moves, not the first.
I bought the IPO everyone wanted, and a quiet part of me narrated the mistake while I made it. The post-mortem found the real bug: a category I had built so I could skip my own system. Knowing isn't a system.
I typed my thirty-two loops, then drew them as a graph, and thought the loop was the top of the system. It turned out to be the roof of a stack eight floors deep, and the floor holding all the weight is the smallest one: the edge.
Typing my automation handed me most of its rules for free; the type carries the contract. One rule came free with nothing, and it was the one my system was breaking: every file gets exactly one job that writes it. On the difference between rules you remember and rules the structure carries.
I gave every job in my automation a receipt, a health check, and a green light, and the system still would not fit in my head. A dashboard shows the state of the parts. The question I actually had was about the shape of the whole, and no amount of state answers a question about shape.
The best thing anyone told me about my own system this year was that I had not invented it. The scripts I grew by hand are a data pipeline, the shape is a DAG, and the discipline is solved. What the tools actually sell, why I am not buying yet, and the difference between wanting an engine and wanting a map.