The manuscript is gone now — seventy-five thousand words traveling somewhere between my inbox and Sarah’s, between Edison and New York, between who I was when I started this and whoever I am today. I kept asking myself, while I was deep in the middle of it, whether there was a right way to do this: to hold a recipe in one hand and a memory in the other and press them together into something a stranger could follow. What I found, slowly and then all at once, is that writing a cookbook is less about precision than it is about translation — and I want to share everything I wish someone had told me before I began.
How to Write a Cookbook
Prep Time: Months | Cook Time: Years | Total Time: A lifetime of meals | Servings: Everyone who loves someone who cooks
Ingredients
- 1 story worth telling — the real one, not the tidy one
- Dozens of recipe tests, repeated until “close” becomes “as correct as I could make it”
- 1 trusted editor who will read it in one sitting
- Notebooks, voice memos, or whatever catches the moment your source cooks without measuring
- Patience for the gap between the memory and the page
- 1 person whose cooking you love enough to preserve
- Willingness to let the book be many things at once — cookbook, love letter, preservation, prayer
Instructions
- Start with a person, not a dish. Before you outline chapters or plan headings, identify whose cooking you are documenting and why it matters. The recipe is never just the recipe — it is the person who makes it, the kitchen they make it in, and the silence or the noise that surrounds the stove.
- Cook alongside your source, repeatedly. Watch their hands. Notice what they do not measure. Ask questions you think are obvious. Write down not just what they add but when, and in what mood, and what they say while they stir. The generous pinch is a unit of measurement only if you record it.
- Test until “close” is honest. Your version of your source’s recipe will not be identical to theirs. Accept this early. Your goal is a reliable, reproducible approximation that carries the spirit of the original — test it enough times that you can say “close” without apology.
- Write the headnotes first, not last. The short narrative that precedes each recipe is where the cookbook becomes something more than a list of steps. Draft it while the memory is warm. You can refine the instructions later; the feeling fades.
- Let the structure hold what the prose cannot. Chapters, sections, and sequences are not bureaucracy — they are the architecture that lets a reader find their way back to a dish they loved. Organize around meaning: occasions, seasons, the arc of a day, or the map of a relationship.
- Sit with the almost-smile. Not everyone whose cooking you document will tell you they are proud. Learn to read the nod, the hmph, the silence that is actually love. These are your confirmation that you have gotten it close enough.
- Send it. The manuscript will never feel finished. Send it anyway. The book being done and the book being perfect are not the same thing, and only one of them is possible.
Nutrition (per serving)
Calories: Immeasurable | Protein: High — this work sustains you | Fat: Some grief, rendered down | Carbs: Years of accumulated meals | Fiber: Everything that keeps the story moving | Sodium: A few tears, probably