This is the second of four releases of this book’s content.
I’ve been using AI long enough now to want to look back. Not at the tools themselves, which change fast enough that any accounting is obsolete before it’s finished. At what I’ve learned. The practices I’ve developed through friction, repetition, and more than a few sessions that went sideways in instructive ways. What it actually means, after three years of serious use, to develop AI fluency.
That’s what this book is: nine breakthroughs, three interludes, one attempt to peel back the layers of my own AI literacy and see what’s underneath.
I use AI daily: designing professional development, revising documents, doing research, thinking through problems I can’t quite see my way around yet. For a long time I assumed I was getting better at it because I was doing more with it. What I’ve come to understand is that doing more doesn’t automatically produce understanding. The breakthroughs did. The moments when something failed in a specific enough way that I could see, suddenly, both what the machine was doing and what I should have been doing differently.
Each of the nine chapters follows the same structure: a breakthrough, a real mind-opening moment from a real AI session, and then two things that moment revealed simultaneously. How the machine works. How to work with it. I’ve come to think of these as two strands of the same structure, inseparable, each one making the other legible. You can’t develop good practice without understanding the architecture beneath it, and the architecture isn’t meaningful without the lived experience that gives it stakes and context.
The book moves in three parts. The first is about managing a conversation: learning to interrupt, recognizing when a session has run its course, doing the setup work that determines whether a conversation succeeds before it begins. The second is about reading AI output critically: catching flattery, making corrections that actually land, recognizing when confident-sounding data has been invented wholesale. The third is about what persists. Three years of working with a system that remembers nothing has helped me understand my own thinking better than I could have anticipated.
Before I get to chapters 3 and 4, a shout out to two fellow AI-ed substackers doing work that complements this book nicely. Andrew Maynard’s 14 essential AI skills every undergraduate should be able to demonstrate gives students concrete “I can...” statements they can defend in an interview on the spot. Sam Illingworth and Frank Andrade’s The Evidence-Based Guide to AI: When to Use It, When to Stop, and How to Tell the Difference asks the question underneath every chapter of this book: not just how to work with AI well, but whether to work with it at all. Both are free. Both are worth your time.
If you’ve been using AI long enough to sense that something is missing from the guidance available to you, that the technical explainers describe the system without telling you what to do about it and the prompt guides tell you what to do without explaining why it works, this is my attempt to close that gap.
It starts with the simplest thing I learned, and the one that changed everything that followed: you have to interrupt.
Nick Potkalitsky, Ph.D.
Chapter 3: The Onboarding
The Breakthrough
I was revising a chapter of this book. The session I’m thinking of was for an early draft of what would become the entropy chapter, and I had assembled a set of materials: a rough draft full of false starts, a cleaner version from a previous session, notes from conversations where the ideas had first emerged. I wanted the model to help me revise toward something sharper without losing what was already working.
I had tried versions of this before. Open a conversation, paste in the draft, ask for revision. What came back was competent and wrong in a specific way: it was revision toward the generic. The model would sand down rough edges that were doing intentional work. It would soften claims I wanted left sharp. The output looked like an improved draft but read like a document that had been pulled toward the mean of what “good writing” looks like in the training data. More careful. More hedged. Less mine.
This time I tried something different. Before I pasted anything, I typed a single instruction:




