Connected to the System
and the dinner that went cold without me

It was late evening. I was at my laptop, working on a time-tracking system for a delivery organization.

From the kitchen, I heard a plate land hard on the table. Then my wife's voice, flat and cold: "come eat."

I knew what it meant.

I stayed anyway.

In delivery operations, time is the main variable. You track it, measure it, optimize it. Every minute matters. I understood this well enough to be improving the system at eleven in the evening.

What I was not tracking was the other time. The time passing at the kitchen table. The dinner going cold. The evening that ended before I joined it.

When I finally walked over, the plate was cold. Everyone had already eaten. My wife said nothing.

I sat down and told myself: I am doing this for the family. This work matters. There is a bigger goal here.

It sounded reasonable.

It was also partly an excuse. I knew it in the same moment I said it.

That is the part that stays with me.

Not the cold dinner. Not even the silence.

The fact that I could see what was happening clearly, name the price accurately, feel the guilt in real time, and still not stop. And that the story I told myself to stay was not a lie exactly. It was a half-truth used as a lock.

This is what capture looks like from the inside.

Not an absence of awareness. The opposite: full awareness, and a narrative ready to justify continuing anyway.

There is something specific about development work that makes the exit point hard to find. There is always one more thing. One more function. One more pass. The end feels close, which makes stopping feel wasteful.

AI makes this worse. When you are working with an AI tool, the next improvement is always one prompt away. The loop has no natural seam. The system is always ready to continue if you are.

It will never tell you the dinner is getting cold.

Across the organizations I work with, I see the same pattern at a different scale.

The project that has been almost done for two quarters. The initiative that keeps running because stopping now would mean admitting the sunk cost. The team lead who stays on a call thirty minutes too long because leaving feels like abandoning the thread.

The justification is always available. The goal is real. The commitment is genuine. And the price is paid somewhere else, by someone who already ate without you.

I am not arguing against late evenings or hard work.

I am saying: watch the story you tell yourself to stay connected five minutes longer. Not because the story is false. Because it is good enough to be used as a reason when the real reason is that you simply cannot find the exit.

The awareness of the price is not the same as paying it differently.