Shubham Nigam, co-founder of Questera AI.
If you’ve been following technology trends lately, you’ve probably heard people talk about “vibe coding.” It’s not your usual way of writing software, as it refers to a style of coding that relies on AI for assistance.
As someone who’s been coding for the past 20 years, spent time in the AI space co-founding an agentic AI platform that generates code solutions and worked closely with developers experimenting with vibe coding, I’ve seen both the magic and the mess that can come with it. So, I want to share some honest, clear thoughts on where I believe vibe coding is heading, what’s working, what’s not and how teams can keep up without losing their way.
What is vibe coding?
‘Vibe coding,” a term coined by OpenAI cofounder Andrej Karpathy, is essentially when developers write code based on how something feels—with the help of AI. It’s fast, flexible and built on instinct. You’re not locked into step-by-step rules. You move quickly and trust your flow.
As MIT Technology Review explained: “Not all AI-assisted coding is vibe coding. To truly vibe-code, you have to be prepared to let the AI fully take control and refrain from checking and directly tweaking the code it generates as you go along—surrendering to the vibes.”
There are a bunch of AI coding tools out there that can help support this approach. For instance, my company built one, and others include Replit, Bolt, Lovable, v0 and more.
Why is it growing?
Vibe coding has been picking up speed. Here’s why I believe that’s the case:
1. It streamlines the coding setup. Traditionally, before you can even write your first real line of code, you often need to set up files, manage folders, pick frameworks, etc. It’s a whole production, and vibe coding helps cut through that.
2. It can give developers more freedom. Traditional coding can feel like walking on a tightrope. There are many rules and a lot of structure. One small mistake and you might be stuck trying to fix it for hours. With vibe coding, there’s a sense of flow.
3. The tools have improved. A few years ago, this would’ve been a joke. But AI assistants and user interfaces have improved, and these tools can fill in the blanks while you focus on the larger idea.
4. Teams are moving faster. I’ve seen projects go from three months to three weeks just because there’s less back-and-forth. You build, tweak and move on.
5. This is just how many people work now. Today, everything’s fast—feedback, releases, updates. Nobody wants a two-hour meeting to talk about button colors. Vibe coding matches that energy. It lets you build, not overthink.
Where is it heading next?
As I see it, vibe coding isn’t likely to slow down, but I do think it’s growing up and entering a phase where it’s less about just speed and more about being smart with it. I’ve tried a few of these new tools, and let me tell you, developers can focus on ideas while the AI smooths out the rough edges.
It’s not perfect. But it’s getting there. And I truly believe the future of vibe coding contains both instinct and intelligence. You stay creative, but don’t lose control.
Is it all sunshine?
With vibe coding, I believe you can get too relaxed. There’s less structure and less thinking ahead. That can lead to messy code, bugs or teams going off-track. Moreover, as the aforementioned MIT article pointed out, AI can make mistakes, and vibe coding can be particularly risky for complex, higher-stakes projects.
Yet, in my view, the biggest challenge is not the code; it’s the thinking behind it. Some folks try to “vibe” through every task and every project. It might feel great at first, flying through screens and features. But then things start to fall apart. Not every moment is made for fast flow. Some things need a pause. Some things need planning. The real skill is knowing when to use vibe coding and when to slow it down.
This mindset is the key. If a team thinks vibe coding means no structure, they’re in for a rough time. But if they treat it like a tool, one you pull out when it fits, then it’s great.
How can companies stay ahead?
I’ve talked to a bunch of teams about this, and here’s what I keep telling them: If you want to keep up without getting overwhelmed, just start small and smart.
1. Help your team see where vibe coding actually fits. Not everything needs it. Point them to the right parts, let them test and let them play.
2. Use tools that quietly clean up behind the scenes. Let developers flow, but have a safety net that checks things after. This can save time later.
3. Give them just enough structure. Don’t lock developers in, but don’t go full chaos either. Let them create, but keep the backup ready.
Final Take
Vibe coding is not bad. It’s exciting. It’s fast. It opens new doors. It’s changing how we think, build and move, and I believe it’s here to stay.
But companies must remember that it’s not a shortcut to great software. Like anything new, it needs intention. Use it wisely. Know when to flow and when to slow down. Set clear boundaries. Keep learning. And, most of all, stay curious.
Forbes Business Council is the foremost growth and networking organization for business owners and leaders. Do I qualify?
Read the full article here
