Every Day I Have to Figure Out What to Eat - How to Stop Losing Your Life to “What's for Dinner?” ebook

INTRO

It is 6:17 p.m. You are standing in front of the refrigerator with the door open, staring at its contents as if they have been legally required to develop new ideas since yesterday. They have not. There is half a cucumber, three eggs, a container you no longer trust, mustard in four emotional stages, and a jar of something purchased during a brief period when you believed you were going to become the kind of person who cooks with capers.

You close the refrigerator.

Then, because apparently twelve seconds may have changed the situation, you open it again.

Still no dinner.

This is how one of the most repetitive problems in adult life begins: not hunger, exactly, but the question attached to it. What are we eating? What should I cook? Do I need groceries? Is there anything quick? Is ordering takeout irresponsible? Did we already have pasta twice this week? Does toast count as dinner if you put something green next to it?

Nobody warned us how much administrative work would be involved in remaining fed.

As a child, food often appeared through systems you did not manage. Someone bought it, planned it, cooked it, or at least announced that dinner would happen at a particular time. Then adulthood arrived and handed you a refrigerator, a grocery store with 38,000 products, several delivery apps, nutritional advice from fourteen mutually hostile internet tribes, and the permanent responsibility of deciding what goes into your mouth three times a day.

Congratulations on your independence.

Please select a protein.

The exhausting part is not usually cooking itself. Sometimes cooking is annoying, certainly, especially when a recipe describes itself as “easy” and then asks you to finely chop twelve things, toast spices, zest a lemon, make a reduction, and locate fresh tarragon as if you live above a Parisian market. But for many people, the real drain happens before the pan even reaches the stove. It is the endless sequence of tiny decisions: what to eat, what ingredients are missing, whether you feel like cooking, what everyone else wants, how healthy it should be, how much effort you can tolerate, and whether the chicken in the fridge is still chicken or has entered the next stage of its career.

You are not making one food decision.

You are running a small restaurant with one exhausted employee and extremely inconsistent customers.

The customers are also you.

Monday You wants to eat healthier. Tuesday You wants something comforting. Wednesday You forgot to thaw anything. Thursday You is suddenly convinced that all existing meals are boring. Friday You deserves a treat because surviving Thursday was apparently an achievement worthy of catering. By Sunday, you are eating a strange collection of leftovers because throwing them away feels wrong and planning another meal feels worse.

Then Monday returns with the confidence of someone who remembers nothing.

This cycle creates a peculiar kind of mental fatigue because the problem never stays solved. You can successfully answer “What’s for dinner?” tonight, and the universe responds with an encouraging message:

Excellent.

See you tomorrow.

That is what makes food planning different from many other tasks. You can renew your passport and, with luck, stop thinking about it for years. You can buy a vacuum cleaner and consider the matter closed until it begins making the sound of a helicopter swallowing a fork. But eating is relentless. You finish breakfast and lunch is already somewhere backstage stretching.

The goal of this book is not to turn you into a meal-prepping machine who spends Sunday afternoon filling thirty-seven identical containers while smiling calmly beside an industrial quantity of broccoli. If you enjoy that, wonderful. I respect your containers. Please do not make me label them.

The goal is simpler: to make feeding yourself take less thought.

That distinction matters. People often try to solve food fatigue by becoming dramatically better at food. They download complicated meal-planning apps. They save 126 recipes. They subscribe to cooking channels. They create folders called QUICK DINNERS, HEALTHY DINNERS, REALLY QUICK DINNERS, and THINGS I WILL DEFINITELY COOK, which gradually become museums of meals nobody has ever seen in person.

Information is rarely the main problem.

You already know that chicken exists.

You know rice exists.

You may even possess both simultaneously.

And yet there you are at 6:17 p.m., looking into the refrigerator like a detective investigating a disappearance.

The problem is usually that your food system asks you to make too many decisions too often. Every meal begins from zero. You keep treating dinner as a new creative project instead of a recurring household function. You ask yourself what you “feel like” eating at precisely the moment when you are tired, hungry, busy, and therefore psychologically qualified to answer only one question:

“Can someone bring me food immediately?”

This is not a character flaw. It is bad timing combined with unnecessary complexity.

Hunger is a terrible executive chef.

