What is Vibe Computing?

That “how” can be almost anything. Clicking through an app. Writing a function. Moving a hundred files. Pulling numbers out of a database. Booking a meeting. Or all of it at once, stitched into a single task. You state the result. The machine handles the operation.

We’ve been building this way since late 2025, before the idea had a name. The name came later, from our founder, Philip Alm, who coined “vibe computing” on Veckans AI, the Swedish AI podcast hosted by Magnus Paues. You can hear the clip here. He wasn’t inventing a concept on the spot. He was naming something himself and Emil Wagman had been talking about for months, because we think it’s the biggest shift in how people use computers since the graphical interface.

Here’s what it actually means.

The deal we made with computers

For about fifty years, using a computer meant learning to think like one.

You wanted to move a file, so you learned where Finder kept it. You wanted a chart, so you hunted for the chart button in Excel and learned which menu it hid behind. You wanted code to run, so you typed it out, semicolons and all. Every single thing you did was a small act of translation. You had an intention in your head, and you converted it into a sequence of operations the machine would accept.

We got good at this. We called it being good with computers. We taught it in schools, sold software based on whose syntax hurt less, and quietly sorted people into those who could make the machine do what they wanted and those who got stuck.

That was the deal. Humans learn the machine’s language, and in return the machine does the work. It got us a long way. But look at what it actually asked of us. The person at the computer was an operator. Their whole job was to know the controls and run the steps in the right order. The part that mattered, the part where you decide what you actually want, got buried under the mechanics of making the machine do it.

From operator to director

Vibe computing flips the deal.

You say what you want. The system figures out how. You don’t specify the steps anymore. You specify the result, and a capable system works out the path to it.

This is a small change in syntax and a massive change in who you are at the keyboard. You stop being the operator who memorized the controls. You become the director who knows the outcome. You don’t need to know where the button is. You need to know what you want, and you need to be able to say it clearly.

That last part turns out to matter more than people expect. We’ll come back to it.

Software fluency is about to stop mattering

For a generation, knowing your way around a computer was a real advantage. Where the menu lived, which shortcut saved an hour, the exact incantation that made the thing work. That fluency separated the people who could bend computers to their will from the people who couldn’t. It was, quietly, a class marker. It took the right training, the right early exposure, the patience to learn interfaces that were never designed for you.

Vibe computing erases that line. When all you have to do is describe the outcome, the person who never learned the shortcut and the person who memorized every one of them end up on equal footing. We think that’s one of the best things about it. Computing stops being a skill you had to earn your way into and becomes something anyone can direct.

The new fluency is taste

Here’s the catch, and it’s the interesting part.

If you no longer have to translate your intent into machine steps, you still have to have the intent. Clearly. Specifically. Vibe computing doesn’t delete the hard part of using a computer. It moves it. The work shifts from how do I make this happen to what exactly do I want.

That’s harder than it sounds. Most of us are vague. We know roughly what we want and we discover the specifics by bumping into the tool. Take the tool’s resistance away and you’re left alone with your own fuzziness. So the new fluency isn’t knowing the controls. It’s taste. Knowing what good looks like. Being able to say the thing precisely enough that a capable system can act on it.

Voice fits this almost perfectly, which is a big part of why we think text was always a transitional interface for this. When you’re describing an outcome instead of entering commands, talking is faster and more natural than typing. The keyboard was built for operators. Directors talk.

Where this goes

Picture the end state. You sit down at a computer and you don’t think about the computer at all. You think about the work. You say what you want and it happens, whether that’s one click’s worth of effort or a thousand. The interface disappears. The friction disappears. What’s left is the part that was always the point: knowing what you want and being clear about it.

That’s the world vibe computing is pointing at. A computer you direct instead of operate. A tool anyone can use well, not just the people who learned its language. The shift from operator to director isn’t a feature. It’s the next chapter in a fifty-year story about who has to do the translating.

So here’s the question worth sitting with. For fifty years the hard part of using a computer was the machine. Learning it, fighting it, bending to it. When that part goes away, the only thing left is you. What you want. How clearly you can say it. Whether you actually know good from almost-good.

That’s the strange thing about a world where the computer does the doing. It hands the hard part back to you, and it turns out the hard part was never the clicking. It was knowing what to ask for. Vibe computing doesn’t make that question disappear. It finally makes it the only one that matters.

Want to go deeper on vibe computing? Explore the directory of the people and products building it, and read more about the idea at vibe-computing.ai.