Posts that treat software, work, and daily life as systems: feedback loops, structure, and what compounds over time.
54 posts · all topics
Arcturus is the Bear-Watcher, the guide-star of the northern sky, and its myths are both about wisdom arriving at the wrong moment. Decan 14 is wisdom and guidance: ten days spent building instruments for oversight, and a last three days that produced no oversight at all. The governor got built and then never consulted.
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.
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.
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.
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.
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.
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.
Regulus spins at 96.5 percent of the speed that would tear it apart, and has held that edge for 250 million years. Decan 11 is sovereignty and heart: governing at the highest intensity you can actually sustain, and finding out that the three and a half percent you hold back was never slack to spend on more empire.
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.
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.
I built a method, pointed it at my own thirty-four repositories, and watched the sprawl become a page I could read. Then I tried to prove its deeper claim and the first experiment came back null. Under the practice is a field: the science of complexence, the loop as a recursive equation, meaning velocity, and the cognitive form, an idea held apart from how you say it. A research program, published openly, nulls and all.
Canopus is the navigator's star, second brightest in the sky and powerful not because it is close but because it is a fixed reference far beyond you. Decan 10 is navigation and purpose: finding a heading when you have lost your bearings, building the structure that holds the course under load, and steering by a star that stays below your own horizon.
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.
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.
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.
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.
Sirius is the brightest star in our sky not because it burns hottest but because it is close. Decan 9 is power as clarity of signal, delivered near enough to be received, and the choice to let the real work be seen without scorching.
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.
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 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.
DevOps was always a feedback loop. The first one ran between people. The one worth building now runs the system back on itself, so every failure and every change makes the next one cheaper and safer. The recursion is the compounding.
When a system gets too big to hold, almost everyone reaches for the same move: make it simpler. It is the wrong move. You cannot simplify the ocean. You can only chart it. This is about the difference between simplicity and legibility, why decisions quietly migrate to whoever holds the context, and how to make a complex system visible enough to navigate without pretending it is small.
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.
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 versus Kubernetes is the wrong question. AWS is math and Kubernetes is physics: two ends of one spectrum, the galaxy and the atom. AWS gives you grand scale but you watch the cost; containers run nearly free but you watch the performance. Here is when to use each, when to use both, and why they become a symphony of systems together.
Antifragility is not resilience. Resilient things survive disorder; antifragile things gain from it. Here is how I apply Taleb's framework to fifteen years of engineering, the way I build films and books from code, and a ten-day journal cycle run as a stress rhythm.
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 is not a job title and never was. It is a thesis about how to build systems that can change without breaking. Fifteen years in, here is what actually compounded, what automation never solved, and what agent mode is now revealing about the practice.
Alhena shows the hidden cost of noise: transmission quality, concise messaging, and recovery architecture matter more than raw effort.
Capella makes the sequence explicit: protect first, then renew. Boundary discipline and simplification preserve long-term throughput.
Menkalinan distinguishes push from steer: cleaner instrument choice and operator posture under pressure outperform visible force.
The mercury-manganese peculiarity in Elnath's spectrum is a product of stable conditions, not heat. Decan 3 tested whether bold expansion could run without the calm foundation underneath. On Day 7 it couldn't. On Day 9 it had to anyway.
Hamal reignited after burning through its first fuel. The Spring Equinox opened Decan 1 with that same question: not how to start from nothing, but how to find new fire from what already exists.
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.
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 five-thousand-year-old foundation and extended with systems thinking.
On maximum effect through intelligent deployment not accumulation, discovering the missing arena at the worst possible moment, crossing a major life threshold, and what a star burning at 22,000 Kelvin from just 8.6 solar masses teaches about efficiency over force
Everything about how we teach languages is backwards. Study, memorize, practice, then maybe speak. I built a system that reverses the order: speak under pressure first, log what breaks, drill the friction, speak again. No app. No gamification. Just markdown files, agent prompts, and real people.
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.
On learning that manifestation requires grounding before release, discovering friction as improvement mechanism, detecting the first signal, and traveling 172 million kilometers while the blue supergiant teaches precision through crisis
Freewriting on AI and the maker's prejudice: creator, original, or regurgitation. Breath and the motion of ink, and a work that stays incomplete for most of its life before it comes out from hiding.
On learning that creative eruption happens not as single explosion but as multiple parallel convection cells, discovering four domains where power deploys, and traveling 172 million kilometers while the red supergiant teaches conscious direction of energy
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.
On living where constellations touch, learning discernment through constraint, and the 175 million kilometers traveled while building liberation through empathy as Alpheratz remained invisible
On aspiration through volatility, F-U money as creative sovereignty, and trusting vision when the star remains hidden behind clouds for nine of ten nights
On agent mode as thinking transformation, building what holds when you step away, and the 535 million kilometers traveled while testing whether foundations could endure
On learning to glow under pressure, showing up when it feels absurd, and the 535 million kilometers we traveled while transformation unfolded
Time is motion. During 10 days tracking consciousness by starlight, we traveled 535 million kilometers through space toward the Great Attractor. On oath-keeping across cosmic scales, burnout as sacred data, and what Sisyphus does when he learns to automate the boulder. A philosophical synthesis spanning Stoicism, Absurdism, and Logotherapy.