Sahil Lavingia: preference

Transcript context

…Yeah. I love putting it below the input. I don't know what this does, but for some reason, if I feel like I'm vibing with this person, like they know what I mean when I say note. I mean like slightly smaller font size, like gray, you know, like note. Like I feel like a designer would get it. So, you know, this is kind of like what I would give to Devin and... then it would it would you know run off and and do its thing it'll wake up and it'll do all these things all but all the stuff that i would basically do right open cursor get the thing find find the files that need to get changes but i personally one of the things i think is really really important is spending more time in v0 like i think many people just like they do a first pass and basically i think mvps are no longer enough like you can actually spend like 10, 20, 30, You're like, oh, now I have to think about this and that and this and like all these like little bits that would make the customer feel really good. The user experience would go up, but the developer experience would go down, right? But if you know an AI is going to be implementing all of that stuff and they're going to do it at like a very high level of conscientiousness, you might say, oh, by the way, redesign it to like have this or like, you know, different roles, for example, right? Like different roles have different amounts, show a preview in the dropdown. You know, so one may be like 200 an hour, one may be like two pay per project, etc. You know, one may be 250k a year. Just for fun, I might say like one may even have multiple pay rates because I've been exploring this idea venerally. And I think part of the beauty of not doing it yourself is the happy accidents. Like AI may just take your your spec and actually do a better with it than you would have. And so, yeah, that's kind of how I use it. And then I generally, if you're hosted, you know, depending on the projects, our newer projects are all Next.js hosted on Vercel. So they'll even give you like a preview branch, right? And I mostly love doing front end stuff with Dev. And actually now they have this pairing thing. I could actually go in and like run Rails console and like check the back end stuff too. But with preview branches, I love making changes to antiwork.com because I can test them almost immediately. I can be like, let's say a new person joined the company. I can just say, hey, add this person who joined the company. This is their motto. By the way, pick a fun icon that matches for them. I didn't pick any of these icons. I would not have made myself a king, for example. I just said, like, I basically just asked everyone in Slack, like, tell me if you want it to link anywhere and what you want your slogan to be. And then I asked Devin to actually do it and pick an icon for each person. That brings me to something I was thinking about, which is when you were in V0 and you were asking it to add on features, I was playing the product manager in my brain and I was thinking, oh, in past lives, people would say, no, that's scope creep. We're just focused on the date picker or we're just focused on updating this component. We can't kind of scope creep and add more and more features. And what I think is interesting, I'm curious your point of view, is you can really start to go to the edges of some great user experience. And it's less about how much time will this take? Or is it too complicated? It's more about what's actually going to work and be useful.…

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