These People Are the Map
Reading Dubberly and Pangaro on how cybernetics connects computing, counterculture and design, one night, on my phone. Maturana, Pask, Nelson, Brand, Pickering and Rittel, and my head spinning.
Systems thinking
Posts that treat software, work, and daily life as systems: feedback loops, structure, and what compounds over time.
52 posts · all topics
The Cybernetics Family Tree
I wondered where cybernetics would sit on my O'Reilly shelf. It has no shelf of its own. It sits under all of them. A checked family tree, from the governors to Kubernetes, with your shelf on it.
The Hacker Ethic Meets Cybernetics
A fourteen-year-old's robot bug at the MIT AI lab pushed a wallet across a grimy floor while the grad students upstairs wrote theses on why it was hard. The hacker ethic, rewritten for cybernetics, humility and AI as a partner.
The Regulator Was Fed Intents
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.
Gentler On-Ramps to Cybernetics
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.
A Cybernetics Reading List, Written Before I Read It
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.
Culture Is the Oldest Information Technology
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.
A Loop Is a Path That Closes
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.
Decan 14: The Governor Was Built and Then Not Consulted
Ten days under Arcturus, the Bear-Watcher, building instruments for oversight, and a last three days that used none of them. The governor got built and then never consulted.
Decan 13: The Harvest Date Moved
Spica is the ear of grain in the Virgin's hand, and Hipparchus found the precession of the equinoxes by trusting a two-degree anomaly in his readings of it. Decan 13 is artistry and perfection: one crop, a rep a day, nothing else refined, and a harvest date that moved because the measurement said so instead of because the mood did.
Hello, Again
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.
Decan 12: Fix the Chassis, Not the Instance
Denebola marks the tail of the lion, and a tail moves before the body does. Decan 12 is reform and intuition: catching the map before it is gone, reading the anomaly instead of the object, and finding out that the fix almost always belongs at the chassis rather than on the instance in front of you.
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.
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.
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.
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.
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.
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.
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.
Decan 11: The Margin Was Never for More Empire
Regulus spins at 96.5 percent of the speed that would tear it apart. Ten days on governing at an intensity I can sustain, and why the margin I hold back was never for more empire.
The Information by James Gleick: The Book That Sent Me Looking for Meaning
James Gleick's The Information is the clearest history we have of how the world learned to measure the signal. It is also the book that showed me, by drawing the boundary so cleanly, the one thing the science of information set aside on purpose: meaning. This review is the origin story of the work I have been doing since I closed it.
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.
Decan 10: Steer by the Star You Can't See
Ten days under Canopus, the navigator's star, bright from far away. Starting in a fog after a fall, talking my way to a bearing, and steering by a star below my own horizon.
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.
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.
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.
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.
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.
Rhetoric Is the Physics of Other Minds
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.
Decan 9: The Brightest Star Is the Closest One
Ten days under Sirius, the brightest star in our sky because it is close, not because it burns hottest. The week I went public with the work and let it be seen, near and clear.
Decan 8: Loyalty Is Not the Same as Staying
Procyon, the herald that rises before the Dog Star, teaches that loyalty is not the same as staying. Fidelity to what is alive in you can require letting go of what is already dead.
Making Complexity Legible: a beat-locked spit-rap on charting complex systems
Making Complexity Legible is Case I of The Cartographer of Complexity, a new Napkin Films series about Making Complexity Visible. The idea: you cannot make a complex system simple without deleting what made it work, so you do not shrink the sea, you learn to read it. A tidal-EDM spit-rap, Plan 9 and OG Bobby trading bars over recomposed Telemann, with a cartographer bunny who roams a sea that brightens as it becomes legible. CC BY 4.0.
Recursive DevOps
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.
Making Complexity Visible: You Cannot Simplify the Ocean, Only Chart It
When a system is hard to see, decisions migrate to whoever holds the context. You cannot simplify the ocean, only chart it: why a live view of a system widens the circle of people who can think about it.
Run Your Life Like Software
Life Ops is running your life as a deliberate system, designed the way you design software: observe before acting, choose responses over reactions, build systems that make the good path the easy one, and version the whole thing like code.
How to Live Coherently Inside Complex Systems
Coherent complexity is what you get when a complex system is made legible without being made simple. You do not reduce it. You map it, until you can move through it on purpose. A field guide to the practice, and the idea behind everything else I build.
AWS Is Math, Kubernetes Is Physics: A Symphony of Systems
AWS is math and Kubernetes is physics, the galaxy and the atom. With managed services you watch the cost; with packed containers you watch the performance. When to reach for each, and for both.
Living with Antifragility: How I Build Systems and a Life That Gain from Disorder
Antifragility is not resilience: resilient things survive disorder, antifragile things gain from it. How I apply Taleb to the systems I build, to films and books made from code, and to a ten-day journal cycle.
Decan 7: Don't Confuse the Label with the Light
Pollux, the brighter twin that Bayer named second, teaches that the label rarely matches the light. Ten days of holding two truths at once, at work and at home.
DevOps Beyond Automation: What Actually Compounds
DevOps was never a job title. It is a thesis about building systems that change without breaking: what compounded once the tools became a commodity, what automation never solved, and what agents change.
Decan 6: Signal Discipline in a Noisy Week
Ten noisy days under Alhena. The move that held: write the wound down instead of leaking it sideways, keep it out of every message, and wait the whole day before believing the story.
Decan 5: Protection First, Then Renewal
Ten days under Capella, the paired giants of Auriga. After a real failure I wrote the protection rule before the next attempt: the shelter goes up first, then the renewal.
Decan 4: The Difference Between Push and Steer
Ten days under Menkalinan, the Charioteer's binary star. A grumpy morning that spilled into the house, a trading loss I caused myself, and learning to steer instead of push.
Transmissions and Coherence
Journaling cements time better than any tracker: a consciousness temperature reading. Build tools that create space and help people, keep the deep breath, let mountains reset the reference point.
Naming and Nesting: The Architecture of Decanal Time
The decanal system handles the ten-day cycle beautifully. But what connects thirty-six decans into a readable year? What connects years into a life? Seven nested layers of time, each with naming conventions and review cadences, built on a four-thousand-year-old foundation and extended with systems thinking.
Universe Recursing on Universe
Lingering snow under hazy February clouds. The human as the Universe's analytical machine, civilizations as falling leaves, and a purpose that may simply be to look up in awe.
Skis Cutting Through Powder
After a day at the computer, ink on the page as a more natural pathway: systems within systems, writing like a dance, and letters sliding across the page like skis cutting through powder.
Antifragile: Things That Gain from Disorder by Nassim Nicholas Taleb
Taleb's Antifragile rearranged how I think about risk: the fragile, robust and antifragile triad, the barbell, via negativa, and skin in the game. Arrogant, repetitive, and worth the argument.
The DevOps Handbook: Why Elite Teams Ship Fast Without Breaking
The DevOps Handbook is the clearest account I have read of why some teams ship small changes often without breaking things. A walk through the Three Ways, the technical practices, and what has dated.
Decan 24: Building Systems That Outlive You
Ten days under Markab, the corner star of the Great Square: a barbell money system designed in a day, a blog pipeline that runs without me, and an outage on day nine that tested both.
Decan 23: Blooming in the Desert
Ten days under Scheat, a dying red giant, when work, care, pain and a tested boundary all arrived at once. Reading Antifragile mid-shock, and showing up on the day it felt absurd.
535 Million Kilometers: When Sisyphus Learns to Automate the Boulder
Ten days under Fomalhaut that began with my body shutting down. If Sisyphus pushes the same boulder forever, why not build something that pushes it for him? So I built the systems.