The Engineering & AI Systems territory. 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.
61 posts • Page 1 of 4
Complexence is the capability of staying oriented inside complexity. Complexence OS is the rough machine I built today to run it: you talk into a file, one Chief of Staff agent sorts what you said and hands the rest to a few specialist roles, and you review only the exceptions. Day one of going from AI assisted to agent director. The method is open source; your data stays yours.
The fight over whether AI is good or bad is the wrong fight. AI is a friction-removal engine, and there are two kinds of friction: the kind that is building you, and the kind that is only taxing you. Telling them apart, in the moment, is the whole skill.
Most defenses of AI are about productivity, and they are weak. The strong case is older and bigger: this is the next rung on a seventy-year ladder of removing effort that was never building anyone. Here it is, made at full strength.
AI does not destroy your work in front of you. It moves the cost somewhere you cannot see: to later, to the invisible, to the version of you that stops getting built. The strongest case against leaning on it, made in full.
I had thirty-three git repositories and treated all thirty-three as if they were on fire. The fix was not more discipline or a better tool. It was a census: an inventory, an edge, and a rule for what counts as alive. Domain cartography applied to my own sprawl.
The hardest part of mapping a complex domain is the blank page. Here are the six layers I run every domain through, from primitives to levels, with the question each one answers, how to actually do it, and the failure mode that shows up when you skip it.
Domain cartography is the practice of charting a complex domain you have to live and act inside, until it is legible enough to navigate. Not making it simple. Making it readable. Here is the field, the method, and the six layers every map needs.
Complexity is the condition of the world. Complexence is the quality you bring to it: the capability of standing inside a system larger than yourself, seeing it whole, and still choosing. A word for the thing all my work has been about.
The same tool that can fold a beginner's learning curve shorter can also erase it. AI compresses apprenticeship when it transfers expertise and destroys it when it lets people skip the repetitions that were quietly teaching them.
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.
There are thirty-three repositories in my workspace, and I cannot hold more than two of them in my head at once. They sit side by side in one folder, but it is not a monorepo. Each is its own indepen...
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...
There is a 4.8 megabyte TypeScript file in my repository that I did not write. A script writes it, on every build, and I commit the result into git like it was mine. Most build advice would tell me th...