High Signal Podcasts Evidence ledger
Method
Browse
← Back to evidence

Evidence receipt / evaluation

Published · transcript-backed

Anton Osika: evaluation

9 Mar 2025 Lenny's Podcast Building Lovable: $10M ARR in 60 days with 15 people | Anton Osika (co-founder and CEO)

“The engineer skill set is still going to be important because that helps you understand what are the constraints, so what you can build and I just think a lot of software engineers are probably a bit scared now like, "Okay, am I out of a job?”

— Anton Osika

Source trail

Everything needed to verify it.

Speaker
Anton Osika
Attribution
Verified speaker
Claim type
evaluation
Recorded
9 Mar 2025
Publisher
Lenny's Podcast

Transcript context

…What's interesting about this in one way is people wonder just what jobs will be more important, what skills will be less important? Let me share a thought I have and then I want to get your take and see where you go with this. It feels like what is getting more valuable is being good at figuring out what to build and then knowing if the thing you had built is correct and good and ready. So it's like discovery, ideation, idea, part of the step of launching a product and then it's like taste and craft. Just like is this the thing? Is this going to solve people's problems because the building now is being done more and more and it's interesting, it used to be the reverse engineering was the hardest, most valuable skill and now it's figuring out what to build. You could sit there and you could just tell it what to build and a lot of people get to your screen I'm sure and they're like, "I don't know what to build, I don't know what people want." And it's like that's the thing now. So just reactions to that and thoughts on what's skills will matter more and less. I mean if you're a founder or you want to build something. Yeah, I totally agree that figuring out what are pain points and seeing there are often currently solutions, some kind of solution to everything. How can you make this 10X better somehow figuring that out is super important when you have an existing product. Then I think taste and tasting what is good is even more of the important part. The engineer skill set is still going to be important because that helps you understand what are the constraints, so what you can build and I just think a lot of software engineers are probably a bit scared now like, "Okay, am I out of a job? What's going to happen?" But they should see themselves as the people who translate the problems that are stated a human, probably, to technical solutions, but they do have to abstract themselves up a few steps, not just looking at in their tech stack like oh I can just do the front end changes. Engineers or technical people are very good at understanding what are the constraints technically and they should see themselves as that translators. Is it almost like you want to learn the eng manager skill of overseeing engineers versus the actual engineering skill or you think it's still going to be really important to learn how to code and be really good at that?…

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

Search evidence