When you are hungry, the part of your brain responsible for thoughtful planning is competing against a much older department whose strategic vision is roughly: calories now. This is why a person can spend twenty minutes considering balanced meals and then suddenly be standing in the kitchen eating shredded cheese directly from the package.

The meeting has been adjourned.

Over the course of this book, we are going to reduce the number of food decisions you have to make without reducing your life to seven joyless meals repeated until morale collapses. You will build a simple system for deciding what to eat, keeping useful food available, creating reliable default meals, shopping with less nonsense, handling other people’s preferences, surviving busy days, dealing with boredom, using takeout without turning it into either a moral crisis or a financial subscription, and recovering when the entire system falls apart because life occasionally has opinions.

Most importantly, you will stop demanding that every meal be an inspired performance.

Some meals can simply work.

A Tuesday dinner does not need a concept.

It does not need to express your values, maximize fourteen nutrients, use the basil before it dies, satisfy every person in the household equally, photograph well, cost almost nothing, create no dishes, take twelve minutes, and make you feel like someone who has their life together.

Sometimes dinner’s job is to be dinner.

That sounds obvious until you notice how many ridiculous expectations have attached themselves to food. Meals are supposed to be healthy, exciting, affordable, varied, homemade, quick, environmentally responsible, family-approved, culturally interesting, nutritionally optimized, and preferably produced from ingredients already in the house.

At some point, a bowl of pasta needs legal representation.

We are going to remove that pressure by replacing constant improvisation with useful defaults. Not rigid rules. Not a military food calendar. Defaults. Decisions made once that can be reused until they stop being useful. A short list of meals you genuinely eat. A grocery structure that supports those meals. Backup food for the days when your energy level is approximately potato. Simple methods for choosing among options without opening five apps and conducting a household referendum.

You will still decide what to eat.

You just will not need to reinvent civilization before every dinner.

And if the system works properly, something surprisingly pleasant happens: food becomes food again. You can enjoy cooking when you want to cook. You can try something new when you actually have the energy for novelty. You can order pizza because you chose pizza, not because you reached 8:42 p.m. after ninety minutes of indecision and finally surrendered to melted cheese.

There is an enormous difference between choosing convenience and being defeated by dinner.

By the end of this book, you should have a food routine flexible enough for real life and simple enough to survive contact with Tuesday. You will know what to do when you are tired, when nobody agrees, when the fridge is empty, when the plan fails, when you are bored with your usual meals, and when you simply do not want to cook.

No culinary reinvention required.

No twelve-week transformation.

No mandatory quinoa.

We have one recurring problem to solve:

You have to eat every day.

It would be nice if deciding how did not become your second job.

Chapter 1 - Dinner Is Not a Daily Creativity Contest

At 5:43 p.m., you receive the question.

“What do you want for dinner?”

It sounds harmless. Almost friendly. A normal sentence exchanged by civilized adults.

Unfortunately, your brain hears:

“Please review every meal available to humanity and select the optimal one based on health, cost, time, ingredients, current cravings, previous meals this week, everyone else’s preferences, and whether we still have that spinach.”

You say, “I don’t know.”

The other person says, “Me neither.”

Excellent.

The Department of Dinner has opened another productive session.

This is one of the biggest reasons food becomes mentally exhausting: we approach a routine problem as if it requires a fresh idea every time. Dinner happens almost every day, yet many households treat it like a surprise event.

“Oh no. Evening again.”

We would never run most of life this way. You do not wake up each morning and conduct extensive research into which toothpaste best represents your current emotional state. You probably use the same one until it runs out. You do not stand beside the washing machine considering whether tonight is finally the night to explore an exciting new philosophy of laundry.

Routine tasks survive because we automate enough of them.

Food often does not.

Instead, we preserve an odd expectation that meals should be varied enough to remain interesting, healthy enough to feel responsible, convenient enough to fit the schedule, inexpensive enough to avoid guilt, and appealing enough that nobody sighs when you announce them.

This makes dinner unnecessarily ambitious.

The first change is simple: stop requiring every meal to be a new decision.

You do not need infinite variety. You need a reliable collection of acceptable options.

That word matters: acceptable.

Not spectacular. Not restaurant-level. Not “everyone clapped when I brought it to the table.”

Acceptable means you like it, you can make it, the ingredients are reasonably easy to keep around, and eating it does not create a domestic crisis.

