Speaker unverified: belief

Transcript context

…As an interesting case study, maybe a thought experiment, if I wanted to vibe code Basecamp or hey, some of the products you’ve built, what would be the bottlenecks? Where would I fail along the way? What I’ve seen when I’ve been trying to do this, trying to use vibe coding to build something real is you actually fail really early. The vibe coding is able to build a veneer at the current present moment of something that looks like it works, but it’s flawed in all sorts of ways. There are the obvious ways, the meme ways that it’s leaking all your API keys, it’s storing your password in plain text. I think that’s ultimately solvable. It’s going to figure that out, or at least it’s going to get better at that, but its capacity to get lost in its own Labyrinth is very great right now. You let it code something and then you want to change something and it becomes a game of Whack-A-Mole real quick. Pieter Levels who’ve been doing this wonderful flight simulator was talking to that where at a certain scale the thing just keeps biting its own tail. You want to fix something and it breaks five other things, which I think is actually uniquely human because that’s how most bad programmers are at a certain level of complexity with the domain. They can’t fix one thing without breaking three other things, so in that way I’m actually in some way it’s almost a positive signal for that. The AI is going to figure this out because it’s done an extremely human trajectory right now. The kind of mistakes it’s making are the kind of mistakes that junior programmers make all the time. Yeah. Can we zoom out and look at the vision, the manifesto, the doctrine of Rails? What are some of the things that make a programming language a framework? Great, especially for web development, so we talked about happiness.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.