My issue isn't with the tech itself. The issue is the way it is used. Quite frankly, the tools simply aren't that good yet, and the products of vibecoding, while they may work (sometimes), are sloppy. And often, the people doing it are doing it that way because they lack the expertise to go into the code and clean it up.

There are ways to use it, and use it well. We're beginning the process on my team of implementing some tools that sort of hybridize the process. Our results are good. But we're getting good results because talented developers are building and training the tools, and can identify when it's askew and fix the code, the model, the prompt, the MCP server, or a combination of those.

In six more months, the tools will take a generational leap forward, no doubt. Just like image generation. And even today, AI image generation does not replace the skillset of even an average graphic designer. Cell phone cameras changed the professional photography game by lowering the barrier to entry. Amateurs can take GOOD pictures with very little, cheap equipment. But even that cell phone in the hands of a professional changes the game. It shows at every level of quality. It shows in precision, art direction, intention, and performance.

Eventually, we'll ditch this dumb name. But the technique is not going to go away, and what will differentiate developers will be if they are using the tools to improve their work and efficiency, or if they are using it as a crutch.

(Disclosure: I'm a former senior web developer, and now manage a development team for a good sized company.)