A book you can read and run

I write books you can run, not just read. The code in them works. You can read every page online. And if you want to own a copy, you pay a little. Here is why I make them that way.

The two books

The first is AI Native Business. It is 14 chapters, about a two-hour read. It lays out how to build a business that is AI-native from the ground up, not a normal business with AI bolted on the side. You can read the whole thing online. If you want the PDF and the EPUB to keep, it is $20.

The second is the deep one, AI Research on NVIDIA DGX Spark. It runs to 53 chapters and around 145,000 words, with real benchmarks for speed, accuracy, and memory that you can reproduce yourself on the desk machine. It is $50.

Prose and code in lockstep

Here is what makes them different. The prose and the code move together. The book is not theory floating above the real work. Every claim has working code behind it, and that code runs.

The DGX Spark book, in particular, is the journey from stories eight through ten turned into a full, reproducible course. The numbers you read in those stories, 52 milliseconds to the first word, 231 question pairs, refusals dropping from 61% to zero, all of it is in the book with the code to reproduce it on your own machine. You do not have to trust me. You can run it.

Why open to read

People ask why I give the full text away. The answer goes back to the divide. The barrier is learning, not money. Putting the whole thing behind a paywall would work against the one thing the book is for.

So you read it online. You pay if you want to own an offline copy, support the work, or just say thanks. That is the model I admire in studios like 37signals. Sell the knowledge in a book, but keep the door wide open. It is all openly licensed, the same way my software is.

Why this is the deepest lever

A book is the first of the four levers, the playbook, taken all the way to the bottom. A short story like this one gives you the shape of an idea. A book you can run gives you the whole thing, step by step, with the code to prove it.

A playbook you cannot test is just an opinion. A playbook you can run is a tool. That is the bar I hold my books to.

The kit, the books, the models, these stories. I make all of it out in the open, on purpose. That is not an accident. It is the whole method, and it is the last story in this arc: Building in public.