Essays

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 2 of 5

A dim desk at night with a face-down phone and a closed notebook, the cold glow of a market chart reflected in the window
• 4 min

Knowing Isn't a System

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.

A tall cross-section of a dark tower lit floor by floor, a single glowing line between two nodes at the foundation and one ring of light at the roof
• 12 min

The Loop Was the Top of a Stack

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.

A dark archive of labeled card drawers, each lock holding a single brass key, one drawer crowded with a dozen keys
• 5 min

One Writer Per Artifact

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.

A dark control room with a wall of small green status lights on one side and a constellation of linked nodes with a single red path on the other
• 8 min

The View You're Missing Is the Graph

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.

A hand-drawn map on a desk under a warm lamp, overlapped by an older printed chart of the same coastline, their lines aligning
• 6 min

You Reinvented Data Engineering

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.

Seven distinct gears arranged in one lit row on a dark workbench, lifted from a shadowed heap of identical-looking gears
• 7 min

A Loop Is Seven Things

Thirty-two automated jobs run underneath my days, I wrote every one of them, and I could not hold the system in my head. The problem was never my memory. It was a word. "Loop" was one word doing the work of seven.

An old map of the Mediterranean under lamplight, with two inked routes leaving Iberia, one east toward Salonica and one west into the Atlantic, Marseille marked between them
• 7 min

Finding Edgar Morin

Edgar Morin died in May at 104, and I met him through his obituary. He spent eighty years on the question I have been building around: how to think inside the weave without cutting it apart. Two book reviews are coming. This is the marker I am leaving at the trailhead first.

• 7 min

Engineering Orientation

Making complexity visible is the method. Orientation is the objective function. The research program now has an installable runtime, laboratories that keep their data, and its first pre-registered experiment, running on my own life.

A terminal window showing hello.sh: a gold HELLO banner in block-letter ASCII art, then a greeting, hello, joshua, the day's decan, the systems' status, and a numbered menu of the loop's next moves.
• 5 min

Hello

The first program you write used to be the machine greeting the world. Hello, world. I built a different first program: my own system greeting me. One warm door instead of four scattered starters, and the greeting sits inside the loop it opens, so it can reach in and improve itself.

The Little Black Book of Hansuru cover, a black book spine with the title in gold and the character hansuru set beneath it.
• 5 min

The Little Black Book of Hansuru

A book I wrote about selling options for income, built on one law: survive first. It shows a record most books would hide, and that is the reason it exists. Out now in Kindle and paperback.

A calm figure standing on a luminous lattice of fine structure that descends into the dark below, the formal floor beneath orientation inside complexity.
• 13 min

The Science of Complexence

I pointed a method at my own sprawl of repositories and got a page I could read. Then the first experiment on its deeper claim came back null. This is the research program underneath, nulls included.

A single voice line entering a small router that fans out to a few specialist roles, each producing a clean document, with one short daily brief returning to a calm figure.
• 12 min

Complexence OS

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.

A single worn brass coin suspended in a shaft of warm light against deep black, its two faces caught between turns.
Cornerstone • 10 min

Germane Friction

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.

A long staircase of stone steps rising out of dark fog toward a warm opening above, a single lantern resting at the threshold.
• 8 min

The Case For AI, Made Properly

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.

A lone figure at a desk in cold screen light, their shadow on the wall thinning and dissolving into darkness, a single warm lamp holding back the corner.
• 8 min

The Case Against Letting AI Think For You

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.

An overhead view of dozens of small folders scattered across a dark surface, most dim and one cluster lit warm, as a hand sorts them into three labeled lanes.
• 6 min

Why Thirty-Three Repositories Needed a Census

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.

Six translucent map layers stacked and slightly offset above a dark table, each carrying a different mark, lit from one warm side so the stack reads as a single deepening chart.
Cornerstone • 9 min

How to Map a Domain: The Six Layers

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.

A weathered hand-drawn map of a vast interconnected terrain, lit by a single warm lantern, with coastlines and routes emerging out of dark uncharted space.
Cornerstone • 9 min

Domain Cartography

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.

A single steady point of warm light at the center of a vast dark web of fine interconnected filaments, oriented and calm inside complexity.
• 9 min

Complexence

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.

Two paths diverging in the dark: a worn uphill trail in warm light and a smooth shortcut fading into shadow.
• 7 min

Compressed or Destroyed

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.