Is vibe coding the future?

As developers use AI to speed up code generation, leaders must work to ensure the technology complements existing practices

The text "Is vibe coding the future" against a dark background with a blue curly bracket (brace) either side of the title. The words "vibe coding" are in yellow, the rest are in white. In the bottom-right corner, the ITPro podcast is shown.
(Image credit: Future)

As developers have embraced AI to a greater degree, many have hailed the rise of so called vibe coding, in which broad prompts are given to AI models to produce refined code that's actionable and in many cases deployable.

But vibe coding also comes with risks, because by its very nature it's more of a hands-off activity. It decreases the degree to which developers can explain what their code is doing, and may lead to them overlooking vulnerabilities.

How serious is this risk, and what are the potential benefits of vibe coding in the future?

In this episode, Rory speaks to Simon Black, director of evangelism at Mendix, to unpack what vibe coding is and why it comes with such high risks.

Highlights

"I think currently, vibe coding and the process of vibe coding has some of limitations. I think the challenge of vibe coding is that they are trying to speed up the part of development that people find most difficult, which is writing the code. And you know that that comes with a lot of advantages. You can get things done very, very quickly, but it often forgets about all the other challenges with software development, things like being able to do peer reviews, being able to improve the deployment, the full software development life cycle."

"You need to need to give it context of your organization and how it builds software. Not just the code but how do I evaluate what type of software we should even be building as an organization? How do I assign the value to it? How do I understand which projects to pick first? You need to be able to give it context around how you govern, how you audit projects."

"They've taken a coders' approach to a no coders' world. Let's say it makes sense. So they've gone, okay, well, we need to build applications quicker. The best way we can do that is by giving AI the ability to generate code. Okay, great. That works if you're giving to a developer audience, not so great if you're giving it to maybe more of a citizen developer, or someone that is not from a software development background, and expecting them to understand, you know, TypeScript or understand React code or understand how databases work and so on.

Footnotes

Subscribe 

Rory Bathgate
Features and Multimedia Editor

Rory Bathgate is Features and Multimedia Editor at ITPro, overseeing all in-depth content and case studies. He can also be found co-hosting the ITPro Podcast with Jane McCallion, swapping a keyboard for a microphone to discuss the latest learnings with thought leaders from across the tech sector.

In his free time, Rory enjoys photography, video editing, and good science fiction. After graduating from the University of Kent with a BA in English and American Literature, Rory undertook an MA in Eighteenth-Century Studies at King’s College London. He joined ITPro in 2022 as a graduate, following four years in student journalism. You can contact Rory at rory.bathgate@futurenet.com or on LinkedIn.