Five reasons
Why it came from me and not from the best-resourced builders in the world.
An injury, a toll, a wire, a report, and a sergeant in a supply room.
1 of 5 · Not a coder
I built it as an operator who could not do it the coder's way.
1 min
I did not build this as a coder. I built it as an operator who could not do it the coder's way. In 1995 I had a parachuting accident that gave me a traumatic brain injury and damaged my spine, and I have been advocating for my own medical situation for the thirty years since. I am also documented neurodivergent, inattentive-type ADHD, and the injury amplifies everything I was already working with. A brain like mine cannot hold an entire context in its head and re-explain the same background to a system over and over before the system will help.
So I built the opposite: a context authored once, kept by the person it describes, composed into the work at run time, so the tool arrives already knowing who it is serving. I built it to second-brain myself.
A mechanism built to accommodate one specific profile turned out to generalize cleanly, because the problem underneath it, a person whose capacity varies being asked to perform as if it were fixed, is shared across a very wide range of disabilities, and across most people on their hardest days. These strategies work even on your hardest days, and the proof is that I build them around mine.
2 of 5 · The toll
A thousand dollars a month to a man who held the fiddly bits.
1 min
There is a less flattering reason too. Before I understood that the machine could take the wheel, I was paying a man a thousand dollars a month to handle outreach, and the work was not getting done. I do not have to name him either, because everybody knows somebody like him: the person who does not care about your mission anywhere near as much as you do, and who you have to go through anyway, because he knows the fiddly bits and you do not. Every small organization has one of those somewhere in the chain, a consultant, a web guy, a grant writer, a cousin who set up the database once, and the mission waits on them.
I want to be careful about what I say next, because it is true through one lens and not through another. The machine does not replace the people who care. It replaces having to go through the people who do not. The fiddly bits were never the valuable part of what that man did. They were the toll he could charge because he held them and I did not, and the moment a machine could hold them for me, in plain words, on a box I controlled, the toll was gone. What was left was my mission and my judgment about it, which is what should have been in charge all along.
3 of 5 · Signal
Meaning is modulation riding on something dumber than itself.
1 min
The second thing is that the security posture here is not academic. I was a 31 Sierra in the Army, a Satellite Operations Technician, and once you have watched data ride a carrier, once you understand in your hands that the wire does not care what it is hauling and that meaning is just modulation riding on something dumber than itself, the shared board and the note-passing and the membrane between systems all fall into place as the same old thing in a new war. All of it is signal carrying data.
I also spent time responsible for an arms room, and was recognized for how I secured it, and I have spent years on the defending side, protecting property and organizations that people set out to harm. This system hands a stranger only the exact records assigned, for the assigned reason, and can eject them instantly, because it was built by someone who has met the people it is defending against. It assumes bad actors by default, because assuming otherwise has a cost I have personally paid.
4 of 5 · What the field found
Stanford said it this year: the job became judgment and oversight.
1 min
Here is something that was only recently said out loud by the people who study this full-time. Stanford's 2026 AI Index Report found that employment for software developers aged twenty-two to twenty-five fell by roughly a fifth while mid-career and senior engineers held steady or grew, and by other counts entry-level developer postings have fallen by about two-thirds since 2022. The report describes the senior work that remains as judgment, system architecture, and the framing of ambiguous problems, and it describes the skills employers now want as problem-solving, oversight, and the ability to work alongside automated systems.
That is the exact split I built this whole thing on without having the words for it. The machine does the fiddly parts. The human does the judgment and the oversight. This method is oversight made structural, built into the wiring where it cannot be talked away. If you are a developer reading this, the news is not that you are finished. It is that the job just became architecture and oversight, which is precisely what standing one of these up for a community is, and which is a shingle you can hang yourself, whether or not the corporate pipeline wants you.
5 of 5 · Judgment travels
The pipeline is collapsing, and the method has an answer.
1 min
There is a second half to that report that nobody seems to have an answer for, which is that the pipeline that used to turn junior engineers into senior ones is collapsing, because the junior work the machines now do was also the apprenticeship. The method has an answer to that too, and it is the kind of thing that is obvious once someone points it out. Judgment is transferable now. Not all of it, and not instantly, but a great deal of what a senior person knows can be written down once as a skill file, an orientation guide to how they actually think and decide, and composed into a junior person's work the way a SOUL is composed into a lesson.
I know this works because it is how I learned. A senior non-commissioned officer in the supply room I was reassigned to taught me how to hustle procurement, how to actually get the thing the unit needed out of a system designed to say no, and that knowledge did not come from a manual. It came from standing next to him. The method lets that kind of knowledge travel without the standing next to. The practitioner's forty years handed forward is the same mechanism.
It is also, I think, the only honest plan anyone has offered for the pipeline the machines are eating. The field is arriving where the gaps already were, and I want to be careful about how I say this: not because I am smarter than anyone, but because I was standing in the gap, I had lost a store to a locked door, and I could not do it any other way.
These strategies work even on your hardest days, and the proof is that I build them around mine.