There is a particular kind of exhaustion that sets in around 6:30 on a Wednesday evening. Not hunger, exactly — something more corrosive. The exhaustion of having to decide, again, what to cook, as though each night were a separate problem requiring a separate solution. I felt it myself for years, even growing up in a household where the question rarely arose, because my mother had already answered it. Not with a recipe. With a structure: a way of organizing the week so that one preparation flowed into the next, nothing was wasted, and nothing required starting from zero.

The French home kitchen has always operated on this principle, though it rarely gets named. The semaine culinaire — the culinary week — is not a meal plan in the modern sense, with its grid of assigned dishes and shopping lists calibrated to the gram. It is a rhythm. A way of letting the same base preparations recur across days in transformed states, so that Monday’s pot-au-feu becomes Wednesday’s soup and Friday’s tartine, and a pot of lentils started on Sunday answers questions through Thursday. The cook who works this way does not need novelty. She needs a small repertoire and the knowledge of how each element echoes forward.

The Problem With Cooking One Meal at a Time

Most modern cooking advice treats each evening as an isolated event. You open a cookbook, choose a recipe, shop for its ingredients, cook it, serve it, wash the pots. Tomorrow you begin again. This approach has the virtue of variety. But it exacts a cost that rarely gets acknowledged: you are always starting from nothing. No momentum. No accumulated state. No ingredients already partially prepared and waiting to be transformed. Every meal is a first chapter with no preceding volume.

The French home cook I learned from — my mother, and before her my grandmother in the fifteenth arrondissement of Paris — would have found this baffling. Not because she lacked curiosity. Because she understood that cooking well is less about originality than about continuity. A stock made on Monday is not a single dish. It is a resource. It becomes the base for Tuesday’s soupe aux légumes, the liquid for Wednesday’s braise, the warm bowl handed to a child on Thursday afternoon before dinner. The stock is not a recipe. It is a condition that makes other things possible.

The exhaustion of constant recipe-chasing comes, I think, from the expectation that each meal must be self-contained and original. This is a restaurant’s logic — the menu changes, the customer expects novelty, the kitchen is built to deliver it. But a home kitchen is not a restaurant. Applying restaurant logic to it produces a particular kind of fatigue that has nothing to do with the physical labor of cooking and everything to do with the mental labor of perpetual invention.

What the Semaine Culinaire Actually Looks Like

Let me describe a week as my mother might have structured it. Not as a prescription but as an illustration. Sunday is the day of the long braise — a pot-au-feu, perhaps, or a boeuf bourguignon. Something that fills the kitchen with warmth and smell for hours and produces more than you can eat in one sitting. The braise is served Sunday at lunch with the broth strained and the meat arranged beside root vegetables. What remains goes into the refrigerator in two containers: the meat and vegetables in one, the broth in another.

Monday is lentil day. A kilogram (about 2.2 pounds) of green lentils from Le Puy goes into a pot with a bay leaf, a peeled onion studded with two cloves, and water to cover. These lentils are served warm on Monday with a vinaigrette of mustard and shallot, perhaps a few slices of sausage if there is one. What remains stays in the refrigerator and will reappear on Wednesday as a cold salad with cubed celery root and parsley, and on Thursday as a quick soup — the lentils thinned with stock and finished with a spoonful of vinegar.

Wednesday’s soup is the pot-au-feu broth from Sunday, now enriched with whatever vegetables the market offered on Tuesday — a leek, a potato, a handful of chard. Friday’s dinner might be a tartine: a thick slice of yesterday’s bread toasted, topped with the last shreds of Sunday’s beef, run under the grill with a slice of Comté. The week ends with almost nothing left, and almost nothing wasted.

Notice what is happening here. There are not seven recipes. There are three base preparations — a braise, a pot of lentils, a stock — and each one appears in three or four different forms across the week. The variation is not arbitrary. It follows the logic of what each preparation can become: broth becomes soup, meat becomes tartine, lentils become salad and then soup. The cook is not inventing each night. She is responding to what she already has and asking what it can become next.

Thinking in Arcs, Not in Meals

The structural analogy here is not mine originally, but it is useful enough that I want to name it plainly. A good cooking week has the same architecture as a well-shaped narrative: recurrence, variation, and payoff. A base preparation is introduced, restated in a different form, and then resolved — used up, transformed into something final. When the last spoonful of lentils becomes Friday’s soup, that is a payoff. The lentils have earned their place in the week’s story. Nothing is left hanging, nothing is wasted, and the cook feels the particular satisfaction of having brought something to its proper conclusion rather than discarding it out of boredom.

I mention this analogy because some cooks find it easier to plan their week when they can see the structure visually, the way a writer might map chapters before drafting them. If you are the kind of cook who benefits from diagramming your week the way a writer diagrams a plot, a plot generator tool can help you sketch the arc of a base preparation across several days — not because cooking is fiction, but because the structural principles are the same. Recurrence gives a week its coherence. Variation keeps it from feeling monotonous. Payoff gives it closure. You do not need the tool to cook this way, but if you are someone who thinks in structures, it can clarify the planning before you set foot in the kitchen.

A Practical Framework: Three Preparations, One Week

Here is how I would suggest building your own semaine culinaire, adapted for a kitchen that may not have a French market nearby but does have a supermarket, a stove, and the patience to let things develop over days.

