I feel like something I've heard a lot from developers is, you know, well, is it even worthwhile contributing to open source anymore? Right. If it's, you know, all just going to get ground up and training and all this, but I think you make a great point about how some of these models used responsibly can actually help surface that, right, and provide that credibility for developers.

And I have to say like the as a person who worked at GitHub, a lot of the code on GitHub is real bad, like super bad, like, and the code review process for most repos is non-existent. It's like you push changes in YOLO. And so the kind of code quality that is that is available on GitHub leaves a lot to be desired. And it's also not a lot of, you know, some languages are represented. So Python, JavaScript, et cetera. But the long tail languages are not represented much at all. And so I think that if we want to improve these code generation tools over time, like contributing code, contributing great code code that is code reviewed. And then also, you know, if you have a favorite language that, you know, if people want to submit Turbo Pascal examples or Fortran or whatever it happens to be, then you absolutely should because if you do, then the models will just get better over time.

I have a friend who works in software development. And I was asking him about, yeah, what the impact of co-pilot has been. And he said exactly what you were referencing their page. He works in Ruby. And he says it just isn't very helpful for autocomplete that he has other, you know, friends who work in like you Python and JavaScript. It's ready and willing to help them out. And for some of the longer tail languages, it's not always so prolific with its recommendations.

I was just going to say, and sometimes it also recommends dated APIs, right? Like APIs that might be from a framework that's a different version or something that's not super contemporary. And hopefully that will improve over time as well. Right.

There was the merging of Google brand and DeepMind. There was your announcements today about bar having code stack overflow, put out a blog post recently about how we're trying to adapt to the world of JNI and making some of the same points that, like you said, we want people to continue contributing knowledge to this like sort of open community where folks can come in and discuss quality or suggest improvements or an update if something is out of date and not just write become a training set that's behind a black box or you have to pay in order to access. So there's a lot of questions that are arising from this. But I think also just so much excitement among developers or even folks like myself, I'm really more on the marketing team, but could like whip up a little fire based app now going back and forth with the as my tutor. And so that's an exciting development to have more people maybe be able to jump into the world of software.