Adam Leventhal

Ha, ha, ha.

But it took a while for people, and some failed experiments, right?

It took Nano Java and Pico Java inside of Sun and a bunch of, and two different OSs inside of Sun and Java.

So there were a bunch of,

like where we got, and then people were like, okay, no, this thing is like, it's important and it has a role, but it's not everything.

Yeah, totally.

And if you were implementing in C, it's like, well, I hope the past is working out for you.

I mean, this is the whole idea of like, you are, you are actually a living fossil and Java is actually going to come to replace you.

And, you know, in some ways it was like, I actually, I really do think it was kind of worse because if you were doing as what we were doing, like, you know, we're in the operating system developing this thing in C, it's like Java didn't really have anything for us.

you know, it was not like, oh, I mean, we did it around the margins, but not like our tooling.

I mean, even the kind of the value that Java legitimately delivered, we didn't really realize any of that.

And, you know, ultimately we, we ultimately had a good relationship with Java, but it wasn't like, whereas I think with like LLMs, like, no, no, you can actually, everybody can kind of up their game with this thing in a way that's really exciting and uplifting.

Yeah, spot on.

Well, David Rain, anything else?

I know there's obviously a lot to talk about here.

That's a great advice.

And actually, let me ask you to expand on that just a half a beat, because I do feel as part of Deep Blue, you do have especially, and it's unclear to me, by the way, if this is truly young people of like undergraduates versus a kind of a more mid-career malaise, and maybe Deep Blue cuts across all of it.

But people who are wondering like, what is, you know, how can I, what is my role in this kind of this new LLM age?

What would be some advice that you would give to an engineer that's early in their career and looking at this stuff?

Yeah, that's great advice.