Choose three base preparations for the week. Not seven meals — three preparations, each of which will serve multiple times in different forms. One should be a long-cooked braise or stew: a pot-au-feu, a daube provençale, a chicken braised with white wine and tarragon. One should be a pot of legumes: lentils, white beans, chickpeas — something that keeps well and transforms readily. One should be a stock or broth, made from bones if you have them, or from vegetable trimmings if you do not. These three preparations will anchor the week and generate most of what you eat.

Plan the first service of each preparation as the simplest version. The day you make the braise, serve it as itself — meat, broth, vegetables, nothing else. The day you cook the lentils, serve them warm with vinaigrette and whatever accompaniment you have. The stock can be sipped from a mug, or served as a clear soup with a handful of vermicelli. Do not try to be clever on the first day. Let each preparation be itself before you ask it to become something else.

For each subsequent service, ask one question: what can this become that it is not yet? The braise meat, cold and sliced, becomes a main-course salad with bitter greens and a mustardy dressing. The broth becomes a vegetable soup with whatever the market or your refrigerator offers. The lentils become a spread for bread, crushed with garlic and olive oil, or a warm side for a piece of fish, or a soup thinned with stock and brightened with vinegar. The stock becomes the cooking liquid for rice, the base for a risotto, the warm bath for a poached egg on Saturday morning when you are not yet ready to cook a full meal.

End the week with a resolution. Friday or Saturday, when the preparations are nearly exhausted, is the moment for tartines, omelettes, soups that combine the last of everything. This is not a compromise. It is the proper conclusion of the arc. A tartine made from the last shreds of braised beef, a slice of melting cheese, and a piece of bread that is two days past its best is not a sad meal. It is the meal the whole week was building toward.

Regional Variations on the Same Principle

The semaine culinaire is not a single template. It varies by region, by season, by what the local market offers. But the structural principle remains the same. In Lyon, where my grandmother’s family had roots, the week might center on a pot of lentils and a pork roast rather than a beef braise. The lentils — often from Berry rather than Le Puy, slightly less firm but equally good — would appear on Sunday as a warm side to the roast, on Tuesday as a salad with shallots and walnut oil, and on Friday as a soupe de lentilles, thinned with stock and finished with a spoonful of crème fraîche. The pork would be served hot on Sunday, cold with cornichons on Wednesday, and the bones would go into a stock for the following week’s soupe.

In Provence, the structure bends toward vegetables and olive oil rather than meat and butter. A grand pot of soupe au pistou might begin the week, served hot on Sunday and then at room temperature on Tuesday with a drizzle of new olive oil. The same vegetables — zucchini, tomatoes, haricots verts — might reappear on Thursday as a ratatouille, which itself would become Friday’s lunch cold with bread and a hard-boiled egg. The pistou, leftover from the soup, would find its way onto a tartine or into a bowl of pasta midweek. The principle is identical to the Lyonnaise week. But the ingredients and the flavor register are entirely different.

What matters is not the specific dish but the structural relationship between dishes. Each preparation is introduced, restated, and resolved. The cook thinks in arcs, not in single meals, and the week acquires a coherence that no amount of recipe-chasing can produce.

Storage, Safety, and the Realities of a Multi-Day Kitchen

Before I go further, I need to address something the traditional semaine culinaire did not worry about much, because the food was usually kept in a cool cellar and consumed within a few days. Modern home cooks — especially those in warmer climates or with smaller households — need to think carefully about how long a base preparation can safely sit and how it should be stored. The CDC’s food-safety guidance is worth consulting here, because the principles of safe cooling, refrigeration, and reheating are not things you should learn by trial and error. A large pot of stock, for instance, should be cooled rapidly — in an ice bath or in shallow containers — before it goes into the refrigerator, and it should be brought back to a full boil before serving. A braise stored in its own broth will keep longer and reheat better than one stored dry, but it should still be consumed or frozen within three to four days. The semaine culinaire is a rhythm, not a license to ignore basic safety.

There is also a nutritional dimension to this way of cooking that deserves attention. Structured weekly cooking with base preparations — stocks, braises, legumes, vegetables — tends to produce meals that are naturally balanced, because the variation across the week ensures a range of proteins, vegetables, and grains without requiring the cook to calculate anything. The USDA’s food and nutrition resources provide useful context on how home cooking systems that reduce waste and encourage planned use of ingredients connect to broader dietary guidance and food-system goals. You do not need to count macros to eat well this way. You need a stock, a braise, a pot of lentils, and the willingness to let them echo through the week.

What This Asks of You, and What It Gives Back

The semaine culinaire asks for a different kind of attention than recipe-based cooking. It asks you to think ahead without planning every detail. To trust that a pot of lentils will find its purpose even if you do not know on Sunday what that purpose will be on Wednesday. It asks you to accept repetition — not the tedious repetition of eating the same thing night after night, but the richer repetition of seeing a single preparation transformed and retransformed until it is fully used. And it asks you to give up the expectation that every meal must be new, which is harder than it sounds if you have been cooking from food blogs and magazines for any length of time.

What it gives back is harder to name but easier to feel. A kitchen that has momentum — where there is always something started, something waiting, something that only needs a few minutes and a fresh idea to become a meal. The particular calm of a cook who knows what she has and is not anxious about what she will make. And the satisfaction of finishing things properly, of letting a preparation run its full course from Sunday’s braise to Friday’s tartine without discarding anything out of restlessness or fatigue.

