Heh. Got a customer recently around this. Entire infrastructure and CI/CD vibecoded. They half implemented Kubernetes in Github Actions that were several thousand lines long and impossible to understand.

I think the problem will get worst. I dislike the marketing around AI, but I do think it is a useful tool to help those who have experience move faster. If you are not an expert, AI seems to create a complex solution to whatever it is you were trying to do.

▲

ethbr1 29 minutes ago | parent [-]

> If you are not an expert, AI seems to create a complex solution to whatever it is you were trying to do.

I've been watching non-developers vibe code stuff, and the general failure mode seems to be ignorance of 3-pick-2 tradeoffs.

They'll spam "make it more reliable" or some such, and AI will best-effort add more intermediary redis caches or similar patterns.

But because the vibe coders don't actually know what a redis cache is or how it works, they'll never make the architectural trade-offs to truly fix things.

	▲	danbolt 9 minutes ago \| parent [-]
		I’ve noticed something similar with vibecoded game rendering logic submitted by peers. Sometimes it will be peppered with extraneous checks for nullptr, or early returns on textures that have zero size. I often wonder if it’s the statistical nature of the LLM mixed with a request in the prompt.