GitHub has just announced a big new product that I believe is going to solve an issue a lot of people have had, specifically with GitHub's AI co-pilot. So in the past, a lot of people complained about this thing first launched because essentially GitHub's co-pilot was trained on, right, all of the repositories on GitHub, all of the code on GitHub, but the issue was a lot of private repositories were used for training, and people were finding that when they were, you know, getting co-pilot to recommend code, it was recommending code from, you know, repositories that were supposed to be private, like things coming out of Apple, and of course this is a big no-no if people are able to get code straight out of Apple's, you know, private IP, their private repositories, so GitHub had to do some quick shuffling back, then I believe they pulled all the private repositories out of their data set, retrained it, they were able to get rid of that, but still people to the day are complaining, you know, about essentially having code that is from other people's repositories, they did try to put another solution in place, in any case, this has been a problem that they've had for quite a while, and today they may have come out with a solution, so on the podcast we are going to be diving into what exactly happened and what they did here. So in 2022, GitHub put in motion a feature that essentially permitted users to automatically block suggestions of matching public code, right, this makes a lot of sense, this is public code, they don't want the suggestions that it looks like they just turned out plagiarizing copied it somewhere, you know, they could be liable, so while this did address one issue, it didn't answer all of the concerns, according to GitHub and a spokesperson there, the system would come into play less than 1% of the time, so you know, it's kind of an interesting idea, maybe gave some people peace of mind, but in reality it wasn't actually used very much, so developers might be intrigued to inspect these code fragments either to incorporate them or perhaps to kind of explore the entire library from which this snippet originated, right, of that 1% of the time, so in an effort to kind of bridge this divide between both desires, GitHub has announced the launch of a private beta of a code referencing feature for GitHub Copilot, so rather than an outright blockage of matching code, developers are now empowered with a choice, when code referencing is activated, Copilot showcases the matching code in a sidebar and it gives developers a freedom to decide essentially their fate, right, what they want to do, if they want to take this code somewhere else or not, now the thing that I actually see being valuable here, you know, they say, oh, this is less than 1% yada yada, and I know they try to downplay it, but if you're trying to code something, you can't figure it out, it's really complicated, you see someone else has done it, it's part of that, you know, 1%, sometimes the 1% of code is still the valuable percentage that a lot of people like to use or it's really valuable or it's the trickiest part, right, so let's say it's there, I think developers would like the option of being able to see that code and, you know, some people are like, oh, then they can copy it, in reality I think they would like to see it and maybe they would just like to see how it was coded, they can write it their own way, but I think that it's actually really useful, even if not for anything but educational purposes, I think it's a really useful tool. So this feature is planned to expand to co-pilot chat eventually, so it was previewed last November, but the feature required some fine-tuning before its release, and GitHub CEO Thomas Domk expressed that major players, including Microsoft, GitHub, and most co-pilot enterprise customers utilizing the original block, you know, using the original blocking feature, so, however, he also acknowledged its limitations stating, quote, it gives you a little control to decide for yourself whether you actually want to take that code and attribute it back to an open source license, it doesn't actually let you discover that there might be a library that you could use instead of synthesizing code, it prevents you from exploring these libraries and submitting pull requests, you might be reproducing everything that already exists in some open source repo, so Domk highlights that this was particularly relevant to commonplace computer algorithms like sorting, the newly introduced feature will allow developers to reject the code, use it directly if the library allows, or have co-pilot reformulate the code.
So the current version doesn't actually allow for results filtering by specific licenses, but the team is working, they're getting feedback to kind of gauge the necessity of adding that, they said, quote, we're letting people understand the match and then go on and explore or go and make the right decision, so Domk explained adding that he believes it fills the gap in the original solution, so the code referencing feature pretty much tends to be more active in scenarios where co-pilot, it kind of lacks context, so when there's tons of context and that all available, you know, from existing code, co-pilot is a lot less likely to suggest a matching public code, however, at the initial stages, I think the likelihood of generating matching code actually increases, so central to this whole kind of initiative is a fast search engine, which is aiming to essentially keep latency within 10 to 20 milliseconds, I think this is really big, no one wants to wait for their code to generate, no one wants to wait a long time for anything, and I think increasing the speed is a big bonus on this, so it can rapidly essentially identify matching code and its licenses, you're not waiting around for that, and currently the matching snippets are listed in the order found, but in line with GitHub's original announcement, future functionality is going to be to sort by repository license, commit date, and you know, et cetera, and that can be expected in the near future, so in essence, GitHub's new feature manifests a nuanced approach to code referencing, catering to the multifaceted need of developers, right, and I think that the ever-changing landscape of software development continues to be shaped, we're seeing a lot of, you know, rapid developments here, and I think the GitHub's latest move is a reflection of the, you know, delicate balance between innovation and also responsible coding practices, so I think this is going to be an interesting story to follow in the future, seeing how they roll this out and how this is actually adopted by enterprise. Thank you for listening to today's podcast episode, breaking down how AI is impacting your industry. Today's episode is sponsored by AIbox, a no-code AI app builder and marketplace which just launched a crowdfunding campaign. If you are interested in investing in a new AI startup, you can go to republic.com slash AI-box, I'll leave a link in the show notes as well to learn more.
The minimum investment is $150 and the maximum investment is $100,000. Until next time, have a fantastic day.