“Vibe coding”: what is it?

By Raphaël Fillion

“Vibe coding”: what is it?

By Raphaël Fillion

Development can seem really difficult, almost impossible for some. We tell ourselves that it takes years of practice before hoping to land a first job in the field. And even in 2025, while a new “revolutionary” technology seems to come out every month, many still struggle to keep up.

In February 2025, renowned computer scientist Andrej Karpathy posted a message on X (formerly Twitter) where he used the term “vibe coding” for the first time. He defines this concept as using AI to code without really knowing what’s happening under the hood. The advantage? The speed at which you can arrive at a product, even without the slightest notion of programming. This concept allows developers to quickly reach the prototyping stage and leave the optimization portion for the end of the project.

There are certain benefits to this concept:

  • Sense of speed: you see the app take shape in real time.
  • Creative adrenaline: mentally finding the solution to a problem triggers a slight thrill of excitement.
  • Low barrier to entry: you open any editor, you type – that’s it.
  • Accelerated learning loop: each prompt returns commented code that serves as a mini-tutorial, compressing months of study into a few guided sessions.
  • Democratization of development: designers, entrepreneurs, or marketers can bring their ideas to life without depending on a technical team, broadening access to software creation.

But you see where I’m going… the benefits stop here.

Behind the fever of “vibe coding” also lie areas of turbulence:

  • Lightning technical debt: what is prototyped in the blink of an eye can become a nightmare to maintain; code generated on the fly often lacks solid architecture and automated tests.
  • Superficial understanding: letting AI write the logic reduces the developer’s mastery; at the first serious bug, you find yourself deciphering a codebase you never really understood.
  • Tool dependency: if the AI service changes its API, becomes paid, or goes down, the workflow collapses – and the team must relearn to row without an engine.
  • Bias and hallucinations: models sometimes generate non-optimal or even vulnerable solutions, relying on fuzzy correlations; without a critical eye, you can integrate security flaws or anti-patterns.
  • Quality and performance take a back seat: a quick prototype is not synonymous with a robust application; optimizations, accessibility, and regulatory compliance still require human expertise and dedicated time.

How can we then use “vibe coding” optimally?

  • Map before coding: Take the time to sketch the architecture: screens, user journeys, look & feel. A clear skeleton avoids dead ends later.
  • Feed the AI maximum context: Show it the mockups, describe expectations and edge cases; the more it knows, the less it hallucinates.
  • Dialogue, iterate, start over: Ask questions (“Explain this code block to me”), test, rollback when things go off track, and start fresh cleanly if necessary.
  • Master the fundamentals: Git, environment variables, deployment: these basics remain essential to consolidate the final 20% (with Cursor, Windsurf, or other tools).
  • Leverage the community: Dedicated Discords, forums, professionals: ask for help, share your roadblocks, and move forward without getting stuck.
  • Move fast, but not blindly: “Move fast and break things”, yes – provided you know how to fix immediately and document the path taken.

Several tools are available for “vibe coding”; here are a few:

BOLT.NEW

A solution from StackBlitz, Bolt.new instantiates a complete Node environment in the browser thanks to WebContainers: a simple prompt generates the skeleton, installs dependencies, launches the server, and even offers instant deployment. Perfect for a full-stack POC in a few minutes, but watch out for beta phase quotas.

LOVABLE.DEV

A “chat-to-build” platform oriented toward MVP: describe your idea (or import a Figma mockup) and the AI produces the frontend, backend, and hosting. The free tier suits public prototypes and small teams; paid plans unlock private projects and comfortable quotas.

CURSOR

An AI-powered fork of VS Code, Cursor reads the entire directory, anticipates multi-file changes, and offers a secure terminal agent. Ideal for accelerating refactors and maintenance, provided you maintain code reviews and automated tests.

CLAUDE CODE

Anthropic’s CLI tool maps your monorepo, answers questions, modifies files, then opens GitHub/GitLab pull requests upon validation. A powerful accelerator for debugging or adding a feature without leaving the terminal.

“Vibe coding” is an excellent accelerator for transforming an idea into a prototype. However, it requires a return to fundamentals: code review, refactoring, testing, and careful architecture. Used with discernment, it fosters innovation; applied without control, it opens the door to significant technical debt. Finding the balance between creative momentum and the rigor of robust, maintainable code remains the key to success.

And you, how do you use AI?

/ Prochains articles