Genuinely not yet convinced. The CEO of windsurf said the goal for the next year was to get agentic coding to the reliability and maturity that it can be used in production for mature codebases. That rhymes true.

I use autocomplete and chat with LLMs as a substitute for stack overflow. They’re great for that. Beyond that, myself and colleagues have found AI agents are not yet ready for serious work. I want them to be, I really do. But more than that I want our software to be reliable, our code to be robust and understandable, and I don’t want to worry about whether we are painting ourselves into a corner.

We build serious software infrastructure that supports other companies’ software and our biggest headache is supporting code that we built earlier this year using AI. It’s poorly written, full of bugs including problems very hard to spot from the code, and is just incomprehensible for the most part.

Other companies I know are vibe coding, and making great progress, but their software is CRUD SaaS and worst case they could start over. We do not have that luxury.

If you get as much enjoyment out of problem-solving and programming as you do doing household chores, I'm not sure why you went into this career. I agree that the folks who are 100% anti-using-it-ever are overreacting, but IME replacing the overwhelming majority of the work with vibe-coding is both mind-numbing from a developer perspective and doesn't actually get you better results (or faster results, unless you're basically cowboy coding with no regard for thoroughly ensuring correctness)

Vibe coding is when you don't check the output.

Instructing Claude Code to handle a circular dependency edge case in your code and write tests for it, while reviewing the work definitely does not quality as vibe coding.