Most people already have several meals that fit this description. They simply do not treat them as a system.

Maybe yours include tacos, pasta with tomato sauce, grilled chicken and rice, scrambled eggs with toast, a stir-fry, quesadillas, soup, baked potatoes, sandwiches, burgers, a grain bowl, or frozen dumplings with vegetables. The specific meals do not matter. What matters is that they work repeatedly.

These are your default meals.

Defaults are not prison sentences. They are decisions you do not need to remake.

Your phone has default settings. Your car has a usual route home. You probably have a mug you reach for more often than the others despite owning twelve mugs for reasons nobody can fully explain.

Food deserves the same privilege.

A default meal says, “When I do not have a better idea, this is good enough.”

That sentence can save an absurd amount of mental energy.

The problem is that people often resist defaults because they confuse repetition with failure.

“We had tacos last week.”

Yes.

And?

You also slept last week. Nobody is demanding an exciting alternative.

There is no award for going thirty consecutive days without repeating a dinner.

Variety is useful. It can improve enjoyment, expose you to different foods, and help create a balanced diet. But variety does not require novelty every night. Those are different things.

If you rotate ten to fifteen dinners you actually like, your diet can feel varied without requiring daily invention. Add occasional new meals when you genuinely want them, and suddenly dinner stops behaving like a creative writing assignment.

A simple way to start is to make what I call the Reliable Ten.

Take a piece of paper, a note on your phone, or whichever digital system you will still remember exists tomorrow. Write down ten dinners that meet four conditions:

You genuinely eat them.

You can make them without unusual effort.

The ingredients are easy for you to buy or keep.

They work on normal weekdays.

Do not write aspirational meals.

This is important.

Do not include “roasted Mediterranean vegetable farro bowls” because you once saw a beautiful photograph and briefly became the person who owns farro.

Write what you actually eat.

If you make spaghetti regularly, spaghetti goes on the list.

If you make eggs and toast when life collapses slightly, that goes on the list.

If your family reliably eats rotisserie chicken, microwave rice, and a bagged salad, congratulations. That is a meal, not evidence in a criminal case.

Your Reliable Ten should reflect your real household, real schedule, real cooking ability, and real tolerance for cleanup.

Reality is surprisingly useful when designing systems for reality.

Once you have your list, the daily question changes.

Instead of:

“What should we eat?”

you ask:

“Which of these ten works tonight?”

That is a much smaller problem.

Ten options may still be too many on a tired Wednesday, so you can reduce the decision further by grouping them by effort.

For example:

Low effort:

eggs and toast;

quesadillas;

frozen dumplings and vegetables.

Medium effort:

pasta;

tacos;

stir-fry;

chicken and rice.

Higher effort:

homemade burgers;

baked salmon and potatoes;

chili.

Now dinner can be chosen partly by energy.

This is more practical than planning according to your ideal personality.

A surprising amount of meal frustration comes from creating plans for the person you expect to become by 6:00 p.m.

At 9:30 a.m., you are confident.

“Tonight I’ll make salmon, roasted vegetables, and that sauce.”

At 6:08 p.m., you are standing in the kitchen holding a piece of cheese.

The administration has changed.

This is why a good meal system needs to respect energy, not merely ingredients.

One dinner may be healthy, inexpensive, and sitting beautifully in your plan, but if it requires forty-five minutes of chopping on the evening you arrive home exhausted, it is not a useful plan.

Your plan should contain meals for different versions of you.

Competent You.

Busy You.

Tired You.

Extremely Tired You, who regards washing a cutting board as an unreasonable escalation.

That final category deserves more respect than it usually receives.

People often design food routines with one acceptable level of effort: proper cooking. Then, when they cannot meet that level, the entire system collapses and they order something.

A better system has layers.

Suppose your normal dinner is chicken, rice, and vegetables.

The full version might be chicken you season and cook, rice, and roasted vegetables.

The medium version might be pre-cooked chicken, microwave rice, and frozen vegetables.

The minimum version might be a rotisserie chicken sandwich and baby carrots.

Same basic function. Different energy requirement.

The point is not to pretend all meals are identical. The point is to stop making “perfect meal or total surrender” your only two options.

That is a terrible operating system.

It is especially dangerous when food becomes morally loaded.

People describe themselves as “good” because they cooked and “bad” because they ordered takeout. They “failed” because dinner was cereal. They “should have” made vegetables. They “weren’t disciplined.”

