My Wife Thinks I'm Addicted to AI

I was the kid who never played video games. My friends would disappear into consoles for entire weekends and I'd sit on the couch watching, bored and a little judgmental. Staring at a screen for hours, building nothing real. I tried a few times, was terrible at most of them, and decided games weren't for me. That became part of my identity for decades.

Now I'm 40 years old, running three AI coding agents simultaneously across two monitors, and I haven't moved from my chair in four hours.

A few weeks ago my wife and I were making dinner. I told her I was in a good mood. She didn't look up from what she was chopping.

It's not because of me. It's not because of the weather. It's because you're addicted to vibe coding.

My first instinct was to push back. Addicted felt too strong. Addictions are destructive. This was productive, creative, useful. She just looked at me. She was right, of course. She usually is about the things I'm slowest to admit.

For fifteen years as a CEO, I context-switched every thirty minutes. Meeting to meeting, decision to decision, fire to fire. I have ADHD, and the constant switching trained my attention span down to something that could barely hold a single thought for the length of a conversation. My wife and I would start a film and twenty minutes in I'd be on my phone. Books that used to take days started taking weeks. I stopped finishing most of them.

Vibe coding broke that pattern. Three hours pass and I don't check my phone, don't open a browser tab, don't drift. For someone who hasn't sustained attention on anything for that long in fifteen years, that fact alone is worth sitting with.

There's a reason it works on my brain when nothing else has. The challenge level never holds still. One moment I'm describing a feature in plain language and watching it appear on screen, and the feeling is generous, almost effortless. Then an agent rewrites a component I didn't ask it to touch. Two agents start editing the same file and neither one knows the other exists. The model I ask for help cheerfully tells me everything looks fine while the screen is full of red. I'll realize I've been leaning forward in my chair for forty minutes, jaw tight, shoulders up around my ears, bargaining with a machine. Then something clicks, the feature works, and my whole body releases. Easy, hard, easy, hard, impossible, breakthrough. My brain never gets the chance to wander because the ground keeps moving.

Gamers know this feeling. Game designers call it the flow channel, that narrow band between frustration and boredom where you're stretched just past your ability but not so far that you quit. The entire gaming industry is built on engineering that state. Vibe coding does it by accident.

But in games, the rewards are virtual. In vibe coding, the rewards are real and they compound. When I showed my wife the photo sharing page I'd built for our wedding, she went quiet for a second, then started scrolling through it slowly. You made this? That landed somewhere no level-up screen has ever reached. And when a context window expires and I lose four hours of shared understanding with an agent, the frustration is just as real. The thing I'm building either works for actual people or it doesn't.

Here's the case I keep making to myself, and I think I actually believe it. Every other addiction I can name narrows your life. Less money, less health, less time, less presence with the people next to you. This one keeps producing things. Tools that work. Problems I've solved for people who needed them solved. Skills I didn't have a year ago. A version of myself that can take an idea and make it real, which after fifteen years on the wrong side of the wall is not a small thing. If the output is genuinely useful, is the compulsion still a problem?

My wife would say yes. She'd say I disappear into it, that I lose hours I meant to spend elsewhere, that the pull of one more agent run at 4am has a texture she recognizes even if I won't name it. And she's watching from close enough to see what I can't.

There are 3.4 billion gamers on the planet. Nearly half of humanity. It took four decades to get there, and all that time the loop was attached to virtual outcomes that reset when you turn off the console. Vibe coding is the same loop attached to real things. The nurse building a patient tracking system for her ward. The teacher building an attendance tool that works the way her classroom actually does. The restaurant owner automating her scheduling because she's the only one who understands the problem.

Every Friday my AI studio team does a show-and-tell, and I watch it happen in real time. Someone shows a tool they built that week, eyes bright, talking too fast, exactly the way I talk to my wife at 8am when something finally works. The pull has them too. It's not just me. This thing is spreading in a way that nobody is tracking because it doesn't look like adoption metrics or revenue growth. It looks like people who can't stop building.

The variable nobody is modeling is the addictiveness of building itself. Not the capability curve, not the cost of tokens, not the labor displacement forecasts. The pull. The thing that keeps someone at their desk not because they have to be there but because they can't leave. Gaming proved that half the planet will show up for a well-designed loop. What happens when that loop is attached to solving real problems, and the only barrier to entry is a browser?

I genuinely don't know whether I'm building something or being consumed by it. My wife is keeping score. I suspect she'll tell me before I figure it out myself.