| "There's a point in the middle where you implement the same function twice perhaps and then on the third time feel like such a thing should already be there and so go look or maybe perhaps add some documentation or centralize functionality to a utilities library etc." Yes, my point was exactly about the middle ground. (And the double implemented functions were of a rather small kind, where rewriting them was faster than looking for the old ones. And it was hyperbole of course, I don't routinely do the same again and again for no reason. I remember maybe 2 or 3 instances of that happening) I wrote bad code and good code in my life, depending on the project and depending on myself. And where I wrote bad code in the past, AI is actually great with helping that. Finding duplicates, documentation out of order, etc. "I believe the point being discussed is the scale of "badness" that vibe-coding introduces." The point I was discussing is that code is not automatically understood, or good, just because a human wrote it. So all in all, sure, Vibe coding enables a new universe of bad code (that pretends to look good). But if done right, it can also raise the bar. It is a powerful tool and up to us on how we use it. |