Guillermo Rauch: belief

Transcript context

…So let's go to this question of just the elephant in the room for a lot of people seeing these things happening, product builders that have been doing things a certain way for a long time with apps like this coming around, whether you could just type a thing in, and build it for you, and it's beautiful. How do you think things are going to change for product managers, for product teams? Where do you think the biggest change is going to happen? How do you think product will be built in the next few years? The most profound one that I alluded to is that conversations between product builders and their customers will be mediated by these zero links, these artifacts. I think when Claude came up with the name artifacts, I found it phenomenal, because we're all in this world, especially in this group of people, we're here to build awesome things and share them with the world. Steve Jobs said this awesome speech about, "It's like our form of giving back to the world is to try and do the best possible job we can and share it with the world." And so the idea that when we talk, we would not have the power to make those ideas a reality, it seems like an L to me. I would love to see people constantly live in the product, be in the design, spend time tuning and trying out new ideas. And that's what the ideal work of the future should look like, and less about again, that abstraction, that being removed from the product or even sometimes I can feel powerless to not be able to change something. This happens a lot when departments collaborate within an organization. Marketing wants design to do something, marketing wants engineering, engineering needs a design. It cuts always. One of the things that people got excited about that we published on the Vercel blog was about design engineering, because a lot of the people that we were noticing were being very successful at Vercel were people that had both the design and engineering skills. And that was actually another huge motivator and inspiration for v0, because we realized that people could be more full stack. We shouldn't put limits on ourselves, and what we can build, and what we can ship, and what we can dream about making possible on these web surfaces. And so you could imagine removing all those limitations, a designer that can ship a fully-baked product, a product manager that can prototype and shift to production. A lot of people that use v0 are back-end engineers that never had the ability to, they could ship an API, they could build a great low-level infrastructure system, but to actually bring their end-to-end vision to life, v0's completing that for them. Let me follow the thread on engineers. A lot of people are wondering, "Do we need engineers in the future? What happens to engineers? Should I learn how to code?" Your long-time engineer thoughts for folks that are trying to decide the career for themselves?…

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