This book started at 2 AM on a Friday.
With 600 lines of Python. Not one line was actual logic.
It was 2 AM on a Friday. I was staring at a Python file that had ballooned to 600 lines — and not a single line was actual logic. It was all prompts. Prompt templates. Prompt formatting. Prompt retries. Prompt prayers.
I was building an AI classifier for a lead nurture system. The kind that, if it works, makes your sales team love you, and if it doesn't, makes them send passive-aggressive Slack messages at 7 AM.
The worst part wasn't the fragility. It was the debugging. When the system broke — and it broke constantly — I had no idea where to start. Was it the prompt? The parsing? The model? The temperature? Every change was a guess. Every fix broke something else. I was playing whack-a-mole with probabilities, and the moles were winning.
June 7th, 2024.
My friend Mohsin sent me one link. “Bro, look into DSPy.”
I clicked it at 10 PM. By midnight, I had replaced 600 lines with 40.
That night, for the first time in months, I didn't get paged.
That was almost two years ago. Since then, I've built AI classifiers, lead nurture engines, ranking algorithms, chatbots, and LLM-powered vision apps — all with DSPy, all in production. This book is everything I wish existed when I started.
Not a tutorial. Not a reference. A complete mental model.
The DSPy docs are excellent — if you already know what you're trying to do. They'll tell you what MIPROv2 does. They won't tell you when to reach for it, why it beats the alternatives, or what it looks like when it fails.
This book fills that gap. Every chapter builds something real — not a HotPotQA demo, not a “summarize this article” example. Real projects with real constraints: cost budgets, latency requirements, edge cases, and production deployments.
Every code sample runs. Every optimization shows measurable before/after numbers. Every “Gotcha” callout came from a real GitHub issue or production war story.
Harmless
Guide
Docs &
Reference
Seven chapters. Zero filler.
Each chapter builds one complete, production-ready project.
| Chapter | Title | What You Build | Core Skills |
|---|---|---|---|
| 1FREE | Don't Panic | Startup Idea Roaster | Signatures, Modules, first optimizer |
| 2 | The Restaurant at the End of the Pipeline | Lead Intelligence Engine | Composition, Pydantic types, BootstrapFewShot |
| 3 | Life, the Universe, and Retrieval | Codebase Q&A System | RAG, ChromaDB, retrieval evaluation |
| 4 | The Babel Fish — Optimizers Demystified | Ticket Classifier | MIPROv2, SIMBA, the full optimizer zoo |
| 5 | So Long, and Thanks for All the Prompts | Fact-Checker & Code Reviewer | ReAct, tools, multi-agent |
| 6 | Mostly Harmless (in Production) | Content Moderation Pipeline | FastAPI, caching, streaming, observability |
| 7 | The Answer Is 42 (Tokens) | Multimodal Product Analyzer | dspy.Image, model cascading, GEPA |
Don't Panic
Build: Startup Idea Roaster
Learn: Signatures, Modules, first optimizer
The Restaurant at the End of the Pipeline
Build: Lead Intelligence Engine
Learn: Composition, Pydantic types, BootstrapFewShot
Life, the Universe, and Retrieval
Build: Codebase Q&A System
Learn: RAG, ChromaDB, retrieval evaluation
The Babel Fish — Optimizers Demystified
Build: Ticket Classifier
Learn: MIPROv2, SIMBA, the full optimizer zoo
So Long, and Thanks for All the Prompts
Build: Fact-Checker & Code Reviewer
Learn: ReAct, tools, multi-agent
Mostly Harmless (in Production)
Build: Content Moderation Pipeline
Learn: FastAPI, caching, streaming, observability
The Answer Is 42 (Tokens)
Build: Multimodal Product Analyzer
Learn: dspy.Image, model cascading, GEPA
One purchase. Everything that follows.
The Book
All 7 chapters, readable now. 6,000+ lines of real, runnable code across every project.
Lifetime Updates
DSPy moves fast — the API changed significantly from 2.x to 3.x. When the framework updates, so does this book. Free, forever.
Future Videos
Chapter walkthroughs and deep-dives are coming. Buyers get access. DSPy is easier to learn when you can watch someone debug it.
Community
Early access readers get a direct line. Questions, war stories, and production patterns — from people actually using DSPy.
This book owes a lot to a lot of people.
Omar Khattab & the DSPy team at Stanford
You didn't just build a framework — you changed how we think about working with language models. The shift from 'prompting' to 'programming' is going to age very well. It's a privilege to help more developers discover it.
Mohsin Tariq
Who on a random June evening in 2024 listened to me complain about LangGraph for twenty minutes and then sent one link. Every engineer has that one friend who somehow always knows about the thing you need before you know you need it. Mohsin is that friend. This book exists because of a single message he sent.
The DSPy Community & Discord
Your questions, bug reports, and creative solutions are woven into every chapter. The 'Gotcha' callouts came from watching real developers hit real walls. Special thanks to the contributors who patiently answer questions, file detailed issues, and push the framework forward every day.
Douglas Adams
Who isn't around to read this but whose fingerprints are on every chapter title and whose philosophy — that the universe is bewildering but navigable if you keep your sense of humor — is the closest thing this book has to a mission statement.
Ali Raza
Software engineer. AI practitioner. Shipping DSPy in production since 2024.
Ali doesn't come from the “write a paper about it” world. He comes from the “ship it on Friday and make sure it doesn't page you on Saturday” world.
Over the past two years, he's designed and deployed AI classification pipelines processing thousands of data points daily, lead nurture systems powering real sales workflows, and LLM-powered vision applications analyzing images at scale — all with DSPy, all handling real traffic from real users.
His approach to DSPy is shaped by the constraints of real products: cost budgets, latency requirements, user expectations, and the cold reality that your fancy AI system needs to work when the demo gods are watching.
“He firmly believes the best technical writing is the kind that makes you laugh while you learn.”