Vibe thinking

A few weeks ago I asked an AI model a question I’d been chewing on for days, and it returned a better-argued answer than I would have produced. I caught myself nodding along. Then I caught the nodding itself, and a stranger question arrived: whose thought was I about to agree with? I had a conclusion in my hands, fluent, structured, quotable. What I couldn’t find anywhere was the part where I had thought it.

We named the software version of this. Vibe coding: a vague prompt produces something, the something works, the loop repeats. The thinking version happens millions of times a day and has no name yet, so let me give it one. Vibe thinking: a vague question produces an opinion, the opinion is fluent, the loop repeats. People are shipping conclusions this way, into meetings and into decisions, and the promise underneath is the same one: thinking is free now, so having positions is for everyone.

Part of that is true, and I won’t mourn it. The production of arguments really is close to free, and it’s permanent. Anyone can now hear the strongest case for and against almost anything in minutes. That’s a genuine gift, and the gatekeeping version of this essay, where thinking is reserved for people who suffered for it, would be wrong.

Here’s the part that’s false. What makes a thought yours is the question you brought, the checking you did against what you know, and whether you’d answer for the conclusion when it costs something. A vague question carries none of that. It has no stake, no criteria for being wrong, nothing the answer must survive. An opinion you can’t be wrong about isn’t a thought you had. It’s a thought you’re holding.

And I know the difference from the inside, because I’ve shipped vibe thoughts. Some of them got likes.

The cost surfaces the same way it does in software, at contact. Software meets a change, another user, time. A thought meets a disagreement, a decision, a consequence. That’s when the vibe thinker discovers what’s missing: challenged on the conclusion, they can’t walk anyone through it, because they never walked to it. They can only ask again. The defense prompt gets longer each round, because the missing reasoning is being paid for in installments.

There’s a version that goes the other way, and it’s how I spend most of my working days now. Thinking with the machine instead of asking it to think. The difference is small to describe and enormous in practice: I bring the question, I push back on the answer, I check it against what I’ve built and seen, and the conclusion that survives gets my name on it. The machine makes me faster and sometimes proves me wrong, which is the point. What it never does in that mode is think in my place, because the verification seat stays occupied.

So the split from software arrives here too. Opinions nobody has to answer for, dinner-table takes, idle curiosity: vibe freely, it costs nothing and gives a lot. Conclusions someone has to answer for, the decision your team executes, the claim you publish, the advice someone acts on: those need a thinker in the loop.

The machines made arguments free. What they made scarce is people who know which conclusions are theirs. The test is simple and slightly uncomfortable, and I use it on myself before anything ships: can I defend this with the machine off? When the answer is no, I didn’t think it, I’m only holding it.