Why the pull toward variety isn't a character flaw, a betrayal, or breaking news, and what twenty-five years of staring at stubborn systems taught me about keeping desire alive for the long haul.

She's right, by the way. And the reason she's right has almost nothing to do with his wife.

What he's describing isn't a scandal, and it certainly isn't news. It's the oldest background process in the human operating system, and it has been running, uninterrupted, for roughly two and a half million years.

I spend my days looking at systems that refuse to behave. So allow me to explain this one the way I'd explain any stubborn legacy service that somehow still can't be deprecated.

It's firmware, not a flaw

The craving for novelty is legacy hardware. It was optimised for a problem you no longer have: surviving and reproducing in a world where most children didn't make it and the gene pool needed all the help it could get. That code shipped a very long time ago. It is still in production. You cannot uninstall it, you cannot patch it out, and no amount of love for your partner will make the process quietly exit.

Here's the part the panic-posts always miss: feeling the craving is not a betrayal. It's the firmware doing exactly what it was built to do. Wanting variety is simply being a mammal with a pulse. Acting on it is a choice, and an entirely different conversation. The feeling is biology. What you do with it is character.

So let's retire one phrase right now: having more than one desire isn't deception. It's a survival instinct wearing a very old uniform.

The framework is the least interesting part

A while ago I wrote about what a Java system handling a million transactions per second actually looks like in production. The whole point of that piece was one line: the framework is the least interesting part. What you build around it is everything.

Relationships run on precisely the same principle.

The initial attraction (the spark, the chemistry, the thing that made you notice each other across a room) is the framework. It's necessary. It is also, on its own, completely insufficient. Spark has never kept anyone married. The architecture you build around it does: the rituals, the attention, the stubborn willingness to keep discovering a person you assume you've already finished reading.

Novelty isn't "out there." You generate it.

Here's the reframe that actually changes things. The craving feels like it points at other people. It doesn't. It points at a missing input: novelty. And novelty is not a resource you have to source externally. It's something you manufacture in-house, from materials you already own.

The brain rewards new. So give it new, from the relationship you're already in:

None of this carries an age limit. Desire doesn't expire on a printed date. It fades from neglect, not from time. People rediscover each other in their sixties all the time, not because their biology changed, but because they decided to keep showing up with curiosity instead of assuming the manual had been fully read.

This one's for both of you

This is not a lecture aimed at one guilty party. It takes two.

Intimacy isn't a phase of courtship that expires the moment the paperwork is signed. It's a practice. And like every practice worth anything, it rewards the people who keep turning up.

A word on dolphins (you're in good company)

So no, you're not broken for wanting more. You were built for more. The trick is realising that "more" was always available inside the thing you already have. You just have to keep building around it.