From the build log
We build in public. Each note is a short, honest look at what we shipped, what broke, and what we learned.
Building in public
Every story here, every number and honest miss, I put out in public on purpose. This is why I build in the open, and how you can help shape what comes next.
A book you can read and run
I write books you can run, not just read. The code works and every page is online. Here is why open, reproducible books beat theory behind a paywall.
The glue tax, and the kit that pays it
Every AI project, I kept rewriting the same boring plumbing. I named it the glue tax. So I built fieldkit, an open kit of 12 tested parts, to stop paying it.
Four things you actually control
The AI divide feels out of your hands. It is not. There are four things you can own instead of rent. Playbooks, software, models, and a device of your own.
Why most teams get nothing from AI
Companies poured 30 to 40 billion dollars into AI and 95% got nothing back. The reason is not cost or tech. It is learning. That gap is why Orionfold exists.
Why I folded Orionfold
After nearly nine years at Amazon, I left to start Orionfold. This is the twenty-five-year story behind that choice, and what the name means.
The cockpit for my models
I had a shelf of models on one desktop and no way to drive them. In fifteen hours I built a cockpit to run, compare, and score them, all on that desk.
Teaching a small model my field
I taught a 3B model my own field with 231 question-answer pairs. It stopped refusing and started answering, in my voice. Small and tuned beat big and general.
My first model on a desktop
I ran my first model on a small computer on my desk. 52 milliseconds to the first word, no cloud, no per-use bill. It felt like a local function, not a service.
Access first, models second
On day one with my desktop AI machine I did not pick a model. I set up how I reach it. Models change every six months. Good access lasts for years.
A spec at breakfast, an app by lunch
With Kiro I turned three sentences into a 24,000-line app, about four hours of my time. The spec did the heavy lifting, and speed became a skill.
One agent, three faces
The same AI agent should meet a developer in the terminal, a manager in a dashboard, and a phone user by voice. One brain, many doors.
Keeping my data in the room
I built an analyst AI that never sends my work to the cloud. Privacy is not a setting you flip at the end. It is a choice you make in the design.
Vibe coding is not passive
After my AI-built weekend I thought coding got easy. Andrew Ng named what I felt. Vibe coding is not passive, it is engineering done fast.
I built a real product in a weekend
Over one holiday weekend I built Web Memo, a working browser tool, about 2,400 lines of code. AI wrote most of it. My sense of my own ceiling moved.
Frontier reasoning at a tenth of the cost
In early 2025 a model called DeepSeek did frontier-level reasoning for about 95% less. And it was small enough to run on my own machine.
The year the gap closed
In late 2024 I watched the AI tool stack collapse into the model itself. The first sign that one person could build what used to take a team.
Get each new story in your inbox.
Short, honest notes from building Orionfold in public. What we shipped, what broke, and what we learned. No spam.