It'll really start to rub when a customer hires a vibe coder; the back-and-forthing about requirements will be both legendary and frustrating. It's frustrating enough with regular humans already, but thankfully there's processes and roles and stuff.

There’ll be more and more processes and stuff with AIs too. Kiro (Amazon’s IDE) is an early example of where that’s going, with a bunch of requirement files checked in the repo. Vibe Coders will soon evolve to Vibe PMs

> When will AI's progress be fast enough for a vibe coder never to need to bother with technical problems?, that's the question.

If we reduce the problem into this, you don't need developer at all. Some vague IT-person who knows a bit about OS, network, whatever container and clustering architecture is used, and can put good enough prompts to get workable solution. New age devopsadmin sort of.

Of course it will never pass any audit or well setup static analysis and will be of corresponding variable quality. For business I work for, I am not concerned for another decade and some more.

I'm curious how many vibe coders can compensate for the AIs shortcomings by being smart/educated enough to know them and work around them, and learn enough along the way to somehow make it work. I mean, even before AI we had so stories of people who hacked together awful systems which somehow worked for years and decades as long as the stars align in the necessary areas. Those people simply worked they ass to make it work, learned the hard how it's done and somehow made something which others pay enough money for to justify it.

But today, whom I mostly hear from are either grifters who try to sell you their snake oil, or the catastrophic fails. The in-between, the normal people getting something done, are barely visible yet for me, it seems, or I'm just looking at the wrong places. Though, of course there are also the experts who already know what they are doing, and just use AI as an multiplicator of their work.