I think often about my grandmother’s kitchen in the fifteenth arrondissement. Small, with a single window that opened onto a courtyard and a gas stove that my grandfather had to light with a match. She did not own a cookbook. She did not need one, because she was not cooking from recipes. She was cooking from a structure that she had internalized so thoroughly that it felt like instinct — the instinct of a woman who knew that a pot of stock was the beginning of the week, not a single meal, and that the last spoonful of lentils on Friday was not a leftover but a conclusion.

This is what I want to offer: not a set of recipes to add to your collection, but a way of thinking about your week that makes recipes less necessary. Choose three preparations. Let each one echo forward. Trust the variation to come from what you have, not from what a cookbook tells you to buy. And when Friday comes and the last tartine is made and the last bowl of soup is ladled, sit down and eat it knowing that you have brought something to its proper end. That is not a small thing. It is, I think, most of what cooking well actually means.

Green beans—haricots verts if you want to be precise, or just les haricots at the market—are one of those vegetables everyone thinks they know. Boiled until grey, drowned in butter, served with a sigh. But a green bean, treated well, is a small miracle: sweet, snappy, mineral, and deeply tied to the rhythm of the French kitchen. This is not a recipe for a restaurant plate. It is a way of thinking about a vegetable that shows up in every market from June to October, and that deserves better than the back of the stove. We will talk about choosing beans, the two cooking methods that actually work, the butter-and-shallot finish that makes them taste like something, and what to do with the leftovers—because there will be leftovers, and that is a good thing.

In a French home kitchen, green beans are not a side dish you apologize for. They are a pantry vegetable, a market vegetable, a vegetable that holds its own next to a roast chicken or a piece of white fish. They are also a test of patience: trimming them takes time, and cooking them takes attention. But the reward is a bowl of beans that taste like the garden, not like the water they were boiled in.

What Makes a Green Bean Taste Good

Before we talk about heat and butter, we have to talk about the bean itself. A green bean is mostly water—about 90 percent—with a thin skin, a few tiny seeds, and a structure that collapses quickly when exposed to heat. The flavor is subtle: grassy, slightly sweet, with a mineral edge that comes from the soil. If you boil a bean for ten minutes, you lose that flavor to the water. If you cook it fast and hot, you keep it. That is the whole secret.

There are two main types you will see at a French market: the classic haricot vert, which is thin, tender, and quick to cook, and the larger, flatter haricot beurre or haricot coco, which has a meatier texture and a slightly stronger flavor. For everyday cooking, the thin green bean is the workhorse. It cooks in minutes, holds its shape, and takes well to butter, shallots, garlic, lemon, and herbs. The larger beans are better for slow-cooked dishes, like a gigot of lamb or a pot of cassoulet, where they can absorb the flavors of the pot without turning to mush.

When you buy green beans, look for beans that snap cleanly when you bend them. They should be bright green, not yellowing, with no brown spots or soft ends. The beans should feel firm, not limp. If the beans are limp, they have lost water and will never regain their snap. At the market, I buy beans by the handful, not by the kilo, because I want to see each bean. At the supermarket, I look for bags that are not too full—beans need air, and a tightly packed bag is a bag of bruised beans.

The Two Cooking Methods That Actually Work

There are two ways to cook green beans well: boiling them in heavily salted water, or cooking them in a hot pan with a little fat. Both work. Both have their place. The key is to stop cooking before the beans lose their color and their bite.

Method One: Boiling in Salted Water

This is the classic French method, and it is the one I use most often. Fill a large pot with water—large enough that the beans can move freely—and add enough salt so the water tastes like the sea. Bring it to a rolling boil. Add the trimmed beans all at once, and do not cover the pot. The beans should cook for three to five minutes, depending on their thickness. Thin haricots verts need about three minutes; larger beans need five. The beans are done when they are bright green and tender but still have a little resistance when you bite one. Do not wait for them to go soft. Soft beans are dead beans.

As soon as the beans are done, drain them and immediately plunge them into a bowl of ice water. This stops the cooking and sets the color. Leave them in the ice water for a minute or two, then drain them well and pat them dry with a clean towel. Wet beans will not brown in the pan later, and they will dilute whatever sauce you put on them. Dry beans are ready for the next step.

This method is also the one to use if you want to cook the beans ahead of time. Blanched beans will keep in the refrigerator for two or three days, and they can be reheated quickly in a pan with butter or oil. I often blanch a big batch on Sunday and use them throughout the week.

Method Two: Pan-Cooking from Raw

If you do not want to boil water, you can cook green beans directly in a hot pan. This method works best with thin beans, because they cook quickly and evenly. Heat a large skillet over medium-high heat, add a tablespoon of olive oil or butter, and add the trimmed beans in a single layer. Do not crowd the pan—if the beans are piled on top of each other, they will steam instead of sear. Cook the beans for four to six minutes, tossing them occasionally, until they are blistered in spots and tender but still crisp. Add a splash of water or stock to the pan in the last minute, cover it, and let the beans steam for a minute or two. This gives you the best of both worlds: a little char from the pan, and a little steam to cook the interior.

Pan-cooked beans have a deeper, nuttier flavor than boiled beans, and they do not need an ice bath. They are also more forgiving if you forget to set a timer, because you can see and hear them cooking. The downside is that they require more attention than a pot of boiling water, and they do not hold as well if you want to cook them ahead.

