At 6:17 on a Tuesday, I am color-coding my week. My laptop screen glows against the gray kitchen light. Blue blocks for deep work. Green for exercise. A thin yellow sliver I have labeled “relationship maintenance.”
My partner, Maya, sets her coffee down across from me. She does not look at the screen. She says, “I miss you.”
I do not look up. “Sunday,” I say. “We can block three hours. Quality time. No phones.”
She is quiet. The refrigerator hums. Then she stands and walks to the shower.
For months, I have been proud of this system. I track sleep, heart rate, caffeine intake, creative output, social touchpoints. I am a software engineer; my job is to make systems efficient, and I have decided that I am a system. I read books about habit formation. I measure my reading in pages per hour. I schedule grief for the thirty minutes after therapy. I am, by every metric I can think of, doing well.
But that Tuesday night, Maya sits on the edge of our bed and tells me she feels like an item on my to-do list. I feel a hot spike of defensiveness. “That is not fair,” I say. “I am being intentional. I am making time for us.”
She shakes her head. “You are not making time. You are allocating it.”
Her words hang in the room. I want to argue. I want to show her the spreadsheet, prove that she occupies 8.7 percent of my waking hours. Instead I feel something cold move behind my ribs. I do not have a name for it yet.
The next morning, I double down. If the problem is that she feels like a task, I will optimize the task. I create a shared calendar. I add a “connection ritual” before bed. I draft a document called “Our Relationship Operating Principles.” I send it to her with a note: “Let’s iterate.”
She does not reply.
That is the moment I begin to crack. The system I built to make me better is starting to feel like a cage. Every conversation becomes an input. Every emotion becomes a variable. My mother calls, and I time the call for exactly the length recommended by an article on “parental maintenance.” My friend texts about his divorce, and I send him a bulleted list of therapists and action items. He thanks me, but the conversation ends there.
One Saturday I am standing in the produce aisle, comparing two avocados according to cost, ripeness, and projected waste, when I realize I am calculating the value of a piece of fruit as if it were a stock. My chest tightens. I put both avocados down. I walk out of the store without buying anything.
I sit in my car for a long time. The dashboard clock says 2:43. I think of my father, who called last week to say he is lonely. I gave him three hobby suggestions and a link to a meetup app. I did not ask what loneliness feels like in his body. I did not just stay on the line.
Something is wrong. My mind is very good at solving problems. But I am starting to suspect that not everything is a problem.
Then I remember a philosophy class I slept through in college. The professor is talking about Immanuel Kant. I remember only one phrase: reason is not merely a tool. At the time I thought it was obvious and useless. Of course reason is more than a tool. It is also a tool.
I go back and read. And the reading stops me.
Kant argues that if reason were only a means to get what we want—better health, more money, more love, more status—then machines would eventually do it better. A calculator does not hesitate. An algorithm does not tire. If intelligence is just optimization, we are building our own obsolescence.
But Kant says human reason does something stranger. It asks whether the things we want are worth wanting. It demands that we treat people as ends in themselves, not as instruments. It gives us the ability—and the burden—to choose principles that we would want everyone to live by.
I read that and feel the cold thing behind my ribs thaw into something sharp and alive. For months I have been using my reason to get more of what I thought I wanted: productivity, health, love on schedule. I have been treating Maya, my friends, my father, even myself as objects to be managed. I have mistaken efficiency for care.
The surprising thing is how long Kant kept to his routines. Every day at 3:30 p.m., he walked so faithfully through Königsberg that neighbors reportedly set their clocks by him. Yet he also wrote that a will guided only by habit or self-interest is not truly free. Routine can serve reason, but reason must judge the routine.
I sit with that for days.
I do not throw away every system. I still use a calendar. I still like a good spreadsheet. But I start asking different questions. Not “How can I fit this person into my life?” but “What do I owe this person?” Not “What is the optimal response?” but “What is the right response?”
On a Sunday evening, I close the laptop. I tell Maya I am sorry. I do not show her a document. I do not propose a new ritual. I ask her to tell me what she needs, and I try to listen without already forming the fix.
It is harder than any optimization problem I have ever solved. My mind keeps wanting to interrupt with solutions. But I stay quiet. Her voice cracks. She says she just wants to know I am there, even when there is nothing to solve.
I feel tears in my throat. I do not have a metric for this.
That night I delete the “relationship maintenance” block. I leave the cell empty. The empty space scares me. It also feels like a door.
Intelligence, I am learning, is not the same as winning. It is not the fastest route from A to B. It is the courage to ask whether B is worth reaching, and who gets used up along the way. My reason is not a machine I can sharpen until it outperforms the world. It is the part of me that chooses to be present, to be kind, to be accountable. And that choice is never efficient.
Some nights I still reach for the spreadsheet. Some mornings I still try to measure my worth in output. But now, when I sit across from Maya with my coffee cooling, I look at her instead of the screen. I let the silence be long. I let the moment be useless.
And for the first time in a year, she smiles at me like I am really here.
