Wednesday night, 9:40pm. I'd been on calls since eight in the morning, I had two hundred unread emails, and there was a spreadsheet open on my laptop that needed a decision I didn't want to make. So I closed the laptop, walked into the kitchen, and spent thirty-five minutes making a pan sauce for one piece of chicken.
Nobody was coming over. Nobody needed feeding but me. I could have eaten cereal standing up over the sink like a raccoon and slept forty minutes earlier.
I made the sauce. I make the sauce every time. And I've finally figured out why.
Cooking Is the Only Thing I Do That Ends.
Everything else in my life is a rolling deadline. A telecom company is never done — there's always more network, more coverage, more uptime to protect. School's never done. The podcast's never done. Every business I've started is a machine that eats attention and asks for more in the morning. I've built a life out of things that never finish.
Dinner finishes. Dinner finishes in forty minutes, and then you eat it, and then it's gone, and there's nothing left to iterate on. There's no version two of Wednesday's chicken. There's no roadmap. Nobody schedules a retro on it.
Do you know how rare that is? A task with an actual ending? I chase that feeling all day and never get it. I get it standing at a stove for the price of a shallot.
I've built a life out of things that never finish. Dinner finishes.
My Phone Can't Follow Me in There.
Here's the part I didn't expect: cooking is the only activity I've found where my hands are too busy and too filthy to hold a phone.
That's not a small thing. I've tried meditating. I've tried the walks. I've tried the whole ritual where you put the phone in another room and pretend you don't know exactly which room. It never works, because none of it physically prevents me. But you cannot check a notification with raw chicken on your fingers. The medium enforces the discipline. I don't have to be strong — I just have to be greasy.
And for those forty minutes my brain does something it doesn't do at any other point in the day: one thing at a time. Onions first. Then garlic, but not too early, because garlic burns and then dinner tastes like regret. Deglaze. Reduce. Off the heat before the butter, always off the heat before the butter. It's a sequence with real physical consequences, and my brain — which spends all day holding nine open loops at once — is genuinely relieved to only be responsible for one pan.
People call that mindfulness. I call it the only time all day nobody can reach me.
I'm Not a Good Cook. I'm a Repetitive One.
Let me kill any impression that I know what I'm doing. I am not a good cook. I have maybe nine dishes. I make those nine dishes on a loop like a bar band playing covers, and I've made some of them a hundred times.
That's the whole trick, by the way. Not talent — repetition. Pick six things you actually want to eat and make them until you can do them while thinking about something else entirely. That's it. That's the entire skill. Nobody needs a hundred recipes. A hundred recipes is how you end up ordering delivery at 10pm because deciding was harder than cooking.
What I did spend money on is a good knife, a heavy pan, and salt that isn't garbage. Three things. Everything else in my kitchen is whatever was on sale. Anybody who tells you they need a sixteen-piece set is decorating, not cooking.
Dishes in my entire rotation. I've made some of them over a hundred times. I get better at those nine instead of worse at forty.
Cooking for One Is Not Sad.
I need to defend this, because people get weird about it.
There's this assumption that real cooking requires an audience. That a nice meal made for yourself is somehow a performance without a crowd — a little tragic, faintly delusional. Like you're setting a table for a guest who isn't coming.
That's backwards. Cooking for other people is generous, and I love doing it, but it's also work. There's a clock. There's a standard. You're managing timing and preferences and whether somebody's going to notice you oversalted the vegetables. Cooking for yourself has none of that. Nobody's grading it. If it's bad, one guy is mildly disappointed and he already forgave you.
And it's the clearest signal I know that I'm not treating myself like an afterthought. It'd be very easy to be the guy who runs five things, gets on the President's List, builds the network, keeps every promise to everybody else — and then eats cold rice out of a container standing up at 11pm because he wasn't worth the pan. I've been that guy. That guy is not efficient. That guy is just neglecting somebody quietly and calling it discipline.
Eating like an afterthought isn't efficiency. It's neglecting somebody quietly and calling it discipline.
The Real Reason, Probably.
I think it's about control, and I think that's fine.
Most of my day is spent on outcomes I can influence but not decide. Customers do what customers do. Vendors miss dates. Markets move. You can be right about everything and still lose the quarter. That's the job, and I signed up for it, and most days I love it.
But a pan does exactly what physics says it will. Heat does what heat does. If I do the steps correctly, the thing comes out correctly — every single time, with no politics involved. There is not one other arena in my life with that property. Forty minutes a night where effort maps directly to result and nobody can renegotiate the terms.
So no, I don't need a reason for the pan sauce. It's not about the chicken. It never was.
It's the only forty minutes all day that actually behave.