Evidence receipt / belief
Published · transcript-backedLex Fridman: belief
12 Jul 2025 Lex Fridman Podcast #474 – DHH: Future of Programming, AI, Ruby on Rails, Productivity & Parenting
“I think one of the big open questions to me is how far you can get with vibe coding, whether an approach for a young developer to invest most of the time into vibe coding or into writing code from scratch.”
Source trail
Everything needed to verify it.
- Speaker
- Lex Fridman
- Attribution
- Verified speaker
- Claim type
- belief
- Recorded
- 12 Jul 2025
- Publisher
- Lex Fridman Podcast
Transcript context
…t, it was the robots that were going to take over. Then Gen AI comes out, and then all the artists suddenly look like, “Holy shit, is this going to do all animation now? Is going to do all music now?” They get real scared, and now I see the latest Tesla robot going like, “Oh, maybe we’re back now to blue-collar being in trouble because if it can dance like that, it can probably fix a toilet.” So no one knows anything, and you have to then position yourself for the future in such a way that it doesn’t matter that you pick a profession or path where if it turns out that you have to retool and re-skill, you’re not going to regret the path you took. That’s a general life principle. For me, how I look at all endeavors I involved myself in is I want to be content with all outcomes. When we start working on a new product at 37 Signals, I set up my mental model for success and I go, “Do you know what? If no one wants this, I will have had another opportunity to write beautiful Ruby code to explore greenfield domain, to learn something new, to build a system I want, even if no one else wants it.” What a blessing, what a privilege. If a bunch of people want it, that’s great. We can pay some salaries, we can keep the business running, and if it’s a blowaway success, wonderful. I get to impact a bunch of people. I think one of the big open questions to me is how far you can get with vibe coding, whether an approach for a young developer to invest most of the time into vibe coding or into writing code from scratch. So vibe coding, meaning I’m leaning into the meme a little bit, but the vibe coding, meaning you generate code, you have this idea of a thing you want to create, you generate the code and then you fix it with both natural language to the prompts and manually. You learn enough to manually fix it. So that’s the learning process. How you fix code that’s generated or you write code from scratch and have the LMS kind of tab, tab, tab, tab, add extra code, like which part do you lean on? I think to be safe, you should find the beauty and the artistry and skill in both, right? From scratch, so there should be some percent of your time just writing from scratch and some percent vibe coding. There should be more of the time writing from scratch if you are interested in learning how to program. Unfortunately, you’re not going to get fit by watching fitness videos. You’re not going to learn how to play the guitar by watching YouTube guitar videos. You have to actually play yourself. You have to do the sit-ups. Programming, understanding, learning almost anything requires you to do. Humans are not built to absorb information in a way that transforms into skills by just watching others from afar. Now, ironically, it seems AI is actually quite good at that, but humans are not. If you want to learn how to become a competent programmer, you have to program. It’s really not that difficult to understand. Now, I understand the temptation and the temptation is there because vibe coding can produce things perhaps in this moment, especially in new domain, you’re not familiar with tools you don’t know perfectly well that’s better than what you could do or that you would take much longer to get at, but you’re not going to learn anything. You’re going to learn in this superficial way that feels like learning but is completely empty calories, and secondly, if you can just vibe code it, you’re not a programmer. Then anyone could do it, which may be wonderful. That’s essentially what happened with the Access database. That’s what happened with Excel. It took the capacity of accountants to become software developers because the tools became so accessible to them that they could build a model for how the business was going to do next week that required a programmer prior to Excel. Now, it didn’t because they could do it themselves by coding enables non-programmers to explore their ideas in a way that I find absolutely wonderful, but it doesn’t make you a programmer.…
Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.