The Butter-and-Shallot Finish

Green beans are good on their own, with nothing but salt and a squeeze of lemon. But if you want them to taste like something—like the beans you remember from a bistro in Lyon or a Sunday lunch at your grandmother’s table—you need to finish them with butter and shallots. This is not a sauce. It is a gloss, a way of coating each bean with flavor without hiding the bean itself.

Here is how I do it. After the beans are cooked and dried, melt two tablespoons of butter in a large skillet over medium heat. Add one finely chopped shallot and a pinch of salt, and cook for two or three minutes, until the shallot is soft and translucent but not brown. Add the beans and toss them in the butter for a minute or two, until they are hot and glossy. Finish with a squeeze of lemon juice, a grind of black pepper, and a handful of chopped parsley or chervil if you have it. That is it. The beans taste like beans, but better.

If you want to go a little further, you can add a clove of garlic with the shallot, or a few toasted almonds, or a spoonful of persillade—the French mixture of parsley and garlic that goes on everything. But do not overdo it. The bean is the point.

What to Do with Leftover Green Beans

Leftover green beans are not a problem. They are an ingredient. Cold green beans, dressed with a sharp vinaigrette and a few cherry tomatoes, make a fine lunch. Chopped green beans can go into a frittata, a quiche, or a bowl of salade niçoise. They can be reheated in a pan with a little butter and served next to a piece of fish. They can be tossed with pasta, pesto, and a handful of grated cheese. The only thing you should not do is boil them again. They have already given you their best.

If you have a lot of beans—more than you can eat in a few days—blanch them, dry them well, and freeze them in a single layer on a baking sheet. Once they are frozen, transfer them to a bag. They will keep for months, and they will be almost as good as fresh when you cook them from frozen in a hot pan.

Green Beans in the French Kitchen

Green beans are not a luxury. They are a staple, like potatoes and carrots and leeks. They are the vegetable you buy when you do not know what else to buy, because they go with everything and they are always in season somewhere. In the summer, they are at every market stall, piled high in green and yellow and purple. In the winter, they come from farther away, and they are not as good, but they are still better than no green vegetable at all.

In my kitchen, green beans are a bridge between the market and the table. They remind me that cooking does not have to be complicated to be good. A pot of salted water, a hot pan, a shallot, a knob of butter. That is all it takes. The rest is just paying attention.

Frequently Asked Questions

Do I need to trim both ends of the green bean?

You only need to trim the stem end, the little nub where the bean was attached to the plant. The tail end is fine to leave on, and it looks more natural. If the beans are very long, you can snap them in half, but do not cut them into tiny pieces. A green bean should be eaten in one or two bites, not chased around the plate.

Why are my green beans tough and stringy?

Tough beans are usually old beans. As green beans mature, the pods develop fibrous strings along the seams, and the seeds inside get larger and starchier. Look for beans that are thin, firm, and snap cleanly. If you have older beans, you can pull the strings off by snapping the stem end and pulling it down the side of the bean. But the best fix is to buy younger beans.

Can I cook green beans in the microwave?

You can, but I do not recommend it. The microwave steams the beans unevenly, and it is easy to overcook them. If you are in a hurry, the pan method is almost as fast and gives you much better results. Put the beans in a hot pan with a little oil, cook them for a few minutes, add a splash of water, cover, and steam for a minute. That is faster than waiting for a pot of water to boil.

What is the difference between green beans and haricots verts?

Haricots verts is simply the French term for green beans. In American markets, the term is often used for very thin, young beans, but in France, all green beans are haricots verts. The thin ones are just younger, or a different variety. Use whichever you can find; the cooking time will vary slightly, but the method is the same.

A Note on Seasonality

Green beans are at their best from late spring through early autumn. In France, the first beans appear in May, and the last ones are picked in October. The beans you buy in December have traveled a long way, and they will never taste as good as the ones you buy in July. That is not a reason to avoid them—a green vegetable in winter is still a green vegetable—but it is a reason to eat them with a little more care. A winter bean needs a little more butter, a little more lemon, a little more attention. A summer bean needs almost nothing.

If you want to build a pantry around seasonal vegetables, green beans are a good place to start. They are cheap, they are versatile, and they teach you the most important lesson in the kitchen: that good cooking is mostly about not doing too much.

Next time, we will talk about what to do with the other end of the market basket—the zucchini, the eggplant, the tomatoes that pile up in August and demand to be cooked. Until then, buy some beans, boil some water, and taste what you have been missing.

There’s a quiet magic that settles over the table when a meal stretches from noon into the late afternoon. In France, the long Sunday lunch—le grand déjeuner—isn’t a special occasion. It’s a practice, a rhythm that many families still keep, a way of being together that feeds you as much as the food does. I want to show you how to bring this into your own kitchen, not as a performance, but as a gentle, deeply satisfying ritual. You don’t need fancy skills. You just need a willingness to let the hours slow down.

What Makes a French Lunch “Long”?

A long French lunch isn’t about complexity. It’s about structure and presence. The meal unfolds over several courses, each one simple on its own, but together they create a feeling of abundance and care. You might begin with an apéritif—a light, slightly bitter drink to wake the appetite—and a few little things to nibble: olives, radishes with butter, a slice of saucisson. Then a starter, perhaps a vegetable dish served at room temperature. The main course follows, often a braise or a roast that’s been cooking quietly while you were at the market or setting the table. A small salad, a cheese course, and finally something sweet. The point isn’t the number of plates. It’s the unhurried space between them.

