"Many people today say Vibe Coding does not work. It creates situations where the code does not work and you can't get out from it"
It's true to say that Vibe coding doesn't work for most complex existing solutions today.
But that's a temporary aspect; things will transition into a phase where this will be possible.
Today, Flow Coding with AI, which I do in production with Claude Code, works well. I can take this hybrid approach because I am still the engineer and partly the coder. As a humans, we run at the pace of man, not at the pace of AI, which is the main difference between vibing and flow coding.
The reason is that our codebase, a complex, multi-tenant B2B solution, was never meant to be built in a "black box" while vibing. But it's compatible with AI in the sense of Flow Coding.
Newly started projects can work with vibing today, at least to some degree, since it's a relatively new technology. At its current enhancement rate, it won't be long before we can create AI-driven solutions on a more complex scale. The biggest question then will be, "Who is we then"?
We developers, We Engineers, or We business people?
BUT:
Those solutions will look different. Those codebases aren't meant to be worked on together with humans. A human will be the engineer outside of this black box.
When?
The companies will shift; Some are doing that today, a few will start soon, and most others will wait years before doing anything (traditional). I don't think this transition will be a fast one. For this, I have spent too much time in the market as an entrepreneur and engineer. I know things are slow. See all the old PHP/ASP.NET Legacy System people still work on.
"Many people today say Vibe Coding does not work. It creates situations where the code does not work and you can't get out from it"
It's true to say that Vibe coding doesn't work for most complex existing solutions today.
But that's a temporary aspect; things will transition into a phase where this will be possible.
Today, Flow Coding with AI, which I do in production with Claude Code, works well. I can take this hybrid approach because I am still the engineer and partly the coder. As a humans, we run at the pace of man, not at the pace of AI, which is the main difference between vibing and flow coding.
The reason is that our codebase, a complex, multi-tenant B2B solution, was never meant to be built in a "black box" while vibing. But it's compatible with AI in the sense of Flow Coding.
Newly started projects can work with vibing today, at least to some degree, since it's a relatively new technology. At its current enhancement rate, it won't be long before we can create AI-driven solutions on a more complex scale. The biggest question then will be, "Who is we then"?
We developers, We Engineers, or We business people?
BUT:
Those solutions will look different. Those codebases aren't meant to be worked on together with humans. A human will be the engineer outside of this black box.
When?
The companies will shift; Some are doing that today, a few will start soon, and most others will wait years before doing anything (traditional). I don't think this transition will be a fast one. For this, I have spent too much time in the market as an entrepreneur and engineer. I know things are slow. See all the old PHP/ASP.NET Legacy System people still work on.
This! "The reason is that our codebase, a complex, multi-tenant B2B solution, was never meant to be built in a "black box" while vibing."