RE: RE: Experience vs AI: who wins when something breaks in production?
You are viewing a single comment's thread from:

RE: Experience vs AI: who wins when something breaks in production?

edje(72)
Published in
The Pub
Words
284
Reading
2 min
Listen
Play
17d

From your story, I feel the developers vibe coding don't know how they shall vibe code. Plenty of companies turn towards vibe coding almost eveything, and not breaking their systems. And when breaking, they fix it. Anthrophic claims that almost 100% of the code what makes Claude, is vibe coded. I know several startups in my country, one man shows, run by serious software developers who earned their stripes in past decades, are vibe coding from A to Z. And yes, sometimes they rewrite something by hand, or change a module or function by driving the AI into the direction the developer wants. But they vibe code from A to Z. And yes, all these are as you call: Production. In fact, these are Dutch challengers to WeTransfer and Office365 with quite several customers already. One of my colleagues started vibe coding a few months ago. He was sceptical. I helped push him. Now he is delivering plugins, adapters, logic based on vibe coding. Already today it is implemented in to our IT solutions, used by in increading number of professional companies in our market, from billion-dollar companies to high-critical systems within governments.

Long story short: Vibe coding must be handle through a process. One must know what one does. At least today. In a few years from now, I predict almost anyone can vibe code. In fact, vibe coding will happen without we knowing it. We simply ask for something: I want to order xyz and the AI system does what it needs to do to get this done, including vibe coding when some service logic is not available, or isn't addressing all the rules it needs to followup on the requestors requirements.

@edje: From your story, | Ecency