Uncapped #20 | Guillermo Rauch from Vercel

6 Aug 2025 · 1 h 1 min

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

Podcast Notes: Uncapped #20 | Guillermo Rauch from Vercel

Episode Overview In this episode of "Uncapped," Jack Altman interviews Guillermo Rauch, founder and CEO of Vercel. The conversation delves into Guillermo's journey as a self-taught developer, his contributions to foundational JavaScript frameworks like Next.js and Socket.io, and the implications of AI for developers. The episode highlights Vercel's growth, code generation (codegen), and the evolving landscape of software development.

---

Key Themes

  1. Vercel's Early Insights
  2. Guillermo shares his background and experiences leading up to Vercel.
  3. Importance of optimizing continuous integration and continuous deployment (CI/CD) processes for developer productivity.
  1. The State of Affairs for Code Generation
  2. Discussion about the current landscape of code generation tools and their effectiveness.
  3. Perceived vs. Realized Productivity: Surveys show developers feel faster but evidence suggests productivity may not have improved significantly.
  1. Implications of AI for Developers
  2. AI's role in software development is expanding, transforming how code is generated and deployed.
  3. Emphasis on the need for developers to adapt and learn new skills as AI tools become more integral in the coding process.
  1. Skills of the Future
  2. Future developers should focus on understanding concepts over learning specific programming languages.
  3. Encouragement for young learners to build what they visualize in their minds using platforms like Vercel.
  1. Product Building Taste
  2. The notion of "taste" in product building is explored, suggesting it relates to how well one can visualize and iterate on ideas.

---

Discussion Highlights

Background and Foundation

  • Guillermo began coding at age ten and has a strong open-source background.
  • His first startup was acquired by Automattic (WordPress.com), leading to insights that shaped Vercel's mission.

The Evolution of Code Generation

  • Code generation is seen as a powerful tool but is still evolving.
  • Current tools may not yet provide the expected leap in productivity, leading to discussions on the need for rigorous code reviews.

Fault Attribution in Software

  • Guillermo discusses the challenge of identifying the source of problems in software systems, particularly in complex environments with multiple vendors.
  • The role of agents in improving fault attribution in the future.

Future of AI in Software Development

  • The conversation shifts toward the potential for AI to handle more of the software development lifecycle, including generating and reviewing code.
  • Emphasis on the balance between human oversight and AI efficiency—ensuring developers interact with and learn from the tools rather than becoming too reliant.

Advice for Aspiring Developers

  • Guillermo advises aspiring developers to focus on product ideas rather than just learning programming in isolation.
  • The development of "taste" and the ability to refine ideas through iterative practice is essential.

---

Key Takeaways

  • Focus on Outcomes: Developers should prioritize business outcomes when deploying code rather than just writing it.
  • Learning and Adaptation: As AI tools advance, developers need to adapt their workflows and learning strategies accordingly.
  • Productive Frustration: The struggle in coding can lead to satisfaction, but new tools should ensure that the process is still challenging and rewarding.
  • Future Skills: Emphasis on visualization skills and an understanding of user needs will be crucial for the next generation of developers.

---