This adds emotional paperwork to an already annoying task.

Dinner does not need a performance review.

If a quick meal lets you eat, spend reasonably, and move on with your evening, it may be doing its job perfectly well.

The question is not, “Would a wellness influencer approve?”

The question is, “Does this meal work for my life often enough?”

That is a more useful standard.

There is another advantage to defaults: they make grocery shopping easier.

When you do not know what you normally eat, grocery shopping becomes a tour of possibilities. You walk through the store considering future meals with the optimism of someone who believes the coming week will contain much more energy than every previous week.

You buy kale.

You buy herbs.

You buy a squash.

You buy a special sauce.

You return home with $94 worth of ingredients and no clear dinner.

Three days later, the herbs have joined the compost program.

Defaults connect shopping to actual behavior. If tacos are a regular meal, keeping tortillas, salsa, beans, or whatever version you use makes sense. If pasta is a regular meal, pasta and sauce are not “boring.” They are infrastructure.

Nobody accuses a fire station of lacking imagination because it keeps fire extinguishers around.

Your kitchen can also prepare for predictable emergencies.

A good default system should include at least three meals that can be made almost without thinking. Ideally, these use ingredients that last a while or can be frozen.

For example:

pasta plus jarred sauce plus frozen vegetables;

eggs plus toast plus fruit;

frozen rice plus frozen vegetables plus a quick protein;

soup plus bread;

quesadillas plus canned beans;

frozen pizza plus salad.

These are not culinary achievements.

That is the beauty of them.

They exist to prevent the 7:38 p.m. crisis in which you are too hungry to decide what to eat and therefore spend twenty-six minutes scrolling delivery menus while rejecting every restaurant.

“Too expensive.”

“Too far.”

“Had that recently.”

“Reviews look weird.”

“Forty-five-minute delivery.”

“What even is Nashville hot cauliflower?”

Meanwhile, hunger is turning you into a less reasonable version of yourself.

Your backup meal should beat that situation.

It should require less decision-making than ordering food.

That is the standard.

If making the backup involves thawing meat, chopping six vegetables, and watching a twelve-minute tutorial, it is not backup food.

It is a project disguised as insurance.

A useful rule is this:

Every household needs at least one dinner that can be produced in fifteen minutes with almost no planning.

Not because fifteen-minute meals are morally superior, but because life regularly creates evenings when fifteen minutes is approximately what civilization has left.

Your first practical action is therefore not to create a monthly meal calendar.

Do not buy special containers.

Do not download an app.

Do not begin by watching “25 Meal Prep Hacks That Changed My Life,” because your evening may disappear and your meals will remain unchanged.

Make the Reliable Ten.

Then mark three of those meals as low-effort emergency options.

That is enough for now.

If ten meals feels impossible, start with five.

If five feels impossible, list the last five dinners you ate that you would willingly eat again.

There is your beginning.

You are not trying to become more creative with food.

You are trying to require creativity less often.

That is a much easier job.

And unlike the cucumber in your refrigerator, it has an actual future.

Chapter 2 - The Hidden Cost of Asking “What Do I Feel Like?”

You are hungry.

This seems like an excellent moment to decide what to eat.

It is not.

Being hungry while choosing dinner is like choosing a vacation while being chased by a bear. Technically, you can still compare options, but your standards have shifted.

At 3:00 p.m., you may calmly imagine grilled chicken, rice, and vegetables.

At 7:21 p.m., after a long day, your internal decision process becomes:

“Food.”

You open a delivery app.

Pizza looks good.

Then Thai.

Then burgers.

Then you remember groceries exist.

You close the app.

You open the refrigerator.

Nothing feels right.

You reopen the app.

This is not hunger anymore. This is a hostage negotiation.

The phrase “What do I feel like eating?” sounds reasonable because food is supposed to be enjoyable. And yes, preferences matter. Nobody wants a system that forces you to eat lentils on Thursday while staring sadly through a window because The Schedule Has Spoken.

But asking about feelings at every meal creates a problem: feelings are unstable, options are abundant, and hunger makes everything louder.

You may be choosing among dozens of restaurants, hundreds of menu items, everything in your pantry, everything in your refrigerator, and every meal you can theoretically cook.

Then we wonder why dinner feels tiring.

