This is the guy that created bittorrent, btw. I know that was a long time ago, but he's not just some random blogger.
I guess we're not going to talk about his cryptocurrency?
not familiar, can you expand?
The cult of vibe coding is dogfooding run amok
551–555 of 555 posts
Re: The cult of vibe coding is dogfooding run amok
#552Earlier quoted context omitted.
"Code quality" here isn't referring to some aesthetic value. Coding agents write code that doesn't converge, meaning code that they cannot evolve after a while. They get to the point where fixing one bug causes another, and then the codebase is in such a state that no human or agent can salvage. People who say they don't care about the quality of code produced by agents are those who haven't been evolving non-trivial…
> Coding agents write code that doesn't converge, meaning code that they cannot evolve after a while That's not true, and I'm not sure what that even means. It's totally up to you the human to ensure AI code mergable or evolvable, or meet your quality standard in general. I certainly have had to tell Claude to use different approaches for maintainability, and the result is not different than if I do it myself.
Sure, if you vigilantly review the agent's output and say no when it's wrong (which happens very frequently) then things work. I meant that without such ver close supervision things don't converge because agents make mistakes that compound.
Re: The cult of vibe coding is dogfooding run amok
#553Earlier quoted context omitted.
I think the industry-wide hope is that AI manages the AI-written code, but it’s unclear whether that’s actually going to work out in practice. Right now, my experience is that is dicey. I’ve had AI mess up a codebase to the point where I threw it away and restarted. Maybe I was doing it wrong, though, in that I was looking at the code and was increasingly horrified by the slop. I get the feeling that in this new worl…
IME AI-native engineering requires a lot of infrastructure to make it viable. Teams who are just opening up cursor and putting it on "auto" and trying to one shot features may get stuff that works but is indeed slop. Since the beginning of the year, I've been spearheading a low-stakes AI-native project (an internal tool). No one's written a single line of code. And we've learned so much from this experience. The firs…
[deleted]
Re: The cult of vibe coding is dogfooding run amok
#554Earlier quoted context omitted.
I think the industry-wide hope is that AI manages the AI-written code, but it’s unclear whether that’s actually going to work out in practice. Right now, my experience is that is dicey. I’ve had AI mess up a codebase to the point where I threw it away and restarted. Maybe I was doing it wrong, though, in that I was looking at the code and was increasingly horrified by the slop. I get the feeling that in this new worl…
IME AI-native engineering requires a lot of infrastructure to make it viable. Teams who are just opening up cursor and putting it on "auto" and trying to one shot features may get stuff that works but is indeed slop. Since the beginning of the year, I've been spearheading a low-stakes AI-native project (an internal tool). No one's written a single line of code. And we've learned so much from this experience. The firs…
[dead]