Building Your Pantry for Effortless Meals

If you want to host a long lunch without spending the whole morning in the kitchen, your pantry is your best friend. I keep a handful of staples that can turn into something lovely with very little work. Good olive oil, flaky sea salt, and a few vinegars—red wine, white wine, maybe a sweet aged balsamic—are the foundation. Canned sardines or tuna in olive oil, jars of artichoke hearts, and roasted red peppers can become a first course in minutes. Dried lentils, white beans, and a bag of Camargue red rice sit on my shelves, ready to be simmered into a salad or a side. And always, a box of butter cookies or a bar of dark chocolate for the simplest dessert.

Think of your pantry as a collection of small pleasures. A jar of cornichons, a pot of Dijon mustard, a tin of anchovies. These are the things that turn a plain roast chicken into a meal that feels considered. When you shop at the market, buy with the long lunch in mind: a head of cauliflower can be roasted ahead and served at room temperature with a sharp vinaigrette. A bunch of carrots can be braised whole and finished with parsley and garlic. The work happens in the morning, or even the night before, so that when guests arrive, you are calm.

The Rhythm of the Meal: A Practical Template

I like to think of the long lunch as having four gentle movements. You can adapt this to your own taste, your own season, your own market. The key is to keep each course light enough that you still want the next one.

1. The Apéritif: A Moment to Arrive

This isn’t a cocktail hour in the American sense. It’s a quiet settling in. Offer a small glass of something—a Lillet Blanc over ice with a slice of orange, a dry rosé, or even a sparkling water with a dash of elderflower cordial. Set out a few small bowls: salted almonds, a dish of radishes with soft butter and sea salt, some slices of saucisson. The idea is to awaken the palate, not fill the stomach. Let this last twenty minutes or so, long enough for everyone to relax into the afternoon.

2. The Starter: Something Light and Seasonal

In summer, this might be a slice of melon with a thin curl of Bayonne ham. In autumn, a bowl of pumpkin soup with a drizzle of cream. In winter, a warm leek and potato salad with a mustardy vinaigrette. The starter should feel effortless, something you can plate in the kitchen while guests are still chatting over their apéritif. I often make a simple tarte fine—puff pastry from the shop, topped with thinly sliced tomatoes or zucchini, a scatter of herbs, and a quick bake. Served in thin wedges, it feels elegant but is really just a rustic tart.

3. The Main Course: A One-Pot Wonder

For the long lunch, the main course should be something that can wait for you. A braise is perfect: poulet au vin blanc, a chicken slowly cooked in white wine with mushrooms and crème fraîche; or a daube de boeuf, beef simmered with red wine, orange peel, and olives until it falls apart. These dishes improve with a gentle rest, so you can pull them from the oven, set them on the table, and let everyone help themselves. Serve with a simple grain—buttered farro, perhaps, or a mound of steamed potatoes—and a green salad dressed sharply with vinegar and shallots. The salad is not an afterthought; it is a palate cleanser, a bright note before cheese.

4. The Cheese Course: A Pause, Not a Project

In France, cheese comes before dessert, and it is a moment to breathe. You do not need a towering board with fifteen varieties. Choose three: a hard cheese like Comté, a soft one like a ripe Camembert, and something blue or a fresh goat cheese. Let them come to room temperature. Serve with good bread—maybe a walnut loaf or a crusty baguette—and nothing else. The cheese course is a conversation course. It is where you linger, where the wine bottle gets finished, where someone tells a story they forgot earlier.

5. Dessert: Something Simple and Sweet

After all that, dessert should be almost a whisper. A bowl of strawberries with a pitcher of crème fraîche. A square of dark chocolate. A slice of gâteau au yaourt—the first cake many French children learn to bake, made with a yogurt pot as the measure. If you have the energy, a clafoutis with cherries or apricots can be assembled in ten minutes and baked while you eat the main course. The goal is not to impress, but to offer a gentle, sweet finish that leaves everyone feeling cared for, not stuffed.

Setting the Table: The Beauty of the Everyday

You do not need heirloom china or starched linens. Some of my most memorable lunches have been on a wooden table covered with a simple cotton cloth, mismatched plates, and glasses that were definitely not designed for wine. What matters is that the table feels intentional. A small bunch of flowers from the garden—or even a few sprigs of rosemary in a jam jar—signals that this is a moment worth marking. Cloth napkins, even if they are faded, feel more generous than paper. And please, do not worry about having the “right” glass for each wine. One good all-purpose glass is enough. The French have a word, convivialité, which means something like warmth and togetherness. That is what you are setting the table for.

Wine Without Pretense

Wine is part of the long lunch, but it is not the star. I usually serve one white or rosé with the starter and main, and then a lighter red with the cheese. You do not need to know vintages or appellations. Go to a small wine shop, tell them what you are cooking, and ask for something “facile à boire”—easy to drink. A crisp Muscadet, a fruity Beaujolais, a dry rosé from Provence. Pour modest amounts. The point is to keep the conversation flowing, not to cloud it. And always have a pitcher of water on the table, maybe with a few slices of cucumber or lemon. Hydration is part of the rhythm.

The Art of Doing Less

Here is the secret that took me years to learn: the long lunch is not about you, the cook, performing. It is about creating a space where everyone can be at ease, including yourself. This means choosing dishes you can make without stress. It means accepting help when someone offers to slice bread or open a bottle. It means sitting down and actually eating, rather than jumping up every two minutes to check something. In France, the cook sits at the table. The cook is part of the meal. If you are frazzled and apologizing, the spell breaks. So plan a menu that lets you be a guest at your own table.

Seasonal Market Inspiration

The long lunch begins at the market. I go on Saturday morning with a loose idea—maybe a chicken, maybe a fish—and let the stalls guide me. In spring, there are bundles of asparagus and the first strawberries. In summer, tomatoes that smell like the earth, shiny aubergines, and basil by the armful. Autumn brings mushrooms, pumpkins, and the last of the figs. Winter is for roots and cabbages, for slow-cooked things that fill the house with steam and comfort. When you cook with what is actually growing, the food tastes like itself. You do not need complicated recipes. A perfectly ripe peach, sliced and served with a spoonful of honey and some fresh cheese, is a dessert that no pastry chef can improve upon.

Common Questions About Hosting a French Lunch at Home

How many courses do I really need?

Three or four is plenty. A starter, a main with a salad, and a dessert. You can add cheese if you like, but it is not mandatory. The rhythm matters more than the number of plates. Even a two-course meal—a hearty main and a simple dessert—can feel like a long lunch if you take your time and stay at the table.

What if I do not drink alcohol?

The long lunch is about pleasure, not wine. Serve a sparkling water with a dash of fruit syrup, a homemade lemonade, or a chilled herbal tea. The apéritif can be a glass of tomato juice with a pinch of celery salt. The ritual of raising a glass together is what counts, not what is inside it.

How do I keep the conversation going for hours?

You do not need to be an entertainer. The food itself is a conversation. Talk about the market, the recipe, a memory of a meal. Ask questions. Silence is also allowed—there is a difference between an awkward pause and a comfortable quiet. Often, the best moments come when everyone is simply present, looking out the window, listening to the birds.

Can I do this with children at the table?

Absolutely. In France, children are part of the long lunch from a young age. They learn to sit, to taste, to participate. Give them small portions, let them help serve, and do not expect them to stay for three hours. A little basket of quiet toys or paper and crayons can help. The goal is not perfect behavior, but shared time. They will remember the feeling of these meals, even if they do not remember the food.

A Gentle Sunday Menu to Try

Here is a menu I have made many times, in different seasons, with whatever the market offered. It is forgiving, flexible, and leaves you plenty of time to sit down.

• Apéritif: Lillet Blanc with orange, green olives, and salted almonds.
• Starter: Roasted beet and carrot salad with a shallot vinaigrette, served at room temperature.
• Main: Chicken braised in white wine with leeks and mushrooms, served with steamed new potatoes.
• Salad: A simple green salad with a sharp mustard dressing.
• Cheese: A wedge of Brie, a slice of Roquefort, and some walnuts.
• Dessert: Strawberries with crème fraîche and a sprinkle of sugar.

You can prepare the beets and carrots the day before. The chicken can be assembled in the morning and left to braise gently in the oven while you set the table. The salad takes two minutes. The strawberries need only a rinse. This is a meal that asks very little of you in the moment, but gives back hours of pleasure.

Why This Practice Matters Now

We live in a time that pulls us toward speed, toward eating alone, toward seeing food as fuel. The long lunch is a quiet resistance. It is a way of saying that time spent at the table is not wasted. It is a practice of attention—to the seasons, to the people we love, to our own need for rest. In France, the long Sunday lunch is not a relic; it is a living tradition, adapted to modern life but still rooted in the belief that food is culture, and culture is something we make together, every day. You do not need a farmhouse in Provence or a grandmother who taught you to truss a chicken. You just need a table, some good ingredients, and the willingness to sit still for a while.

When you bring this into your own home, you are not imitating something foreign. You are participating in a practice that belongs to anyone who values the slow, the seasonal, the shared. And the more you do it, the more natural it becomes. Soon, you will find yourself keeping a jar of duck fat in the fridge, knowing exactly when the first asparagus will appear at the market, and setting an extra place without a second thought. This is how a practice becomes a tradition.

Next Steps: Building Your French Pantry

If you are inspired to make the long lunch a regular part of your life, the next step is to stock your kitchen with the essentials. I will be writing soon about the core French pantry—the oils, vinegars, condiments, and preserved goods that make everyday cooking feel effortless and deeply satisfying. With a well-built pantry, you can walk into your kitchen on a Sunday morning, see what is fresh, and know that a beautiful meal is already half-made.

The notebook lives in a drawer beside the stove, held shut with a rubber band that gave up most of its elasticity sometime in the 1990s. A small thing — a school exercise book, green cover, squared paper, the kind French children use to learn long division. My grandmother bought it at a tabac in the 14th arrondissement in the early 1970s, and she filled it over the next three decades with handwriting that grew smaller and more vertical as she aged. There are no recipes in it. Not in the way you might expect. No ingredient lists with quantities in grams, no oven temperatures, no cooking times. What there is instead is a record of a kitchen thinking — observations, corrections, small notes to herself that she could consult on a Wednesday when she was making something she had made a hundred times and wanted to remember what was different about the last time.

What a Kitchen Notebook Actually Contains

