My grandmother’s kitchen notebook is a school exercise book with a marbled cover—the kind you buy at any papeterie for two euros. The pages have gone soft with steam. Flour fingerprints pressed into the margins. A stain near the middle covers part of a recipe for lapin à la moutarde. Something spilled. Probably stock, probably during that particular rush when you are feeding six people and the phone rings. She never rewrote the page. The stain is part of the recipe now.
I have thought about that notebook more in the last few years than I ever did when she was alive to ask about it. The question I keep returning to is not what she wrote but how she wrote it. Why her version of a recipe—with all its abbreviations and crossed-out quantities and marginal notes in that slanted hand—is more useful to me than any printed recipe I have found for the same dish. The answer, I think, is that her recipe was written for a specific person in a specific kitchen. It assumed things. It corrected things. It remembered what went wrong the last time and warned you in two words. A printed recipe cannot do this because it does not know you.
So this is an argument for writing down your own recipes. Not copying from books. Not bookmarking on a screen. Writing them—in your own words, with your own adjustments and failures noted, on something you will keep. The French have a tradition for this: the cahier de cuisine, the kitchen notebook. It is older and more practical than the cookbook industry would like you to believe.
The Cahier de Cuisine: What a Kitchen Notebook Actually Is
The cahier de cuisine is not a journal. Not a place for reflections on the meaning of food. It is a working document. A record of what you cooked, how you did it, what you changed, and what you will do differently next time. In French households of my grandmother’s generation, it was often the only cookbook. Recipes came from your mother, your neighbor, the woman at the market who sold you the leeks—and you wrote them down in your own hand so you would remember them the way you remembered them. Not the way someone else decided you should.
The form is simple. A dish name at the top. Ingredients, usually without exact quantities, because the quantities depend on what you have and who is coming. A method, written in shorthand, full of phrases like « jusqu’à ce que ça sente bon »—until it smells right. And then, crucially, the annotations. The things you add after the fact, in the margins or between the lines, when the dish has taught you something the original note did not know.
My grandmother’s notebook has a recipe for soupe au pistou that reads, in its first version: « haricots verts, haricots blancs, courgettes, tomates, basilic, ail, huile d’olive. Faire comme d’habitude. » Do it as usual. Then, below, in smaller writing: « Trop de basilic l’année dernière. Mettre la moitié. » Too much basil last year. Use half. And below that, from a different summer: « Ajouter le pistou à la fin, pas pendant la cuisson. Éric n’aime pas l’ail cru, mettre moins. » Add the pistou at the end, not during cooking. Éric does not like raw garlic, use less.
Three layers. The original note, the first correction, the second correction. Each one is a specific lesson learned in a specific moment with a specific person in mind. No cookbook could have told her that Éric does not like raw garlic. No digital recipe app would have remembered that the basil was too strong in the summer of 1994. The notebook knows these things because it was there.
Why Your Own Words Matter More Than the Right Words
There is a difference between transcribing a recipe and writing one. Transcription is what you do when you copy a list of ingredients and steps from a cookbook into a notebook, changing nothing. Writing a recipe is what you do when you have cooked a dish enough times to know where it bends, where it breaks, and where you have made it your own—and you put that knowledge down in language that reflects how you actually think about the dish.
This distinction matters because a recipe written in your own words carries your judgment inside it. When my grandmother wrote « jusqu’à ce que ça sente bon, » she was encoding a sensory skill she had developed over decades. She was not being imprecise. She was being precise about the only thing that mattered: the moment when the aromatics in the pan have given what they have to give, and you must move forward. A recipe that says sauté the onions for 5 minutes is less precise. Your onions and her onions and my onions are not the same onions, and five minutes means nothing without context.
The act of writing in your own words also forces a particular kind of attention. You have to decide what to include and what to leave out. You have to name the steps in a way that makes sense to you—not to a reader you will never meet. You have to confront what you do not yet know. If you cannot write the recipe without copying someone else’s language, you have not yet cooked the dish enough times to own it.
This is where the tradition of the cahier de cuisine intersects with something broader about writing and knowledge. The practice of recording observations in your own voice, with personal expression and lived experience woven through the instructions, is a form of creative nonfiction—what the Purdue OWL describes as writing that encompasses personal, voice-driven prose that goes beyond mechanical instruction. A kitchen notebook is not literature. But it is a creative document in the precise sense that it requires you to create meaning from experience, to choose words that carry your understanding, and to write for a reader you can imagine—your future self, your child, the friend who asked for the recipe at last Saturday’s dinner.
The Anatomy of a Recipe Card That Works
Here is what I have learned, from my grandmother’s notebook and from twenty years of keeping my own, about writing a recipe that someone else can actually use. Not a beautiful recipe. A useful one.
Name the dish the way you talk about it. Not Haricots Verts à la Provençale if you call it the green bean thing with the tomatoes. The name is the first thing someone reads, and if it does not match how the dish lives in your household, the recipe already feels foreign. My grandmother’s notebook has a recipe titled « La chose de mardi »—Tuesday’s thing—because she made it every Tuesday for thirty years. The name tells you nothing about the ingredients. It tells you everything about the dish’s place in the family.
List ingredients the way you buy them. Not 200g of haricots verts, trimmed and blanched but a handful of green beans per person, the thin ones, snap the ends off. The first version is a chef’s mise en place. The second is how a person shops and cooks. Quantities matter, but approximate quantities in language that reflects real market behavior are more useful than precise ones that suggest a precision the dish does not require.
Write the method in the order you actually do it. Not the logical order. The real order. If you start the rice before you chop the onions because the rice takes longer and you want to use the waiting time, write it that way. The logical order is for someone reading a recipe to understand its structure. The real order is for someone cooking it to get dinner on the table. These are different documents.
Note what can go wrong. This is the single most important thing, and it is the thing that printed recipes almost never do. If the béchamel breaks when you add the milk too fast, write that down. If the bottom of the tarte Tatin burns because your pan handle is not ovenproof and you forget to check, write that down. If the soufflé rises better when you let the base cool to room temperature before folding the whites, write that down. These notes are not admissions of failure. They are the accumulated intelligence of someone who has stood at that stove and watched the dish misbehave.
Record the adjustments you made for specific people. My grandmother’s note about Éric and the garlic is not a concession to pickiness. It is a record of hospitality—the specific care of feeding someone well, which means feeding them something they will enjoy. When I read that note, I know two things: how to make the soup, and how to make it for Éric. That is what a recipe card is supposed to do.
What a Printed Recipe Cannot Do
A printed recipe—whether in a cookbook or on a screen—gives you instructions. It cannot give you the memory of the last time you made the dish, because it was not there. It cannot tell you that your oven runs hot and the roasting time should be shorter, because it does not know your oven. It cannot warn you about the time you used salted butter instead of unsalted and the sauce was too salty, because it has no record of your failures. A recipe card, written and maintained by the person who cooks from it, does all of these things because it is a living document.
The difference is authorship. A printed recipe is authored by someone who has never met you. A handwritten recipe card is authored by someone who knows your kitchen, your ingredients, your guests, and your particular habits of attention and distraction. The Authors Guild, in its guidelines on writing and authorship, makes a point that applies here more directly than you might expect: it is your original voice, thinking, and creativity that make you the writer you are, and when you claim authorship in a work, it means something specific—something that a generic output cannot replicate. A recipe card is an authored document in this sense. It carries the intentionality, the accumulated judgment, and the particular voice of the person who wrote it. A machine-generated recipe, however competent, does not carry these things because it did not learn them by standing at a stove and watching a sauce reduce too far.
I am not making a romantic argument against printed recipes or digital tools. I own cookbooks. I use them. But I do not cook from them directly. I cook from my own cards, which began as copies of recipes from those books and became, over years of annotation and correction, something the books never were. Mine.
The Problem With the Blank Notebook
Here is where I have to be honest about the friction. Keeping a kitchen notebook sounds simple, and the practice itself is simple, but starting one is surprisingly hard. A blank notebook is an intimidating thing. You sit down to write your first recipe and you realize you do not know how much to write, how much to leave out, whether to organize by season or by category or by the order in which you learned the dishes. You write one recipe. It feels awkward. You close the notebook. Two months later, you cannot remember where you put it.
I have watched this happen to friends who genuinely wanted to keep a kitchen record. The problem is not motivation. The problem is structure. A blank page gives you no guidance about what a recipe entry should look like, how to leave room for annotations, or how to find what you wrote six months later. My grandmother’s notebook worked because she started it when she was fourteen and never stopped—but she also had a form, taught by her mother, that made each entry consistent enough to be useful.
For someone starting now, there are tools that can lower that initial barrier. I have come across an AI story generator like Unsloppy that helps maintain a living document—not as a recipe app that gives you someone else’s instructions, but as a writing tool that gives your own notes a structure to live in. The point is not to generate recipes. The point is to have a place where your seasonal observations, technique adjustments, and margin corrections can accumulate without the friction of a blank page or the impermanence of a scattered notes file. The tool serves the practice. The practice is still yours.
A Concrete Example: Writing the Card for Lentilles au Lardons
Last January, on a cold Monday that felt like it deserved lentils, I made my weekly pot of lentilles au lardons. Green lentils from the Puy, lardons from the butcher on rue de Bretagne, one shallot, a bay leaf, water. I have made this dish so many times that I no longer think about it while cooking—which is exactly when a recipe card is most useful. To record what you did without thinking, so that when someone asks you for the recipe, you can give them something more than a shrug.
Here is what I wrote in my notebook that evening:
Lentilles au lardons — lundi
2 tasses de lentilles vertes du Puy (les petites, pas les grosses)
200g de lardons fumés
1 échalote, coupée en deux
1 feuille de laurier
Eau froide pour couvrir + 2 cm
Faire revenir les lardons à sec dans la cocotte. Pas besoin d’huile. Quand ils sont dorés, ajouter l’échalote coupée en deux — la laisser colorer un peu. Ajouter les lentilles, laurier, eau. Porter à ébullition, écumer. Baisser le feu, couvercle entrouvert. 25 minutes. Goûter à 20. Les lentilles doivent être tendres mais pas en purée.
Saler à la fin — les lardons sont déjà salés. Poivre noir, beaucoup.
Notes: Trop d’eau cette fois. Couvrir juste au-dessus des lentilles, pas 2 cm. La prochaine fois goûter à 18 minutes — celles de cette année cuisent plus vite.
That is a complete recipe. It is not elegant. It will not be published. But it will allow me—or anyone who cooks in my kitchen—to make the same dish next Monday, and to benefit from the fact that I noticed there was too much water and that this year’s lentils cook faster than last year’s. The card is specific to my cocotte, my source for lardons, and the particular batch of lentilles du Puy I am working through. None of that information is transferable to a general audience. All of it is essential to me.
What to Do When a Dish Changes
The lentil recipe above is not finished. It will never be finished. Next January, the lentils may cook differently again. I may find a better source for lardons. I may decide to add a carrot, or to try the version with a spoonful of crème fraîche stirred in at the end, which a friend in Burgundy swears by. When that happens, I will write it in the margin or below the existing notes, with a date, the way my grandmother did.
This is the thing that distinguishes a living recipe from a dead one. A printed recipe is fixed. It was tested, edited, formatted, and sent into the world as a finished product. A handwritten recipe card is never finished because the cooking is never finished. The dish changes because the ingredients change, because the seasons change, because the cook changes. The card should change with it.
I have a recipe for tarte aux pommes in my notebook that I have been adjusting for fifteen years. The original version used butter from the supermarket. The current version uses butter from the fermière at the Saturday market, which has a higher fat content and behaves differently in the crust. The card records this transition—when I switched, why I switched, what I had to change about the technique. If I had kept the original printed recipe and simply followed it, I would never have noticed the difference. The card forced me to notice because the card is a document that expects to be revised.
The Real Reason to Keep a Kitchen Notebook
I have been making a practical argument, but there is a deeper one I should not bury. A kitchen notebook is a form of memory. Not nostalgia—memory in the active sense, the kind that informs what you do next. When I open my grandmother’s notebook and read her note about the basil, I am not reminiscing about her. I am cooking with her. Her judgment, formed in a specific summer in a specific kitchen, is present in my kitchen because she wrote it down.
This is what the cahier de cuisine does that no other form of recipe documentation can. It preserves not just the how but the why. The reason you adjusted the garlic, the reason you switched butters, the reason you started the rice before the onions. It preserves the cook’s mind at work, in real time, in language that is imperfect and personal and therefore honest.
If you have never kept one, start with a single recipe. Not a blank notebook—a single card. Write down a dish you have cooked enough times to have opinions about. Write it the way you actually cook it, not the way a cookbook would describe it. Note what went wrong the last time. Note what you changed. Date it. Put it somewhere you will find it. Cook the dish again next month, and add whatever you learned. You will have begun a document that no one else can write for you, because no one else has cooked in your kitchen or fed your people or made your mistakes. That is the point. That is the whole point.