Hacker News new | ask | show | jobs
by zionsati 1 day ago
What I've experienced was if you let an agent "fix" the problems, and keep vibe coding away, at some point they'll stop working. Fixing one breaks another, and the tests you think you had as guardrails turned out to be useless because they're contradictory. The specifications (hence spec driven coding with AI) become very important. If you get that wrong, the agents will try their best to somehow fit the output to your requests. For simple UI projects, sure, you can quickly see it visually. For anything complex (most real world systems are), there's a lot of reading and re-reading AI produced code. This could be slower and more time consuming, and often cause mental fatigue because there's no way you can gauge the level of THIS particular AI's output, unlike when you're doing PR reviewing for a actual human. You tend to take shortcuts because you know them, how they code, and their strengths and weaknesses. With AI, it's random, and I've personally seen prod going down because of it.

So yes, I think the crowd is anti-AI where it matters. But claiming AI-assisted version could have been deployed 10x faster, I doubt you've really maintained any real world software systems.