software engineer

“Like next, next token prediction is going to, is getting you surprisingly far. But I don't think it's gonna get you all the way there to like replacing, you know engineers at big companies.”

“And I think over time, like I increasingly think that basically, especially because of the capabilities of these AI models, every software engineer will need to become an ML engineer and a data engineer also. As they build their application and we'll, we'll fi…”

“There's a lot of other ones where the job of the software engineer and product manager and designer is going to shift from prescribing the how to Prescribing or describing the why and the what and the goal, and we leave it to the AI to figure out stochasticall…”

“I think we both realized that we're spending a lot of our time in the process of reading and understanding the existing code rather than building new features. Cause all that is a prerequisite for Being able to build quickly and efficiently.”

“I think if anything, there's going to be more engineers, not less and I'll kind of give two reasons why. I think the first is there's just so much demand for engineering out there and so much demand, honestly, even in ways that we don't always think about, rig…”

“I think the average software shares today might spend 20% of their time thinking through all these, like, really fundamental problem solving questions, and 80% of the time writing that in code. And I think they'll, they'll be able to do five x more, and they'l…”

“I think the role of A software engineer five or 10 years from now, it looks something like a mix between a technical architect and a product manager today, you know, where, where a lot of what you do is, you know, you take problems that you're facing or that y…”

“The most curious software engineers are actually fundamentally lazy at heart, right? Because you're trying to find ways to, like, you know, build the meta solve to, like, solve the thing that you're trying to do, right?”

“So I, I'm very bullish on software engineers. I think it would take a lot to sort of destroy that demand. I think people look at a lot of like AI as like a kind of fix something, but in my opinion, it's like, No, it's just gonna unlock more latent demand for m…”

“Every time that's happened, you know, It turns out like there's so much latent demand for software that actually like the number of software engineers goes up. So like, I feel like you look back at like, you know, last like four years of software development, …”

“All the things that go into making a good software engineer, that's gonna be really hard to do. Like, I think it's going to be a years long build out for even some of the verifiable domains. Cause there's so much that goes into a good software engineer of like…”

“When you look at what an engineer does in an organization, 80% of their time they're spending trying to comprehend complex systems and collaborating with teammates.”

“The best engineers I work with today are not fresh color strats. They're people with, you know, 10, 15 or more years of experience, but they're also really on top of AI tools, and that, those engineers are just completing a class of their own.”

“I think we're going to see a lot of these really great engineers who care about the bespoke craftsmanship of everything they do. They're going to be unhappy working at larger companies. As these coding tools get even more. Accelerant because it goes against th…”

“I think that fundamentally you know, there's so much demand for software and there's so little supply of engineering and reality relative to that demand that as you add this enormous boost of productivity to software engineers it just gets soaked up. Right. Be…”

“There's all this stuff about there being less software engineers, and I think we just build more software. I think we just build a ton more software”