When My Father Cooked

Some family routines become visible only when the person who usually holds them together is not there.

In June 2010, I wrote a short entry about my father cooking.

The event, as I described it, had a predictable ending:

after the meal, he handed the kitchen over to his son so the dishes could be washed.

Everyone did the part they preferred.

That was the joke.

Then I added another detail later.

When my mother was away, my father did not immediately start cooking from scratch.

For the first three days, he reheated the food she had prepared in advance.

Only after that reserve ran out did cooking become unavoidable.

It was a tiny domestic observation.

But it says a lot about how families quietly organize themselves.

In most homes, nobody sits down and writes a systems diagram.

There is no formal process document.

No flowchart.

No service-level agreement.

No ticketing system.

And yet the house runs.

Food appears.

Dishes disappear.

Laundry moves through stages.

Bills get paid.

Things are found.

Things are bought before they run out.

Someone remembers appointments.

Someone notices that the refrigerator is nearly empty.

Someone knows where the clean towels are.

Someone knows which cupboard contains the thing nobody else can find.

Domestic life is a system.

Most of its infrastructure is invisible.

That invisibility becomes obvious when one person leaves.

Then the system begins exposing its dependencies.

My mother’s absence did not mean immediate catastrophe.

She had already prepared food.

That is important.

The system had redundancy.

For three days.

There were reserves.

Pre-cooked meals.

A buffer.

Then the buffer was consumed.

The next stage activated.

My father cooked.

And after he cooked, I washed the dishes.

At the time, this looked like a family joke.

Now it looks like a primitive but perfectly functional division of labor.

One person cooks.

Another cleans.

Nobody has to love every task.

The house still works.

That line in the old entry—

everyone doing the part they like—

was playful, but there is something useful inside it.

Work does not always need to be divided symmetrically.

It needs to be divided fairly enough and clearly enough that the system does not depend on one exhausted person doing everything.

That is a much harder problem than it sounds.

Families often inherit task divisions without discussing them.

Who cooks?

Who shops?

Who cleans?

Who repairs?

Who remembers birthdays?

Who organizes visits?

Who takes care of paperwork?

The answers may come from habit rather than choice.

Habit is powerful because once a task is consistently handled by someone, everyone else stops noticing it.

This is true at home and at work.

A task becomes invisible precisely because it is reliably completed.

Nobody celebrates the fact that dinner appeared.

Dinner always appears.

Nobody asks how clean clothes reached the drawer.

They are simply there.

The work becomes visible when it stops.

This is one reason domestic labor is easy to underestimate.

Successful maintenance produces absence.

No crisis.

No mess.

No shortage.

No forgotten appointment.

The result of good maintenance often looks like nothing happened.

That makes it hard to value.

Engineers know this problem too.

When infrastructure works, nobody notices.

When a server stays online for three years, nobody applauds each morning.

When backups work, the achievement is mostly invisible.

When a system is secure, the result is that something bad did not happen.

Maintenance has poor drama.

Failure has excellent drama.

Homes are the same.

A meal that arrives normally is ordinary.

A meal that fails to exist becomes an event.

My father’s three-day strategy was actually very sensible.

Why cook immediately if prepared food is already there?

Use inventory first.

Reduce waste.

Delay unnecessary work.

This was not necessarily strategic optimization.

The archive does not say.

Maybe he simply preferred reheating to cooking.

That is probably the safer interpretation.

Still, the behavior was efficient.

There is something funny in the way families develop fallback modes.

Normal mode:

Mother cooks.

Exception mode, days one through three:

Father reheats.

Exception mode, after prepared food is exhausted:

Father cooks.

Cleanup phase:

Son receives kitchen.

System restored.

You could almost write it as pseudocode.

That would probably ruin the memory.

The important part is that everybody understood the logic without needing to discuss it.

Families build protocols through repetition.

“Protocol” sounds too technical for home life.

But think about it.

Who answers the door?

Who drives on long trips?

Who handles strangers?

Who calls the repairman?

Who checks whether the stove is off?

Who gets up when something makes a noise at night?

Every household has default behaviors.

Some are explicit.

Most are not.

Children learn them by living inside them.

Only later do we realize that another family may operate completely differently.

What seemed normal was local.

This is one of the strange discoveries of adulthood.

You visit another home.

Their meal times are different.

Their rules about shoes are different.

Who cooks is different.

How people speak at the table is different.

How much food is prepared is different.

What happens after dinner is different.

Nobody is necessarily wrong.

You are looking at another operating system.

Same hardware class.

Different configuration.

The entry about my father cooking was written from the perspective of a son who noticed the comedy of the handoff.

He cooks.

I wash.

Fair enough.

But the later detail about my mother preparing food before leaving changes the story slightly.

Her work was still present even in her absence.

For three days, she was not physically there, but her preparation continued feeding the household.

That is a form of invisible presence.

People often remain inside routines after they leave the room.

A parent travels, but has prepared everything.

A colleague goes on vacation, but leaves notes.

A teacher is absent, but the lesson plan remains.

Good preparation extends presence.

The danger is that this can also become an expectation.

The person leaving may feel responsible for preventing every inconvenience caused by their absence.

That is not always fair.

If one adult cannot leave home without preparing three days of food for other adults, the household may have a dependency problem.

I do not know enough from the entry to say that was our situation.

The source only tells me that my mother had prepared food and that my father reheated it for the first three days.

So I should not turn one joke into a family diagnosis.

But the broader question is worth asking.

A resilient household should be able to survive the temporary absence of any one person.

Not perfectly.

But competently.

People should know enough to function.

Cook something.

Find things.

Pay for things.

Clean up.

Handle a problem.