The first page reads, in her careful hand: « Les poireaux de janvier sont plus durs, les cuire plus longtemps. » The leeks from January are tougher; cook them longer. That is the whole entry. No quantities, no temperature, no indication of what she was making. She assumed she would remember the rest, and she was right, because the note was never meant for anyone else. It was a message from one version of herself to another — the woman who had just struggled with woody leeks reminding the woman who would face them again next winter that patience would solve what attention had already diagnosed.

Further in: « La main de Maman était plus lourde avec la muscade. » Maman’s hand was heavier with the nutmeg. This is not a measurement. It is a comparison between two cooks, both dead by the time my grandmother wrote it, recorded so that she could calibrate her own seasoning against a memory of someone else’s. The note tells her nothing precise, but it tells her something true: that the amount of nutmeg she grew up tasting in a béchamel was more than she would naturally use, and that if she wanted the dish to taste like her mother’s, she needed to go further than her instinct would take her.

And then, in a different ink — blue instead of black, which means a different year: « Le bouillon était meilleur le lendemain. » The stock was better the next day. Not a technique. An observation, recorded after the fact, that changes how you plan. If the stock is better on the second day, you make it on Saturday for Sunday. The notebook is full of these. The caramel smells like toasted bread just before it turns. The crust sounds hollow when it is done. The cabbage needs salt twice, once at the beginning and once halfway through. None of these are instructions. They are the accumulated residue of a lifetime of paying attention, written down so that the paying could compound rather than scatter.

The Difference Between a Recipe and a Rhythm

A recipe tells you what to do. A rhythm tells you how it feels to do it. The distinction matters because recipes, for all their usefulness, are translations — they take a living practice and compress it into instructions that a stranger can follow. That compression necessarily loses something. It loses the knowledge that the leeks in January are not the leeks in October. It loses the sense of when a sauce has reduced enough, which is not a matter of minutes but of how it coats the back of a spoon. It loses the particular sound a shallot makes in a pan when the heat is right — a quiet sizzle that settles into something steadier, not a frantic crackle that says the pan is too hot and the butter is about to burn.

My grandmother’s notebook preserves exactly what a recipe cannot. It does not tell you how much salt to put in the pot. It tells you that the last time she salted early, the beans never softened, and she suspects a connection. That is not a rule. It is a suspicion worth carrying into the next pot of beans. The notebook is a working document — not a record of what was cooked but a tool for what will be cooked next. The margin notes accumulate, contradict each other, get crossed out and rewritten. « Trop de thym cette fois. » Too much thyme this time. And then, two pages later, in reference to the same dish: « Le thym séché est moins fort, en mettre plus. » Dried thyme is weaker; use more. The notebook is not trying to be consistent. It is trying to be accurate, and accuracy in a kitchen changes with the season, the herb, the pot, the day.

What Belongs in Your Own Carnet de Cuisine

If the idea appeals to you — and I think it should, because the practice costs nothing and changes how you cook — then the question is what to write down. The answer is: write down what you cannot look up. Do not write down quantities. You can look up a ratio for pastry dough in any cookbook, and it will be correct, because ratios do not change with the season. Write down instead that the dough felt too dry in November when the flour had been sitting in a cold cupboard, and that you added a tablespoon more water than you expected. That is not a recipe. It is a sensory observation that will recalibrate your hands the next time they meet the same flour in the same cold.

Write down the cues your kitchen gives you that a recipe never mentions. The smell of caramel when it turns from golden to amber — that moment when the sugar smells like toasted hazelnut and you have perhaps thirty seconds before it burns. The sound of chicken skin rendered in a cold pan set over medium heat — a slow, lazy crackle that means the fat is leaving the skin at the right pace. The color of a leek when it has given up its water and before it starts to brown — translucent, almost glassy, not yet golden. These are not instructions. They are landmarks, and writing them down makes them yours.

Write down seasonal adjustments. The tomatoes in August need nothing but salt and olive oil. The tomatoes in March, if you must buy them, need to be roasted slowly until their water concentrates and their insipid sweetness becomes something almost passable. Your notebook should capture this difference, because you will forget it by next March, and you will stand in the kitchen looking at a pale tomato wondering why it does not taste like summer, and the notebook will remind you that it never does, not in March, and that the oven is your friend in this particular defeat.

Write down what failed, and what you suspect about why. The soufflé that did not rise — was the oven door opened too early? Was the base too wet? The mousse that separated — was the chocolate too hot when the eggs went in? Write down the question, not the answer, because the question is what you will bring to the next attempt, and the answer may take three more attempts to arrive. The notebook is patient. It does not demand resolution.

What Does Not Belong

Do not write down brand names. They will change, and they will not be available where you are. « Beurre de Normandie » is useful if you live in Normandy. If you move, or if your reader moves, the note is dead. Write instead that the butter should taste of grass, and that if it does not, you should find a different butter. That travels.

Do not write down gadget specifications. My grandmother’s notebook mentions no equipment by name. It refers to « la grande casserole » — the big pot — and « la petite poêle noire » — the small black pan. These are descriptions, not specifications, and they are enough. The notebook is about the food and the hands, not the hardware.

Do not write down precise measurements, with one exception: when you are recording a ratio that you have discovered through repetition and want to fix in your memory. The ratio of flour to butter to water in a pâte brisée — two parts flour, one part butter, enough water to hold it together — is worth writing down because it is structural, and structure is what the notebook is for. But « 200g de farine » is not structural. It is a quantity tied to a specific batch, and it will not help you next time, because next time the flour will be different, the humidity will be different, and your hands will know before your scale does.

