Burke Holland

And the only way to really understand all these levels of abstraction, but the second that that comes out of my mouth, I'm like, yeah, but at some point, you had to understand what the compiler was doing, and you don't anymore.

I don't know what the compiler does, nor do I care.

So as you said, we don't know where all this is going.

But I don't think that you couldn't bring a non-technical person in and just drop them inside of an AI tool and be like, do it.

Unless it was like v0 or something for Vercel, where it's really abstracting.

But to actually ship a piece of software, no, you still need to be a dev.

I think that for your high-performing devs, I actually wonder about this.

Because the thing is, in the past, your really high-performing devs were people that could do things like build very complex algorithms to solve speed problems, performance issues, et cetera.

But AI is really good at that.

It knows all the algorithms.

It can just destroy leak code.

So I'm unsure at this point if that's really the case, other than that you need to know what to ask for a lot of times.

You may need to know that you need a binary search at this point, right?

And to be able to direct the AI and say, why don't we do a binary search here and see if that's faster?

You don't have to implement.

You don't have to know what that is.

how that's implemented.

That's not your problem, but it is your problem to understand the conceptual nature there.

Yeah, that's a really good point.

Somebody had made this point, I think I've made this point before, that my fear was, oh, we're all going to stop coding and just prompt AIs and we're all going to get dumber because no one is going to know what they're doing anymore.