No, I completely disagree with this entire article.

Bad code or good code is no longer relevant anymore. What matters is whether or not AI fulfills the contract as to how the application is supposed to work. If the code sucks, you just rerun the prompt again and the next iteration will be better. But better doesn't matter because humans aren't reading the code anymore. I haven't written a line of code since January and I've made very large scale improvements to the products I work on. I've even stopped looking at the code at all except a cursory look out of curiosity.

Worrying about how the sausage is made is a waste of time because that's how far AI has changed the game. Code doesn't matter anymore. Whether or not code is spaghetti is irrelevant. Cutting and pasting the same code over and over again is irrelevant. If it fulfills the contract, that's all that matters. If there's a bug, you update the contract and rerun it.

▲

zozbot234 7 hours ago | parent | next [-]

> Bad code or good code is no longer relevant anymore.

It's extremely relevant inasmuch as garbage code pollutes the AI's context and misleads it into writing more crap. "How the sausage is made" still matters.

▲

il-b 8 hours ago | parent | prev | next [-]

Someone vibe-coded the brake control system in your car. It passes the tests. Is it good enough for you?

	▲	jschveibinz 7 hours ago \| parent [-]
		This is the crux of the whole conversation. What percentage of software is "critical"? My guess is 50%. And AI will soon be able to play in that space as well. So in the future, maybe 25% of "critical" software will require real humans in the loop?

▲

sunnybeetroot 8 hours ago | parent | prev | next [-]

This entirely depends on the product. If it’s your own personal blog, then for sure no need to read the code, but a change in a banking architecture would be irresponsible to not have an understanding of the actual code change.

	▲	cesarb 2 hours ago \| parent \| next [-]
		> If it’s your own personal blog, then for sure no need to read the code, I can off the top of my head think of at least three ways in which being careless with the code powering "your personal blog" could have real consequences. Suppose it has a bug which allows unauthenticated users to manage your pages, or even worse remote code execution. Then it could be used as a jumping-off point to attack other systems, for instance by turning it into a C&C server for some malware. It could be used in a "watering hole attack" against your readers. Or someone could edit the blog articles to make it appear that you said something you didn't. "Not reading the code" is irresponsible for any software exposed to the global network.
	▲	adrian_b 7 hours ago \| parent \| prev [-]
		Yes, vibe coding is perfectly acceptable if it is coupled with financial and penal liability of the authors of the program for any damages caused by that program, so if they choose to use it they must be willing to bet on its suitability. In case of damages, vibe coding should be an aggravating circumstance, i.e. gross negligence. When the use of a program cannot have any nefarious consequences, obviously vibe coding is fine. However, I do not use many such applications.

▲

azov 6 hours ago | parent | prev [-]

Your code is that contract (unless your tests cover every possible input, which is not practical in most cases).