Out of retirement. Building again.
I spent four decades being the one they called when the system absolutely had to work. I shipped under other companies' names the whole way. Round two, I'm doing what I never did before: putting my name on it, and building the whole thing myself.
Pure C. No frameworks. Roll your own.
I'm rebuilding all of it — down to the metal. No runtime I didn't write. No vendor lock. No dependency I can't see to the bottom of. If a primitive isn't already in the tree, I write it. I learned the machine at the hardware level decades ago; now I build from there, in C, the way it should have been done the first time.
- Build the chip. Build the stack.
- Own every layer. Trust nothing you didn't make.
- Build the tools too — the software that builds the software.
"What are you building, brother man?"
Weeks of little sleep, surrounded by seven laptops all building at once while I kept every one of them moving, my best friend since the 8th grade asked me that. I looked into the camera and said one word:
And I meant it. People ask what you could possibly do with all of it, rebuilt from the metal up. Same answer: everything. It has a name — The Pantheon.
SealedI don't sell. I don't claim. I deliver.
I only show a thing when it's shipped, done, and usable by real customers. If it isn't running where people can use it, it doesn't exist — nothing to discuss. That's why The Pantheon is sealed: not a tease, a standard. I don't put my name on anything before it's real.