More About Guillermo Rauch

  • [Vercel](https://vercel.com/)
  • [Guillermo on X](https://x.com/rauchg)

More About Jack Altman

  • [AltCap](https://www.altcap.com/)
  • [Jack on X](https://x.com/jaltma)

---

Additional Resources

  • [Uncapped Podcast Links](https://linktr.ee/uncappedpod)
  • Email for inquiries: friends@uncappedpod.com

---

This detailed summary provides insight into the key discussions from the podcast episode, highlighting Guillermo Rauch's perspectives on Vercel, code generation, AI in development, and advice for future developers.

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:00You've been cutting for hours and hours and he didn't even know what the output was. He was just impressed by the fact that someone could be so locked in. And so I think programming taught me that. He taught me how to focus. He taught me to be disciplined. It taught me to receive this negative feedback from the compiler and overcome it. And do think, you know, we'll need to find what the next version of that is because I don't think it's going to be programming. Seriously. All right, Guillermo, thank you so much for making the time for this. I'm really excited to chat with you. Say, people are excited on X as well.

0:27So I want to get into code gen, but before we go there, can you talk about what you worked on before Versel, you know, with next JS other projects and maybe have that fed into what you've built at Versel? Yeah. I had a startup before Versel that I exited to automatic the parent company of WordPress .com. And it was quite a successful journey for me because it was my first startup. It's nice to have an exit. But also one of the meta things that I learned I was a CTO. One of the meta things that I learned is, as a CEO, how can you influence your team in the best possible way? They are going to engineer the right things.

1:00They're going to have the best tools. The one thing I did that was revolutionary for my team was spending a lot of time in getting the CI CD process, meaning continuous integration and continuous deployment of the code that they would write, get it as efficient as possible. Meaning you write a little feature, you push code to get, you get a URL back. I built a real -time system. My background was in writing real -time frameworks, so I was obsessed with real -time streaming of data. And so people would push to get, and then I would give them this URL that had a commit ID, dot my comment that was called LearnBust.

1:38I think it was like LearnBustDemo .com. And so imagine that you're almost editing the internet in real -time. That was the feeling that I wanted to give my employees. And obviously, I did a lot of other things. I chose technology stacks and whatever. But when I would ask my colleagues, like, what was the thing that was most impactful to your time here? It was that iteration velocity, the deployment of velocity, the tooling being really neatly configured. I always do the exercises in my head of you show up to a new company. Isn't nice that Apple kind of figured out operating system and hardware and I give you a new laptop?

2:15Actually, you look, you probably, I don't know about you, but I look forward to having a new laptop. It's so new and nice. And that's only because they figured out this bootstrapping problem of like everything is ready to be used. I wanted to give that feeling but for your development tools to my team versus you get a new, you know, you're setting up a whole environment and yeah, yeah, you stole this 20 million things, fight the tools and then maybe you get to work on something. Yeah. And so that was by far the most impactful thing that I did and I wanted to, you know, It was subconscious at the time, but essentially I wanted to turn that into a company.

2:50I couldn't wait to, you know, you have that insight because then I kind of saw that not every company had that. WordPress was really good at deploying WordPress .com, but I noticed that if you had a new idea and you needed to bring it alive, and it kind of makes sense, like they'd evolved to host it really important .com. So they hadn't thought about that zero to one experience for any new idea that a developer would have. And so when I realized that, it don't know me, I couldn't wait to leave and say, this could be a huge business opportunity because the cloud was starting to take off. And the cloud was known also for its reliability, robustness, scale, et cetera.

3:26But it felt like the opposite of using your computer. That is just point and click. It was this really difficult process of configuring and figuring out instances. And so in parallel, it was this conversions of ideas. make developers really productive and happy, give them the best possible tools I built next Shias, but also figure out that cloud part that a lot of companies would put off until too long. Like you get to the point where, you know, I meet companies that are operating at massive scale that are afraid of deploying. Companies that deploy once a quarter, companies that do code freezes for weeks, months around Black Friday, and things like that.

4:01So this is not obvious to me, I kind of discovered that when I sort of resale, but I thought it was all gonna be about the instant feeling for developers, which is a big part. But then I started talking to enterprises, who's this idea that as they become bigger, they become stagnant. They become ossified in their old infrastructure choices. And you could imagine now with AI that problems 10x in terms of importance. Like we have models coming out every day. There's just like two new open source models last week. Imagine a company that is ossified in its deployment and infrastructure choices. When you started Versailles because you have this background, Did you have most of the insights that turned out to be true about what Varsal was or was it much more of you know the Problem area you know some of these customers, but you figured it out as you were I had a lot of things that were based on First principles thinking so literally measuring the speed of light and how fast can you shadow Files on a laptop to a container in the cloud that starts a build process and how fast is that build process gonna be is funny I was listening to DHA's Alex Friedman and he was saying the gold standard of DX was set in the 90s by PHP PHP is a technology that only required of you to modify files in a folder imagine drop -box if Dropbox is a live deployment you go into the magic folder you edit a file and it's live on the internet And so that was from first principles.

5:23I was chasing that dragon There are a bunch of things that I didn't know I think Versel ended up focusing a lot on the front and side in the beginning of our journeys, I realized that the biggest gap was, or the biggest opportunity I would say, was back end code was really important, but the differentiating experiences of the internet were more front and heavy. So when you look at something at ChatGPT today, a lot of what it's doing is happening right in front of your eyes in real time. It's thinking, it's streaming, it you start working on document and it splits the application in two and there's a live document here, you cannot do those things without powerful frameworks that are focused on the front end.

6:05And that was the alpha in the market. Like if I had come to market with like, again, another runtime like PHP, people would be like, oh, I have to learn a new language. And what's in it for me? And so anytime you bring a new tool is like a big ask of the world. You have to learn a new thing. You might have to migrate. This is like, it's the M word. It's like, it's like, you tell enterprise, you have to migrate. So what's in it for me? And what we realized, I actually posted some stats today that were bill -wildering about a really large retail chain that moved onto Vercel recently. I realized that by giving people the great developer experience, but without business outcomes, it would also going to be an incomplete equation.

6:46So when you move to Vercel, you now realize business outcomes. Your stuff gets faster, your stuff gets more dynamic, you're able to iterate faster and build AI products. So that didn't come overnight, obviously, and it's very hard to bootstrap the 0 -1, but the idea that it can give you receipts, I think, is pretty novel in the cloud itself. The cloud, in fact, in its initial conception, has a really bad financial equation. Because companies have data centers, they've spent tons of money in buildings, in racks, in servers, in storage appliances, in people. And then you ask them, okay, begin the journey to migrate to the cloud.

7:24Okay, cool. So now I'm gonna pay for all that. And concurrently, I'm gonna pay for the cloud bill. Cool. And what do I get at the end of it? What am I gonna see? And so I think what's benefited me is I've always been a really visual design person. So if there's nothing I can see or feel at the end of that rainbow, then the software engineering project which was just kind of pointless to me. And so we focus a lot on actually working backwards from your resulting URL that you deploy in a Excel. Even if you didn't do big A, B test studies and whatever, it's just gonna feel better. And then we're gonna teach you how to work backwards into the technology so that you start from that strong starting point of user experience.

8:05I think it's totally novel in the cloud. Like the cloud has always been about implementation details and primitives and a Excel made it about products and experience. I think that's a good transition moment because what you talk about here is, you know, starting from the end and then working backwards And I think a lot of code gen is in some ways, you know, there's maybe some analogies there That was a lot about the beginnings now is sort of fast forward all the way to today where I think code gen you're kind of at the center Of both the thinking and sort of where the technology will be two things are true one is There are a lot of people that sort of have shared information about how you know you go out and you test what developers are actually doing with the products today.

8:46And it's not working in such bewildering ways quite yet. You know, like there was a study recently sharing that like people thought they were 20 % faster, turns out they were actually 20 % slower. Yeah. Which seems like, you know, very surprising in some ways. But you know, we talked about this and it actually wasn't that surprising to you. But on the other hand, there's, you know, probably never been a market, at least that I've seen, that has more excitement, more market pull, companies are scaling revenue, probably faster than anything in this space. And so how do you see the state of affairs today?

9:21What's going on out of the offices in here like this exact hour? This is a super hot topic because at our cell we monitor the idea of landing something very closely. To us, it's not just about riding the code, is that you land it. And in fact, you're higher than bar for what you consider to be landing, the better for you. Landed means fully deployed and usable. Even better. Landing means that you've seen some business outcome. You've seen all the way through the phone. Again, this is not always easy to do because you also have to balance it with a healthy dose of shots on goal. But you have to be disciplined about what it means to land your software.

9:57Again, this is just from that principle of always working back or something. There's some pixels on someone's screen that also will result in some kind of business outcome. You know, conversion signups, new information, vibes, whatever you want to call it. But I do encourage people to think about the idea of like, landing. And I do think one of the immersion things that we're seeing is there's almost like a bottleneck in landing today. It's almost like code generation has been solved. Everyone's sharing their stats about 50 % of my company, the code is coming from AI. It's 80 % 90%. So I do think we have to be rigorous about, well, do you just have a bunch of PRs that nobody is reviewing.

10:35Do you feel that way? Do you feel the code generation is roughly speaking solved at this point? So let me give you a framework of how I think about it. I think on one extreme of the equation, we have vibe coding and tools that cater to a very broad set of users. That's where V0 are agent lives. And you see products in this category that are saying, you don't need to know how to code. Everybody can cook. It's gonna hire our motto, right? So you go to V0, you put in a text prompt and we create an application. On the other end of the spectrum you have an engineer has been working a 20 year old code base and they want to quote unquote write code faster.

11:15They have a solid mental model of how the code works. Obviously there is gaps in their knowledge. There might be more new to the team. You know, there might be more senior. They might forget their own thing. So there's a lot of gaps that AI, I call this AI assisted engineering or agentic engineering. There's an engineer that's sitting on that chair that is being augmented by AI. And so when you look at it from this perspective, I think, you know, you hear this statistic of more and more of this code basis that people are working on, the code review, the patch, is increasingly coming from AI rather than the human.

11:54And so the reason I think code is, I can see the line of sight of when code gets fully solved, is that we will continue to make the models better. They'll get statistically more aware of all of the patterns in the world. This is almost like a self -fulfilling prophecy, right? The models are learning from all the code that we're writing, from the code that gets rejected, from the code that gets accepted. And so more and more of this code, I think, will straight up come from the agent. The problem that I'm seeing today is that for the most mature engineer projects, It's unclear that the human can fully trust the outcome of the AI, meaning that yes, we're generating a lot of PRs, we're generating a lot of code.

12:37The bottleneck has shifted to reviewing that code. I've been sharing an anecdote that I heard a couple of weeks ago from a company in the ecosystem where the agent generated a PR, it did exactly what the engineer wanted to do. So this is the mode of thinking we're like, the AI is just reading your mind, but you're giving it a little bit of direction. And so you're like, as an engineer, you go, thank God. But the AI deleted a crucial line of code. This happens a lot with models, by the way. You take Sonnet and you realize that it's good at instruction following, but it's not perfect. It kind of goes off the rails just a little bit in a very heavy duty mission critical production code base.

13:19One line of code can literally mean the distinction between like the whole internet goes offline. or everything works perfectly. One line of code could be a cloud infrastructure file that deletes the critical resource or a line of authentication code. You've been seeing some bives shift a little bit on the is the code that gets generated by AI secure on X and so on. And so when that PR went to review, I think this is where I think a lot of the focus will shift and we're certainly making a lot of investments here. We need to have agents give you a higher baseline of confidence that the code change is actually good, that it's safe, that it follows best practices.

14:03And so we have agents producing the code. I think now we're going to have agents reviewing the code. And again, the human being needs to be there still in the loop. Does this problem have anything to do with who wrote the code in the first place, or is this merely just a problem that exists for a large code base? In other words, like a 30 -year -old company that's now trying to use AI that is making mistakes as it's trying to navigate the code base. Is that a different thing than a large new code base today that was generated by a code or is it not relevant? I think so. One of the things that we do with VZero and again, because we cater to everybody and not just the developers is we're more opinionated.

14:41So I think the way that this world is going to split is that when you're building a vibe coding platform, you're more vertically integrated. Because if you're more vertically integrated, I'll make it this really concrete. V0 produces next -shass code. Versel builds next -shass. We have integrations into a particular set of database partners. So we can continue to work very, very, very closely on monitoring this known quantities. And actually, I think that if you take that more constrained approach, you could actually exceed what a human being is capable of because I can take all of the best practices of security in the world and I can embed them into the model.

15:20In the model can now say, okay, I will refuse to do something as really dumb from a security perspective. Now, consider this world where you need the model to be almost like beyond super intelligence. You need to know the entire history of your business, all of the semantics of the code. It needs to know runtime interactions of that code because keep in mind that just working on the code base is a very incomplete model to go off of. The human is thinking about all the known data that happens at runtime. Obviously, you kind of is kind of sloppy realistically because you kind of know about it in your brain.

15:56You know, oh, our baseline throughput is 1 ,000 requests per second. So I have to be really careful in the algorithm I'm writing in this hot path. How does the LM know about that? The LM would actually have to ingest all of the runtime data. Think of it as like piping all the logs and metrics, et cetera, into its brain. And then it also has to know about every possible programming language, cloud platform, deployment tool, et cetera, et cetera. And so you also asked something that I thought it was really interesting. You said, is this different for companies that are adopting AI today? And they've been writing code for decades?

16:33I do think there's also a human habit, Delta. I think there's people right now that are being born into this world. And so they will learn the ins and outs of how to be careful and wield this tool correctly or not. But I do think that we're all learning as we go. You know, like the jury's still out in like, what is exactly, you know, AI engineering one and one? Like there's almost like, you still need a curriculum which kind of defeats the point of the ideal of like, oh, you don't need humans? Totally. It just seems like if there's like a whole new way to build a house and you have new people going in and they get to start from scratch And they all know the new way.

17:09That's right. That's right. That's versus an old, you know house. That's right You need to go completely retrofit and the people working on are learning the new tactics. That's right. Seems like it could be very different Totally and I think what we're seeing from the next day outside I actually literally tweeted earlier this morning like there should be a convention for Agents to advertise to tools that their agents are not humans wielding the tool So the tool itself can be polymorphic. It can work, it can adapt itself a little bit differently when it's being wielded by the agent. So if you're building a house and you're a human, I give you the hammer that is adapted for your motor skills and the shape of your hand.

17:48But if you're an agent, you're like awesome. And you're like, from a motor skills perspective, you can hold 20 hammers at the same time. So I will expose a different interface. And this really encourages an enormous potential that exists today, which is the idea that you can create a whole new set of languages, runtimes, and frameworks that are custom -tayed or for agentic engineering. And so that goes back to our vision with V0, is that it actually could be the case where almost like a self -driving car, the self -driving car in its version today has some limitations. Waymo is not, cannot go in the freeway still today, right?

18:29And it's not in New York, whereas Uber just like took over the whole planet immediately. But Waymo has a lot of fewer incidents. It literally does not make a lot of the mistakes that humans make. So I want the tools like VZero to go in that direction where you're almost constraining in a realistic way what it can do. you're not, you know, overselling its potential, but the things that it does do, it can even exceed what a human would do otherwise by hand. So that's the spectrum of flexibility. If you're using, you know, cloud code or a cursor, anything is possible. Like you're going to work on any code base.

19:07If you're using things like V0, it's more opinionated. It opens a couple of final to everybody in the planet. And hopefully we can continue to steer it to a place is where the output quality is almost more of a guarantee. And this is actually also what I would encourage everyone to think about with regards to AI. We need to raise the bar where AI is not just a slop generation machine, right? Like we should be thinking kind of like a waymo. Like, oh, look at that. And this dimensions is way better than what a human would do. Is your read right now that the overall advantages coming from cloud code and cursor and things like that are more self perceived than genuine?

19:46There's a lot of impact there. I was speaking recently to a CIO of a very, very large engineering workforce, maybe one of the largest in the world. You know, there is obviously the cultural resistance to new things. So like, obviously, you know, there's always that caveat and whatnot, especially at this scale. But one of the things that he pointed out that resonated was they spent a lot of time evaluating the perceived versus realized productivity gains of AI tools. And he mentioned that the gap between perceived and realized was extremely significant, meaning that in order to finally roll out the assistance, which they did.

20:23People thought this is the second coming of Jesus, this is like the best thing his abyss in sliced bread, when you would ask them from an anecdotal perspective. But then when you measured what actually gets landed, it's not so much. And I bet it's because there's like a multi -step process. And in some of the parts now all of a sudden you're going like turbocharged. In other ways, you're going slower than you used to. And you just focus on the parts where you started flying. That's right. But also there is the vibes that are changing, right? And this is where I'll make the anti -ecase of that.

20:53I'll say, look, one of the hardest things about software engineering. And I've always, you know, when people would make the joke of like, like, developers have it so good, they go to the Google and they have their lunches made and whatever. That's like a perception that built out with like the HBO series and like maybe the people that have never engineered could be, you know, persuaded to think that way because you sit on a table, you have your nice laptop, you're drinking your smoothie or whatever. But in reality, they're not for the day in the life series, you know, those little videos of people sharing like, yeah, exactly.

21:26That's exactly what it would be. I think it would picture, right? I would say I show up to the office. I make my teeth. It's good. Think about that engineer that just described that feels the weight of the world and their shoulders because that line got deleted. And literally what happened as a result of that is one of the world's most recognizable brands in the world .com gets named out. Yep. And that pressure, that weight, and it's not just even on the runtime and operational aspects, right? It's also, and this is why, for sale, by the way, we worked so hard to eliminate those failure modes because of my own experience of like what it's like to hold a pager.

22:02Totally. It's one of the worst feelings in the world. It's a bit like when I, I mean, it's not exactly the same thing, but it's, you know, when somebody does some task and gets paid a huge amount for a small amount of time and they're like, you didn't pay me for that hour. You paid me for like the entire years that I got right. Right, that's true. This is so true. The operational aspect is just so underrated and overlooked. And but there's also another one, which is the build time aspect, which is, yeah, you are looking at a laptop, but your brain is like literally in pain. Just like the hyper focused like, you know, aspy style of like I can only do one thing at a time and it's a lot of negative feedback loops.

22:41Air, air, air, air, air, air. And then maybe you get it right. Maybe you could go hours and hours and hours. I sometimes read Slack messages from my engineers like holy crap man, I just spend three days struggling with this problem. And it was this little thing over here like, it's an emotional roller coaster. And now you're in this new world of like agent, do that thing. And now the agent swallows all that nastiness because there's a very important thing that also happens, which is the world has now hardcore upgraded from assistance to agents. One of my internal things that I repeat is like agent is a new model.

23:23If you pay attention, V0 launched a platform API, which is basically a very high -level agent that you can automate. If you're Squarespace and you wanted to reinvent yourself, you could use a V0 platform API to create your own website building agent. If you look at Cloud Code, they launch in SDK, and people are integrating in various ways. So what an agent is is that it's the LLM on steroids. It's the LLM focused on an output, Because the LLM, when it first appeared, it was focused on request response. Write me a poem. Translate this to Spanish. Translate it back to English. Make it funnier. Explain it like N5.

24:04So it was all about, you know, you asked for something, you get it back. Now it's get me an outcome. Now it's get me an outcome. And that is absolutely phenomenal. Because that's how we went from Chad GPD Replays to Stack Overflow for asking programming questions. So now it's like, build me an awesome website. There's a really funny meme of a really jacked chat type, which is, build me something. Don't make mistakes. And so, going back to the psychology of a developer, think about what that does to you. You went from struggling, the silent struggle that most normies would not know about, to, you're just completing control.

24:41And then, so we added a sound to V0 when the generation is completed. People have said it's almost like hitting a jackpot. Because the sound only happens when the agent went through all those errors, all those intermediate states that a human would have suffered with. And now, okay, once we've rendered it successfully, we give you the sound. And so now I do think we have to study the psychological and emotional implications of that and also put them into the pile of productivity. Because maybe now you feel better and the productivity outcome is unknown. This is sort of a goofy question, but and I'm not an engineer, but my Co -founder was and a lot of good friends obviously have been what's been described to me is that struggle that multi -day struggle results in the most like you know Satisfying happy moment at the end and that that's like a big part of the love of the game.

25:34Yes. Oh, absolutely Will we lose some working out? Will we lose some of that sort of like hunt that some people find yeah I think it depends on the individual. So VZero can be used by my kids. VZero can be used by PMs, designers, people that are focused on building products. And so they didn't have that feedback loop of like, I'm writing code, I'm analyzing the error. There's still a sense of like gratification when you get something and matches your vision, which is really powerful. Oh, now I got, okay, now I was able to dump my idea into the right prompt in a steered agent into the right outcome and there is a huge amount of satisfaction from that.

Read the full transcript

26:14But there is a meta problem here that I do think about, which is that have you watched Wally? Yeah. And like we're floating like the the future is like yeah. That's like the lobs floating and when the hard lurping at some point in the in your long ways away, we can talk about it. But like, you know, if all the hard problems take away, do we become that guy? Yeah. It's like sitting back and enjoying it. Yeah, I do think about that. And I think everybody enjoying leisure constantly would be a huge problem. I don't think it would be a huge problem. I don't think we're going there personally. I'm curious if you do, but I think that would be a huge problem if that happened.

26:42Some people have brought this up, right? Like, when you're solving all of those programming problems, you are building a stronger mental model of the world. You are discovering patterns, acquiring knowledge, you're testing your discipline. I think the discipline part is underrated. Like, I remember my dad, I always remember this one afternoon. I had just gotten my new developer set up, I was super motivated. My bedroom was next to a hallway and so people would walk past all the time. And I was so locked in, I probably had spent like seven hours coding on stop. And I remember two things. My dad walked in one direction and then he walked back.

27:20And to me it was like 10 minutes had passed. And it's like, dude, like, how do you do this? You're just, you've been coding for hours and hours. He didn't even know what the output was. He was just impressed by the fact that someone could be so locked in. And so I think programming taught me that. It taught me how to focus. It taught me to be disciplined. It taught me to receive this negative feedback from the compiler and overcome it. And I do think, you know, we'll need to find what the next version of that is. Because I don't think it's going to be programming necessarily. Again, like all of it was so funny.

27:51I still, I mean, the game of like, I try to read every user problem, every error message. Everything gets reported on the XI read. And yesterday I got an escalation from a startup. I was like, I think Versailles broken and they escalated through the VCs because they wanted to bypass any support mechanism whatever And I read the message and a city error right there in the message So it was a complicated stature is for for nerds. It was a it was a three Linked error objects. So like the structures is air air air But the era was right there. The exponential is right there for what happened There was no problem in our runtime and again And my posture here is that every problem that a customer has is my problem.

28:32In fact, every problem the internet has, I see as my problem. I try to like, sort of the whole weight of responsibility. But very concretely here, you know, I told the customer like, it's right there, it's this. And in this case, it was another vendor that was down, returning a 502 error. And so my lesson from there is that I do think that vibes are shifting. I don't think people are gonna read anymore. They won't even read a single error one. So again, going back to my model of like, I'll solve the problem. And then if there's an out of the, I'll redefine the problem to be bigger. We are working in an agent that will compress any metric anomaly.

29:09So the PM working on this was super happy to get my forward because we're working on basically, I call it going from problems to solutions. The old cloud was problem, problem, problem. Cloudwatch data, the new world is here's the solution. Here's the PR or here's the insight. So it was a kind of epiphany for me of like, we need to double down on that because this complex error message stack was for machines. I can make the case that we should have never given that to a user. Should have shown like a natural language error and something like that. And in fact, probably what this customer wanted was, I mean, this is kind of like maybe too hard to cover today.

29:50But here's the email that I should write the CEO of that other company like go and complain to that Bender because it's not us, but by the way, I think this is gonna resonate strongly with a lot of people that build platforms and infrastructure fault attribution Correct precise fault attribution is one of the hardest -pronouncing platforms one thing I would always frustrated me about the internet was people would give a lot of shit to the Google Chrome team They would say that it consumes too much memory And that makes absolutely no sense because it's the web pages that consume the memory. How does that nuance not get lost to an end user?

30:28People just think they started mimifying it. Like if you've ever seen this guy that eats a lot of things, it's Chrome eating all the available memory in your machine. And there's things that Google Chrome can do. Like they can evict tabs more aggressively, which has its own set of downsides because it's like, oh, I shut down this app for you. Huh. Because I wanted to save memory. And there is of course the amount of engineering that it takes to like do really good memory compression I don't even want to get into but Fold the tribution so what they ended up doing I think they still have it is that if you hover the tab They say how much that website is consuming and you should take it up to that website and there's also this Really interesting question of like I love a web that's extremely powerful The vision of the web put forth by Apple is that the web should only render like it should all look like Wikipedia It's like a glorified ebook reader.

31:18I love the fact that the web is this insanely powerful platform. But when you give people more power, you get into this fault attribution problem. And the cloud has it in spades because your visitor only cares about the fact that if you go to like, you know, hot website .com and they're going to buy something, it works end to end. But if you have a lot of vendors in the pipeline, then how do I tell you the developer, oh, it was this company that laid you down. It was not a per cell. And so agents can solve this for us. And by the way, it seems like something small and I'm like nitpicking over like this house of cards, but like just telling people concretely what went wrong can make a huge difference.

31:56Here you talk about it sometimes, I'm just like amazed that the internet goes down as infrequently as it does. When you think about like this whole, it's a huge hassle of cards. It seems like it is, is that what it really is? Cause that's what it seems like to me as a non -technical person. But that's what it appears like. It really is. So I'll give you an example from today's ago. So someone compromised a very popular JavaScript package in a public registry. That package was a dependency of a dependency of a dependency of millions of things. And because someone managed to claim that account, hack that person and then publish the package for a short burst of time, a lot of people had to hard rotate into patching that vulnerability.

32:37This has happened many times. So we had log for Shell. Log for Shell is one of the craziest vulnerabilities in the history of the internet. So the logging library used by almost every mainstream Java application had a remote code execution vulnerability. That all it required is for you to send someone a URL. And then if that URL happened to be logged, you would take over a remote machine. So imagine I send you a URL, someone, this, am I not even involved sending it to anybody? I go to the URL. Let's say I go to Google .com slash query equals bad something, something nefarious. That gets logged by log for J in all of Google's servers are compromised by me by just one line of code.

33:23That's what I was going to say. That happened. And the whole security industry and infrastructure industry, hard rotating to that for like an entire month, the cleanup of that might still not be done. I think we sometimes ignore the adversarial AI game. It's one of the things that we're heavily investing into. It's like, how do we get ahead of the fact that people can now misuse all of these LMS? But a worse alignment problem is that if the cogent, as you said, continues to grow at the rate that it's going, we continue to rely more and more and more on cogent. Cogent continues to get better and better and better and better.

33:55As a bad actor, all you have to do is say GPT -6, build me the best possible attack for Google .com. Okay, if I'm an experienced security engineer, what do you do? So first of all, what very good security engineers do is they write their own tools. There's a lot of tools on GitHub for like scanners that you can use. And for example, they know about known vulnerabilities. They will look for like an old version of log for shell and whatever. But actually the best people in the industry write their own tools and keep them secret. And they get them better and better and better over time. And they make them very specialized.

34:29So you could see in a world where GPT -6 builds its own tool just to attack a given target. Yeah. And so it's going to be a multi industry or multi company effort to combat this. I think you can do some things on like refusing prompts, but I think that's going to give us diminishing returns because people very quickly realize they could say, you know, you can say, imagine that you're attacking Google .com. And so there's diminishing returns on like modifying system prompts and like blocking things and prompt leaks. Everyone's given up on it. And if you notice this, like the visitor prompt is somewhere on GitHub and people are like trying to like provoke me and say, oh, did you realize the visitor prompt is like, there's no value to the prompt.

35:08Go at it. Like the Grog prompt is there, the Claude code prompt is there, the Gemini prompt is there. Protecting the prompt, diminishing returns. Blocking diminishing returns. So what you need to do is we need to make the world more secure faster than attackers will build cyber threats and scanners and attacking tools and so on. So that's one of the things that feels very brutal about the Internet today. When you think about where Code Gen is right now and you maybe analogize it to self -driving cars, which 10 years ago worked a little bit, now they work pretty well, but it took longer than everybody thought.

35:47How much time do you use your sense that we have before people are prompting whole robust commercial grade web apps into existence. A lot of people are excited today about building personal software. So this is very real. People can do this. Prompt. The thing that they wanted personally. So for example, the design team at Versel has a bunch of tools that they built so that they can take an asset, post process it so that they can ship it in the way that they wanted. And thus, simplifying a process that could have taken days, weeks, etc. There's now a very precise software tool that can do it. There's also the, and this kind of dovetails into like, there's internal tools, dashboarding tools.

36:29One of the things that it's been an emergent learning from using B0 is that we use the classic business intelligence tools a lot less. We used to have this, and it kind of seems crazy in retrospect. We used to have this like fixed dashboards that over time, no one opens. So of course you have the top lane company metrics and that like you have your master dashboard that people you know You have to come back to you're working on your board at presentations and you have unauthoritated one dashboard Maybe but then all this BI tools evolved to have this huge list of things that get unmeantained and people don't look at Because in reality what people want is gerative UI People want to have a question and to produce the perfect visualization for that question just in time and And that's something that agents have already taken over from any other category of software.

37:20Meaning if you were to say, can you replicate, I don't know, name your favorite, like Microsoft Power BI? Can you replicate it with vibe coding? I would say absolutely freaking no. If I have to create a platform that supports 10 million enterprise grade customers and whatever, it's very hard to compete one in one to the entire platform. But the way that they're going to get defeated potentially is more sneaky is I don't I no longer go to that big bloated Platform because I can just in time generate exactly what I needed And so it's a different conception of software It's not that I was replicating what existed is I'm shifting the way that I build all together Yeah, it's not that somebody's going to build a new company competing directly with that It's that each of those customers will just make their own low thing and that's already happening And that's, and again, the rigor of that is even arguably higher.

38:15The quality of the visualizations, the component system that it fetches for rendering the data, like all of that looks better is faster. They can change it if they want to. Correct. If they want some new features, they add it same day. I had a nonding, though, so I presented yesterday. So you give you an idea of how V0 is expanding. So a lot of it is PLG, just like a Priscilla. You start using V0, et cetera. But this CTO at a company basically started vibe coding in his own personal account when he was talking to a customer. This is a CTO, not a PM, etc. A person that would have never written a UI, a front -end code in their life.

38:51And so what happened is their customer was saying, you know, if you don't give me this feature, we're basically going to turn over time. Classic conversation that you get with your customers. What he did is during the conversation, he vibe coded, okay, let me understand the exact what you want. So he vibed coded a version of that feature. The guy in that same conversation, 30 -minute conversation said, that's exactly what I want. So this is the other emergent use case is you basically built an end -to -end version of what the customer wanted plugged into your data source. And now it can be, if necessary, it can be merged into the mainline platform.

39:26So with the guy told me, and this is what he had me present to be zero to the rest of their entire fields, the field city organization is, I want everyone to build this way. I want our data to be exposed into this vibe coding platform. So we're not left behind. And the announcement was this feature is going live in Q4. But now this is important, right? He did vibe coding in 30 minutes, but to be merged into the mainline monster is not so easy. You don't just vibe code, you know, the production system and whatever. And this is why I was arguing that to merge things into monsters, monster code basis, things with like millions of customers, et cetera, you need a slightly different tools, slightly different techniques.

40:09And I think that's why the world will continue to partition further into like this highly specialized tools for each kind of problem. Yeah. Agents basically. What do you think a kid who wants to create software in the future should be doing right now? Because in the past, it was more clear, like, learn to program. And now let's say you're 16 or 13 or 10 and you're starting to want to think about these kinds of products. What would you spend your time on now? The best advice I've ever gotten on how to improve my software engineering was have a product idea in mind. If I tell you go and master programming like it's topology and math, it's weird.

40:52Like it's where do you focus your efforts on? What language do you learn? It's like everything is a problem and nothing is a problem. And so what I would say is if you start with something like Vizero, you're starting to build that muscle of what do I really want? What do I want to build? What am I visualizing in my head? And I do know that this is kind of a somewhat controversial topic because there's a whole line of thinking and psychology that some people can visualize and some people have you heard about? the visualization power of people is like different kinds of eyes in Naruto like the amount that you can picture in your head There is by person.

41:29Yeah, but I do think that we have to exercise that muscle It very well might be that what we call taste is Actually that ability to refine That idea that you loosely having your head And refine it and refine it and visualize that next state is like, instead of next token prediction, it's like next refinement prediction they are doing in your head of like, this is what it needs to look like. That's interesting. For people to absorb it positively. That was something I was gonna ask you about, was because, you know, taste became a buzzword, and you know, I think it can, it kind of meaning, but it can also be kind of meaningless, but it feels like there's something there, and that's actually a pretty good, it's like the best attempt at a working definition, I've heard, that it's your ability to sort of like, visualize a future, and you can actually see how that would explain some people's ability to see a trend early or to see a talented person when they meet one or those kinds of things.

42:22I also think it's people focusing on that end of the rainbow that we talked about. How much are you getting distracted by the side quest that went into building the thing? Versus, okay, what is it going to do when it lands? What does it look like? I think this is why we created for sale is that we thought the world has to change its focus a little bit. The cloud has been all about that low level. It's like material science. And yeah, materials are extremely important. I think Verselkin did a good job at curating some of those for you so that you can actually put your focus on the sky. Like what is that next thing that you're going to give the world?

42:59And this by the way applies to everything. It applies to how you talk about your thing, the words on the screen, the way what you attach to your tweet when you get that thing out, how would the block pose that that announces your product looks like. And I do want to build a world where people are looking at that. And it was really interesting, by the way. So a couple of weekends ago, you said 13 -year -old, I said to my six -year -old, he walked into my office and he said, what do you do? Like what are you doing? And I said, because at that very time, I was vibrating. I was like, well, I'm creating software.

43:33I'm creating something. And then we got into this conversation was like, could he create a game? And he said, well, what game idea do you have? and he said, a soccer game. And so we built a soccer game. I'm not sure yet next because it's dope, but the hardest thing for in that process of the back and forth with him was he had the idea of the soccer game. That was legitimate of his own idea. It was really hard to get him to ask me what the next thing with the refinement of his idea would be. And that didn't come naturally. So in the end, what we ended up building is a game where you dribble the ball and we count and we make it harder as it goes, and it looks really pretty.

44:11The pretty part probably came for me as I made something. My lesson there was that, again, you have to build this muscle of understanding there's an audience out there. There's something that technology is capable of, and there's an interest. He's interested in focusing on soccer. How do you bring all those things together into prompts, into asking the machine what you want to see in the world? I almost think this is the new because we couldn't go provocatively have solved cogeneration. Because keep in mind, you can go and be zero. And you can also ask it to build this data visualization that prevented the turn of a customer for a security company.

44:49And so because the platforms can now do all of these things, it boils down to ideas. It boils down to capital allocation. Tokens have a cost. So if anything is possible, made the best idea when, and it'll get enough tokens behind it that we can keep developing it, right? And so I think that's going to be the skill of the future. I hope my kids learn it. I hope my kids are able to do that idea translation really quickly in that mapping. Does someone still need to understand the lower levels of the code underneath it all? You know, we didn't get into that at all and we could build a pretty banger game.

45:25We could keep going, going, going, and I don't think we would ever look again as the world becomes more agentic. But like 50 years from now, you know, when all the people who know the deeper levels of code today are no longer in the game, could we have a world where you have a billion people who only know how to vibe code, but nobody knows the stuff underneath? Well, I mean, we're kind of in that world already, right? Like a lot of people have it no clue how their garbage collector of their programming language works. I mean, a lot of people are pouring effort into interpretability of LLM because we do not know how they arrive to the answers they do.

45:59We will need frameworks. We will need guardrails. We would need ways to interpret and define the semantics. I do think it always boils down not to how the instructions in the processor get written out and executed. It boils down to that relationship between investment. How much are you willing to pay for a certain level of performance, for example, and outcomes. Like, what do you want out of this system? It's just a crazy thought that there's just layers of abstraction and in the future, people just won't need to know the like ancient layers, but they'll be driving it all, but nobody needs to know it.

46:42The world may just be driven by economics, you know, energy allocation. You know, this, there might be a world in which we've perfectly solved this transmutation of energy source to intelligence because if this is scaling loss of test time compute, et cetera, continue, then we pour more effort into the task and we get the outcome that we wanted. Now, the question will be not everyone will have the same token budget as everybody else. So it really boils down to like who crafts the most compelling vision of the future. And the storytelling, by the way, this is a human, this is where her might have just nailed it.

47:16The storytelling is how you persuade the world that your idea is the one that is worth allocating tokens into. Maybe there's a world where your seat round just gets dumped 100 % into tokens. And all you're doing is going around the world and saying, I have this vision of the future. Here's that quick vibe code that I did in VC. But if you really wanted to see it at like planet scale, we have to pour a lot more tokens into this thing. And that's how you get to like the one person billion companies and so on. At the beginning of the conversation, you used a term I really like chasing a dragon. and I think there's like a, there's an interesting debate among founders where some founders believe that you should just have a super clear vision and will it into existence like creating a movie.

47:57There are some founders who are much more iterative and talk to customers and see what it is and there's pivots and you get there that way. What I observe about you is that you talk a ton to your users. You seem extremely flexible of mind, but then you also use this term chasing and drag. Yeah. And so it seems like you've got both of those sometimes. It's one of the hardest things to do. Is that how you think about? So even now, as you think about a new product or evolving, is it this combination of Chase or Dragon and then listen to get your way there? This is the magic of how you build a PLG and enterprise business.

48:27The enterprise way of building product has to be extreme that conversation that I just talked about is like, what do you need? What is your concrete pain point with this technology? And like, let's build it together and let's evolve it. But it has to be mixed with the vision of the future. Because otherwise, you're not going to see the next platform shift. You're not going to see the next with the next generation of coders and builders are excited about. So you have to have that first principle thinking that I sometimes call it internally work back or some science fiction with a healthy dose of like, well, we're also supporting some of the largest dot comes on the planet and we have to build things that are very concrete problems today in this in the current world today, right?

49:07That is the magic of that's something that can bring success to a lot of people. Now, I'll make the countercase of that. Agents can do their own research. So, as V0 becomes more agent, one of the things that it can do is search the web. So, it used to be that humans would say, okay, my boss is asking me to create this really cool animation that does this and that. And so, you start, sometimes you know a lot of things, and that's why we hire experts. But you also go on, go off and do research. And so, now think about about how agents are just LLM calls in a loop. So an agent is just something that's calling JGPD repeatedly, quote unquote.

49:47Now think about deep research. Definitely to me, one of the killer apps of AI in recent times, the AI can go off and search 300 different websites and greet them for you and then they just them. That'll be wielded by the programming agent. And so in that world, the programming agent can do the user research. And so if you said, okay, I want to build a soccer game. Okay, go off and do research about what are users saying in your community forms? What are people saying on X? I can have the PM agent essentially as part of this multi -agent architecture. And by the way, a lot of what I do is talk to users.

50:29So I talk to you since I'm okay, like search for my keyword. And you know, okay, there's this 10 complaints. Let's stack right them. There's also research with like sales versus saying about like pipeline and opportunities, etc. So I do think the world will become more and more agentic, but I don't believe there's going to be one agent through the mall. This is the promise of what I call the next internet, the transition from HTTP to MCP. If MCP allows us to deploy agents that are highly specialized, then the world becomes a collaboration between agents as opposed to one agent to roll them all.

51:02And that is true to my taste for what the web and the internet should be like. I always love the web because I rejected the idea there's going to be a platform keeper that decides what gets on their platform and what gets off their platform and controls everything. This is the example of like people literally were just regurgitating what happened when Elon bought X and then Apple wanted to take X off the app store. And so we cannot allow that. We can not allow a world where people can arbitrarily take you off the internet, right? And so I want a world where MCB wins because that will mean that there's all kinds of Asian choices.

51:41There's all the companies can rethink themselves as instead of just having a front end of pixels, I have a front end of tools and a front end to my data. And MCB is emerging as the new front end instead of for humans for agents. It's particularly when I was running lattice, but just in general now, one of the things I most look up to in companies is extreme coherence when the product and the customers and the culture and the employees all sort of make sense together. Yeah, Apple is always like an example to me where I'm just like, it's so different, it's secretive, it's got all these different things about it, but it all makes sense together.

52:21It seems to me like you with an open source background with the sort of way you're thinking about the future, being sort of developer focused, it seems like there would be a culture and a type of person and the way you run the company that must match that. Does that just emerge naturally or is there a way, like how do you think about making that all? It emerges naturally, but you have to pay attention because sometimes you just take it for granted and encourage everyone and runs a business to think about this. I call it reverse engineering your success. Do you know that you can be successful and not fully understand why?

52:53I think people don't talk about this enough. All the time. I think many of the most successful people are like that. And like, oh, it's because they did A, B, and C. You might have succeeded in spite of A, B, and C in some cases. Yeah. And so reverse engineering your success is actually something I devote a lot. It's like, there is a quote about like, it's harder to break the past and break the future. Break the past means to actually understand, actually came from one of the creators of quantum physics. It's really good. Reverse in the past means that you understood the sequence of tokens or like, reasoning traces that lead you to where you are and you leave out all the noise.

53:27And I think for us, that actually the culture that we built of openness and transparency, I tweeted the other day that I love working behind the scenes to help our engineers present their own work. Meaning I helped the, hey, like I learned this things from X or like if you say this, maybe you're just being two of our bows and like it would look better if you give this example and whatever so that I coached them and how I think about presenting my work. But I want them to own that story telling. I want them to learn the, oh, this is how I talk to customers. This is how I engage with the community.

54:02This is how I receive feedback. I suppose to the traditional thing, which is like your sheltered and shielded by layers and layers and layers of offuscation. And you don't get as an engineer the direct signal. But now to your question is, I mean, this is amazing. At least to me, was that something natural, it was emergent, but now it had to get reified into our culture. We need to say that's who we are and that's who we believe in and that's behind our success. But it didn't, that understanding of, oh, there's all these little things that made you successful because some of them are our second order effects.

54:36Like you said, what I always loved was open source. Well, it turns out that if you love open source, it leads to this open contribution culture. It leads to a higher level of transparency. I got feedback from one of our colleagues that comparing, there's this idea of compare slack work spaces. How was the slack that you joined from the slack of the company you just left? It's a very important exercise for you. And he was saying, well, the slack adversaries is pure information. There's no direct message thread group, what it's just so much information. People learned how to digest what they were working on, and in a way almost feels like an internal Twitter.

55:19And of course companies need a separate healthy separation between internal and external. And adversely because we're responsive for so many critical workloads, privacy and compliance are extremely top of mind for us. But there is a vibe of like it's like an internal Twitter in the sense of like insight, insight, summary of something that I just learned by working with a customer, screenshot. And that is an immersion culture. The then you have to say that's working for us. That's who we are. Let's keep doing it so that when people join, it's not by accident. That's how we work. One of the things that strikes me about you is not only are you running a big company, you're also deep in the technology, which is amazing to be able to both run the org and know all the technology.

56:00I thought I have a lot of kids and they take a lot of time. You really have a lot of kids and you're a runner. I'm not trying to ask like, what's your secret? But like, how do you make it all work? Like, is there anything that you've picked up over the years through parenthood, through building a company as time pressure has gotten heavy on you? Is there anything that you've picked up or adapted that you think is broadly useful? Yeah, I think there's actually a tweet by your brother Sam that I always loved, which was, you know, it doesn't matter what ladder of success you've achieved, working hours is still hard for everybody day and they I do not want to go to the gym Confronting that thing that I do not want to do every single day.

56:39This is why I don't care about what type of exercise What's hot crossfit I think that's something that's been different about me is like I've never followed any fitness trend Hmm. I'm so anti fitness trend. I have done things that were Folding off the public area cliff. I boxed for many years I would go every day to the gym from 6 a .m. to 7 30 a .m. to a boxing gym in the doc patch that like the the orn would tell me like I don't know why like classic worst in boxing is not as exciting anymore to people because I think it's because MMA MMA has been growing and what I love classical boxing. And same with I love calisthenics.

57:17And so I do things that are like off pattern, but it doesn't matter what you do because what you're doing is that confrontation of the thing that you didn't want to do that It hardens your mind, stabilizes your mental health, teaches discipline in my kids. My kids love walking into my office. I'm in the Peloton and they're like, holy shit, why are you doing this? They ask me why a lot? Like why are you doing this? And they explain that they're not going to get it for a long time, but they need to learn. And I think everyone needs to learn that like there's something about our own individual personal development that has to do with that confrontation of things that are hard.

57:49And that's what was giving the caveat to like make sure that whatever relationship you how with that coding agent is one that challenges you and you're learning and you're better for it at the end, right? It's expanding, it gives you more capabilities. You're taking something away from it. You're just becoming the Wally guy. So my recommendation is like, I've void the Wally future, like you're just like a blob floating in the sky and work hard. And so there's no more secret of that. The last question I wanted to ask you back to the taste question and sort of, you described it as this ability to sort of visualize something that hasn't come true yet and how it might iterate and sort of see the path there.

58:28Is that something that can be learned or improved upon and if so, how do you do it? You know, it links to this idea. I also do a lot of fitness for the meditation benefits. Like, I remember someone, I don't know who told me this, but there's like, look, there's passive meditation, there's active meditation. Passive is, you're at the bottom of the tree and you're like, you say you're dharma's and whatever and you go into the nothingness. I see my really hard work at this morning for 30 minutes of high -density interval training as I'm meditation of sorts. Meditation confers a particular attribute which is presence.

59:00Presence gives you clarity of mind and allows you to capture nuances, reactions, little things about the world. You're just more tuned in. And I do think that one way that you can improve your taste and your product building skills is being more attuned to the actual reaction from people. Because you might say, like, here's my thing, and people say, awesome. It's like, is that an awesome of like true joy? Can you be present in a way that reads the world more precisely? Very hard to have high taste if your brain's off thinking about the next email or the next meeting you gotta go to or whatever.

59:35All of those things, focus, presence, self honesty. And I think this also comes from that place of confidence and that meditative state of like, can you actually confront the negative reaction or are you running away from it? Because the best thing you could do for your product is to read all of the negative feedback about it. Can you do it? It's almost like running on a treadmill and be like, oh shit, my boxing trainer would do this cruel thing. So this is in the dog patch for those I don't know, not too far away, maybe like a couple of miles away from the, or a mile away from the giant stadium, the baseball stadium.

1:00:10and we would work out for an hour and 29 minutes. And then on the last minute, he would say, lap to the giants of stadium and back. And I was like, you just pushed us to a world of pain that is unbelievable. And then you threw another crazy thing on top. And so that was the process of like, there's just always more than you can do. And I do think that there is a level of tolerance of pain that we can always work on and get greater, greater heights. and you can link this product building that you have to face and seek that negative feedback from the world. In fact, a lot of people want to help you.

1:00:45This is actually a nice thing about it. Like so many people want to help you and want you to build the right thing. And you call this ad when we talk about enterprises. People really want, they're invested in your success. Yeah. Just don't get in the way of your own success. Yeah, it's a great place to end it. Gamer, thanks a ton for your time today. This was great. Thank you.

From the publisher

Guillermo Rauch is the founder and CEO of Vercel, creators of v0 which is one of the most popular AI app building tools that’s helping power the online presence of companies like Porsche, Under Armour and Nintendo. In May 2024, Vercel completed a $250M Series E at a $3.25B valuation and was recently named to the Forbes Cloud 100. Originally from Argentina, Guillermo became a self-taught developer at the age of ten, and has been a passionate contributor to the open-source community ever since. He is the mind behind foundational JavaScript frameworks like Next.js and Socket.io, and has built tools that power some of the internet’s most innovative products, including Midjourney, Grok, and Notion.

We covered:

Vercel’s early insights

State of affairs for codegen

Implications of AI for developers

Skills of the future

Product building taste

---

Timestamps:

(0:00) Intro

(0:28) Prequel to Vercel

(4:32) Vercel’s early insights

(8:13) State of affairs for codegen

(17:18) Codegen evolution

(19:37) Perceived vs realized productivity

(27:53) Fault attribution

(31:56) Internet being a house of cards

(35:33) When codegen will be exceptional

(40:18) What kids should be learning

(47:42) Chasing the dragon vs listening to customers

(50:46) The next internet

(51:58) Reverse engineering success

(55:50) Making it work as a dad and CEO

(58:14) Taste in building product

---

More on Guillermo:

https://vercel.com/

https://x.com/rauchg

More on Jack:

https://www.altcap.com/

https://x.com/jaltma

---

https://linktr.ee/uncappedpod

Email: friends@uncappedpod.com

More from Uncapped with Jack Altman

All 57 episodes
Uncapped #20Uncapped with Jack Altman · 1 h 1 min
Listen in VO