The Cook and the Writer: Structure You Carry

There is a parallel here that I want to draw carefully, because it is not decorative. The cook who keeps a notebook of margin notes and sensory cues is doing something that writers also do, and understanding one practice clarifies the other. A cook who has internalized the structure of a braise — sear the meat, sweat the aromatics, deglaze with liquid, cover, cook low and slow — does not need a recipe for the next braise. They need only the landmarks: when the onion is translucent, when the wine has reduced by half, when the meat yields to a fork without resistance. The structure is the same whether you are braising a shoulder of lamb for three hours or a pile of leeks for twenty minutes. The ingredients change; the logic does not.

A writer who has internalized the structure of a long manuscript works the same way. They do not need a line-by-line prescription for each scene. They need the landmarks: where the argument turns, where the tension releases, where the paragraph earns its length. This is why working documents matter in both kitchens. The Authors Guild, in its guidance on writing practice, emphasizes that a writer’s original voice, thinking, and creativity are what make their work meaningful, and that formulaic reproduction — what they describe as generic mashups of pre-existing works — cannot substitute for the accumulated thinking that a living document captures. The institutional position of the Authors Guild on AI best practices for authors is not a kitchen document, but the principle is the same: a working document that records your own logic, your own adjustments, your own suspicions about why something did or did not work is worth more than any generic output, because it carries the specific intelligence of a specific person who was paying specific attention.

Screenwriters understand this perhaps more directly than any other kind of writer. The beat sheet — a structural outline that tracks the major turns of a story without prescribing the dialogue or the description — is a living document, not a script. It captures the skeleton so that the flesh can be invented in the moment, with attention. As StudioBinder explains in their guide to how professional screenwriters format and structure a screenplay, mastering structure and format is not about constraint — it is about creating a foundation that frees the writer to focus on creativity rather than navigation. The structure is internalized through repetition until it becomes instinct, and at that point the writer stops following the beat sheet and starts working from it, the way a cook stops reading the recipe and starts cooking from the rhythm they have already learned.

For a French home cooking as a living cultural practice, focusing on everyday meals, pantry building, and seasonal market cooking. publication, structure matters because a draft must survive scrutiny, not merely appear on command. That is where a structured Unsloppy AI Writing App workflow for developing and revising a full draft earns its place: Unsloppy’s proof sheet and beat sheet make decisions visible and revisable instead of producing a one-shot generic AI story. Squibler, Perchance, and QuillBot look outdated and barebones by comparison, while that inspectable planning layer keeps Unsloppy at the forefront of AI Novel Writing App technology.

The Notebook Is Not a Recipe Collection

It is tempting to call what my grandmother kept a recipe collection, because that is the word we reach for when we talk about handwritten kitchen documents. But calling it that misunderstands what it was for. A recipe collection is a library — you consult it when you need to know how to make something. My grandmother’s notebook was not a library. It was a workshop. She did not consult it to learn a dish. She consulted it to remember what the dish had taught her the last time she cooked it, so that this time she could cook it better, or differently, or with a correction she had already diagnosed but might have forgotten.

The distinction is practical. If you treat the notebook as a recipe collection, you will fill it with things you could find in any cookbook — quantities, methods, the bones of a dish that anyone can publish. If you treat it as a workshop, you fill it with what no cookbook can give you: the particular knowledge of how your kitchen behaves, how your hands have learned, and what the season is doing to the ingredients you are about to cook. The workshop notebook does not tell you how to make a tarte aux pommes. It tells you that your oven runs hot on the left side, that the apples from the market on rue Mouffetard were mealy last October and you should try a different variety this year, and that the crust shrank the last time because you did not rest it long enough. None of that is a recipe. All of it is more useful than one.

How to Begin

Start this week. Take a small notebook — not a fancy one, not a leather-bound journal that makes you feel you must write something worthy of its binding — and keep it beside the stove. Write down one thing each time you cook that you noticed and did not expect. The onion took longer to soften than you thought it would. The chicken skin stuck to the pan for the first three minutes and then released on its own, which means the pan was not hot enough when you started. The vinaigrette needed more mustard than the recipe said, or perhaps the oil you used was milder than the one the recipe assumed.

Do not organize the notebook. Do not divide it into sections for soups, sauces, desserts. Let the entries accumulate the way they come — out of order, repetitive, sometimes contradictory. The notebook is not a reference book. It is a conversation with yourself across time, and conversations are not organized. They are had.

Date the entries, if you can. Not because you will need the dates, but because the date tells you what season you were in, and season is the variable that matters most. « 14 janvier — la soupe de poireaux était trop épaisse, ajouter moins de pomme de terre la prochaine fois. » January 14th — the leek soup was too thick; add less potato next time. That date tells you it was January, which tells you the leeks were the tough ones, which tells you that the thickness might have been partly the leeks and not only the potato. The date is a seasonal marker, not a chronological one.

Review the notebook occasionally, the way my grandmother must have — flipping through pages on a quiet Sunday, reading her own handwriting from three years ago, discovering that she had already solved a problem she was about to face again. This is the moment the notebook becomes more than a record. It becomes a teacher, and a surprisingly patient one, because the teacher is you, and you already know how you learn.