The Workshop
Behind the Book

The manifesto was the easy part, in a way — it's the argument I've been making in my head for two years. The Playbook is harder, because it has to be useful, not just true.

Useful means specific. It means naming the actual tools, in the actual order, with the actual failure points where people quit. It means admitting the parts that are slow and unglamorous instead of selling a fantasy. There's an entire industry built on telling people they can get rich with AI in a weekend, and every one of those promises makes the real path harder to see.

So the Playbook is the opposite of that. It's the path I actually walked — literacy, prompting, the stack, building a real thing, making it reliable, turning it into leverage — written for someone who has no degree, no network, and no runway, because that was me. If it required privilege I didn't have, I couldn't have done it, so the version I'm teaching doesn't require it either.

It's the thing I wish someone had handed me the night I first opened a code editor.

Early on, the journal and the book were the same thing — every entry was treated as a chapter, and the chapters were treated as entries. It was convenient and it was wrong.

A journal and a book are different objects. A book is finished, ordered, structured — you read it front to back and it makes an argument. A journal is alive, dated, out of order, and honest about the mess. Conflating them made the book look unfinished and made the journal look pretentious.

So I split them. The book is now its own structured product. The journal is this — the live record of building it. Two different things, doing two different jobs. The fact that it took me a while to see that is itself a journal entry.

Lesson that keeps repeating: the structure of a thing should match what the thing actually is. When something feels off, it's usually because two different ideas are sharing one container.

I keep getting asked why I didn't just write a manuscript and pitch a publisher.

Because the argument of the book is that the people who win in this era are the ones who build and own their own infrastructure instead of handing their value to a platform. It would be incoherent to make that argument and then hand the whole thing to a publisher who takes the rights, the list, and most of the money.

So the book lives on a server I control, at a URL I own, in code I wrote. The manifesto is free because the argument deserves to spread. The Playbook — the how — is the part I sell, because teaching the skill is real work and real work has a price. That split is the book practicing what it preaches.

This journal is the part of the process most books hide: the thinking out loud, the decisions, the things I got wrong and fixed. The book is the polished argument. The journal is the workshop.