The Fastest Way to Be Done

The fastest way to be done with dinner is to not clean the kitchen.

If you don’t clean the kitchen, a mess builds up. The pots and pans pile in the sink. The spoon you need is somewhere under something else. You may have to scrape dried spaghetti from last Tuesday or rinse peanut butter from a knife before you can use it. But eventually you will find what you need, and dinner will happen.

And still, the fastest way to be done with dinner is to not clean the kitchen.

That’s what makes this hard. You can always be done faster today if you don’t clean today. The time spent wiping the counter or putting the knife back is time not spent eating.

This is why skipping cleanup keeps winning. What’s measured is that dinner was made. The outcome. The visible result. Not how much effort it took to get there, and not how much harder it made the next dinner.

The same thing happens when decisions are made under pressure. There isn’t enough time. There isn’t enough understanding yet. You don’t have all the data, and you may not even know what the real problem is. But something has to ship, so choices are made with what’s available. Structure bends a little. Cleanup waits.

And it works. Dinner happens. Features ship.

If you cleaned the kitchen after dinner every day, the total time spent making dinner over a year would be far less. But that advantage only appears over time, and time over time is rarely what’s being measured. The mess doesn’t announce itself. It accumulates quietly and shows up later as friction.

At some point, more effort goes into working around the kitchen than into cooking. So things get rearranged. Shelves are moved. Tools are reorganized. The goal is to make tomorrow easier.

In software, this is when code gets refactored. In organizations, this is when teams and responsibilities get restructured. The kitchen is rearranged to make tomorrow feel possible.

This is what happens when we optimize for now, when we move before understanding has had time to catch up. If no one intervenes, things settle into whatever feels fastest.

Over time, you begin to notice this pattern. You see how small compromises accumulate. You feel when a name no longer fits, or when a boundary has grown heavier than it needs to be.

Over time, you realize software engineering is a craft. You rename things while they are still small. You adjust structure before it stiffens. You clean a little while the system is still warm.

A good chef doesn’t wait until the end of the night to discover the kitchen is unusable. They wipe the board between steps and reset the counter before reaching for the next ingredient. It doesn’t look dramatic. It simply keeps cooking straightforward.

And still, the fastest way to be done with dinner is to not clean the kitchen.

Eventually the way you move through the kitchen becomes the kind of cook you are — and the kind your future self has to work with.