Independence inside a family is not the opposite of closeness.

It protects closeness from turning into helplessness.

This lesson becomes especially clear when young adults first live alone.

Tasks that were previously background suddenly become visible.

There is no magic.

The trash does not take itself out.

The refrigerator does not refill.

Toilet paper does not reproduce.

Clean shirts do not migrate into wardrobes.

A person did those things.

Or several people did.

Living alone is partly the discovery of hidden labor.

You begin calculating effort differently.

A meal is not only eating.

It includes deciding what to eat.

Buying ingredients.

Preparing them.

Cooking.

Cleaning.

Storing leftovers.

The activity has a tail.

This is why the line about handing the kitchen to me after dinner is so accurate.

Cooking is not complete when food reaches the table.

Someone still has to deal with the aftermath.

The kitchen remembers.

Dirty plates.

Pots.

Oil.

Crumbs.

Counters.

A meal produces evidence.

Many arguments about domestic work come from counting only visible central tasks and ignoring the tail.

“I cooked.”

Yes.

Who cleaned?

“I bought the groceries.”

Who made the list?

“I did the laundry.”

Who folded it?

Systems work is full of tails.

So is housework.

A task has preparation, execution, and cleanup.

People often volunteer for the interesting middle and disappear before the final phase.

My father apparently did not disappear.

He delegated.

That is management.

Perhaps the first managerial structure I experienced was not at work after all.

The kitchen had a clear chain of command.

The cook had authority to appoint a dishwasher.

I was the dishwasher.

Promotion opportunities were limited.

At least the assignment was temporary.

There is warmth in this memory because nothing dramatic happened.

My mother was away.

Food existed.

My father managed.

I helped.

The house continued.

That ordinary continuity is what family life mostly consists of.

Not speeches.

Not major events.

Small transfers of responsibility.

Who is doing dinner?

You.

Fine.

Who is washing these?

You.

Fine.

Tomorrow?

We’ll see.

The mundane parts of family life rarely seem worth recording when they happen.

That is why I like finding them in old archives.

Major events survive naturally.

Birthdays.

Graduations.

Trips.

Deaths.

Weddings.

Jobs.

But ordinary cooperation disappears unless somebody writes down the joke.

A short entry about washing dishes can preserve more domestic atmosphere than a formal family photograph.

Photographs show people.

Small memories show how they lived together.

The phrase “my father cooking” contains several generations of expectation too.

In 2010 Turkey, as in many places, domestic roles were still strongly gendered in many families.

They still are in many homes.

So the event was funny partly because it was treated as an exception:

father cooking because mother was away.

That framing deserves to be noticed.

Cooking itself is not gendered.

Cleaning is not gendered.

Household competence is not gendered.

But families inherit cultural patterns, and those patterns become jokes because everyone recognizes them.

The useful thing is not pretending those patterns never existed.

It is seeing them clearly enough to choose differently when needed.

Maybe in one family, one person genuinely loves cooking and another hates it.

Fine.

Preference is a reasonable basis for division.

Gender is a much weaker one.

The ideal household is not one where every task is divided mathematically in half.

It is one where the people involved can see the work, value it, negotiate it, and cover for one another.

That last part matters most.

Cover for one another.

My mother was gone.

My father covered the cooking.

I covered the dishes.

That is what families do at their best.

Roles are stable until they need to become flexible.

The ability to switch roles is resilience.

This applies beyond households.

Teams fail when knowledge is concentrated in one person.

If only one employee can deploy the software, there is a problem.

If only one person knows the password, there is a problem.

If only one person can explain the customer setup, there is a problem.

If only one person in a household can make food, there is also a problem.

Redundancy sounds inefficient until the primary person is unavailable.

Then redundancy becomes survival.

The family version is gentler.

Nobody starves because one person is gone for a few days.

But the principle is the same.

Know enough of one another’s work to keep life moving.

There is also a small lesson in the three-day buffer.

Prepared food buys time.

Time is one of the most useful things preparation can create.

A backup buys time.

Savings buy time.

Documentation buys time.

Meal prep buys time.

A charged battery buys time.

A full tank buys time.

Many forms of preparedness are simply ways of preventing immediate decisions.

You do not need to solve the problem now because past-you already did some of the work.

My mother had apparently done that.

For three days, future household members benefited from earlier effort.

Then the future arrived and asked my father to cook.

Eventually every buffer ends.

That is another systems lesson.

Caches empty.

Batteries drain.

Savings run down.

Prepared meals get eaten.

A buffer is not a permanent solution.

It gives you space to transition.

If you use the space well, great.

If you only postpone adaptation, the same problem appears later.

In our case, adaptation was simple.

Cook.

Then hand the kitchen to the son.

I keep returning to that handoff because it is the perfect ending.

There is no hero.

No helpless father.

No saintly mother.

No oppressed son.

Just a family redistributing small work.

The younger me saw the joke in it.

The older me sees the structure.

Both are true.

Maybe that is why these old entries are useful.

At the time, I wrote what made me laugh.

Years later, the same sentence reveals what I had normalized.

Who did what.

Who was absent.

Who adapted.

Which work was visible.

Which work stayed invisible even when the person doing it was away.

The archive does not preserve what my father cooked.

That would be a nice detail.

It is not there.

So I will not invent a pot of beans, pasta, eggs, or some heroic stew.

All I know is that after the prepared food ran out, he cooked.

And afterward, the kitchen became my problem.

That is enough.

Sometimes a family memory needs no recipe.

Only roles.

Mother leaves food.

Father reheats.

Father eventually cooks.

Son washes dishes.

Everyone survives.

The house continues.

That is domestic engineering in its simplest form.