The hosts were discussing a conference talk in which a well-known framework author said he no longer reads or writes code himself. One co-host doubted the industry is ready to stop reading code, and this was the reply.
…it's, it's not like just one prompt, but you can certainly get there. And the need for abstractions and the need for actually reading the code and having it beautiful and look beautiful and all that stuff is is not as necessary anymore as as much as that is a bit of a gut punch to a lot of people.
…produce and now they're easier to produce. So, you know, needing, needing the types of things that we used before, you know. Oh, what was this one thing about Ruby was that, you know, Ruby is the language of his dreams, but he's not writing code anymore. So why does it matter what the language is?
And if you even just go, like, I would love to go through the last 12 months of our podcast of being like, yeah, I can write the code, but you still need to review it. Or yeah, you can, you can get help with tab completions, but you still need to review, you know, like, like the level of cope that we've had over the years. And you, do you think that after the year we have had that it's going to just stop where it is? Yeah.
Yeah. And it's just done. Oh, yeah, yeah. As much as you
hate it, also the answer to a lot of the stuff of the problems of AI, the answer is often just more AI. And, you know,
yeah, I mean, that's why, like, I don't, I don't think it's cope. I just think that the like code, like AI can poop out code 100x, what a human can do, but that still means you need evals and you still like, I guess the process has changed for evaluation because maybe you're not doing it by hand.…