This is decision overload.

You do not need a psychology degree to understand it. If someone asks you to choose between two acceptable sandwiches, you can probably decide. If they give you a 19-page menu containing sandwiches, bowls, wraps, salads, pizzas, noodles, breakfast, desserts, seasonal specials, and something described only as “the experience,” lunch has become homework.

More options can feel like more freedom until you are expected to choose among them while tired.

Then freedom starts wearing a fake mustache and calling itself admin.

The same thing happens at home.

Your kitchen technically gives you many possible meals. Your phone gives you thousands more. The internet gives you recipes from every cuisine on Earth, including several dishes that require equipment you do not own and one ingredient available only from a family farm in northern Sicily.

Possibility is not the same as usefulness.

The solution is not to stop caring what you want.

It is to ask a better question.

Instead of:

“What do I feel like eating?”

try:

“What kind of meal would work tonight?”

That question introduces constraints.

Constraints are helpful.

We often treat them as limitations, but good constraints reduce noise. If you know dinner must be ready in twenty minutes, you have eliminated many options. If you know you want something warm, easy, and inexpensive, the field shrinks again.

You are no longer selecting from all food.

You are selecting from realistic food.

That is progress.

A simple decision sequence works well:

First: How much effort do I have?

Second: What needs to be used?

Third: Which default fits?

Fourth: Do I strongly want something else?

Notice the order.

Craving is still allowed. It simply does not run the entire company.

Imagine you come home tired.

Effort level: low.

You have tortillas and cheese that should be used.

Your default list includes quesadillas.

You do not strongly want anything else.

Decision made.

You have spent perhaps twenty seconds choosing dinner.

The old system may have involved staring into the refrigerator, asking another person what they want, rejecting their suggestion, checking a delivery app, remembering the tortillas, considering pasta, checking the refrigerator again, and eventually making quesadillas anyway.

Same dinner.

One version requires a minor decision.

The other requires a documentary series.

This is a recurring pattern in everyday life: we often know what the practical answer is relatively early, but continue searching in case a more exciting answer appears.

Sometimes it does.

Usually it is just another menu.

One reason this happens is that we secretly want dinner to improve the day.

If work was frustrating, traffic was awful, the weather was bad, and someone sent an email containing the phrase “gentle reminder,” food may suddenly acquire emotional responsibilities.

Dinner is no longer expected merely to feed you.

Dinner is now responsible for morale.

This is understandable.

Food is pleasurable. Comfort matters. There is nothing wrong with deliberately choosing something enjoyable after a difficult day.

The problem appears when every ordinary evening becomes a search for the meal that will make everything feel better.

That standard is hard for pasta to meet.

Sometimes you are not searching for food.

You are searching for a feeling.

Reward.

Relief.

Novelty.

Comfort.

The sensation that the day has finally become yours.

Again, none of these are wrong. The useful move is simply noticing what job you are assigning dinner.

If you want comfort, choose comfort intentionally.

If you want convenience, choose convenience intentionally.

If you are simply hungry, maybe do not require dinner to repair your relationship with capitalism.

This sounds ridiculous because it is ridiculous.

It is also common.

People often spend more money or more time on food when they are exhausted because the meal has become compensation for the day.

“I deserve something good.”

Fair.

But “something good” does not automatically require $47 of delivery food and a service fee with the confidence of a mortgage payment.

You can build comfort meals into your defaults too.

Maybe grilled cheese and tomato soup is comfort food for you.

Maybe it is ramen with an egg.

Maybe it is mashed potatoes, pasta, curry, a burrito bowl, or cereal eaten while watching something undemanding.

The specific food is yours.

The useful principle is to know your comfort options before the bad day arrives.

Otherwise the bad day becomes your purchasing department.

Another issue with “What do I feel like?” is that the answer changes while you are looking.

At first, sushi sounds good.

Then you see pizza.

Now pizza sounds better.

Then a burger appears.

Suddenly you remember fries.

You are not discovering a deeply held preference. You are reacting to images.

This is why browsing food apps can create appetite rather than merely satisfy it. You may begin with a vague hunger and end with a highly specific desire for something you had not considered two minutes earlier.

Your eyes have joined the planning committee.

A useful rule for delivery apps is to decide the category before opening the app.

Not the exact restaurant.

Just the category.

For example: