01 / preference
I love that it builds internal tools too, not just the front end.
“I love that it builds internal tools too, not just the front end.”
- Speaker
- Lenny Rachitsky
- Publisher
- Lenny's Podcast
Lenny's Podcast / episode intelligence
Speakers in the public record
Claim mix
Evidence policy
Every row below preserves an exact excerpt. Identified speakers are linked; unresolved voices are labeled and excluded from people counts.
Claim ledger
17 published records
01 / preference
“I love that it builds internal tools too, not just the front end.”
02 / recommendation
“We use Google Cloud. So we abstract all of that away from you, but we use Google Cloud behind the scenes.”
03 / belief
“Some people will figure it out by going to ChatGPT and Claude and asking questions and I actually am really inspired about how persistent some of our users are, which is really amazing. But I think you'll get an MVP pass, the MVP where it's a product that's working and you need to change and iterate on it.”
04 / belief
“Let me just actually double down on what you just said, which I think is really interesting.”
05 / belief
“We have a PM role. I think up if you're product manager. We're hiring engineers and product managers.”
06 / belief
“I mean, if you're really good, it might be hours but it probably would take me a few days. I would say I'm like decent engineer, it'll take you a few days.”
07 / belief
“I could keep going and going, but I think we should also let people go play with these things and process all the things we've been talking about.”
08 / evaluation
“Typically, you're bottlenecked where your ideas are not fitting in because they need to be made and they need to be made quickly.”
09 / prediction
“So can you actually build the next Salesforce if anyone can generate Salesforce? And then the question is, and this is why I emphasize being generative, because I think then the thing that will make you better is by being able to iterate and improve the thing really quickly and generate new ideas.”
10 / commitment
“We want to get to a point where the agent can go grab a human when it runs into a problem. I think that would be sick.”
11 / prediction
“I think a very important scale that's perhaps harder to develop but it's worth working on is being generative, being more generative, being able to generate new ideas quickly, because you can think about it as a factory line.”
12 / preference
“If you're at a big company, it's very easy to bring a new editor and start coding with it. It's quite hard to bring something that's quite opinionated about everything from how the code runs to how the code deploys, but that's the trade-off we're willing to make is like yeah, we're not going to get into the enterprise main software development pipeline, but we want to empower everyone to be able to build software, and that means product managers, designers.”
13 / evaluation
“I think people are unaware of just how far things have gone and how much is actually possible, especially when someone that knows what they're doing is using the product.”
14 / preference
“I think people are familiar with some of the more chat interfaces like v0 and others where it's purely chat, but this is a full IDE where you can go and look at the files and edit them yourself or ask the AI for an explanation.”
15 / evaluation
“I think where it gets really tough is that when you're hitting scale and you want to architect a system that is resilient, and so that means you would start sharding databases and you would start using different queue systems and components and things like that.”
16 / preference
“The most important model that we use is the Sonnet model from Claude, from Anthropic, and it is the best model at coding.”
17 / evaluation
“One thing that I think is really difficult now is having roadmaps, especially if you're doing anything in AI, but really anything that AI could affect, you want to be able to react to it really quickly.”