Paul Dix

you pair that with like cloud code or gemini cli or codec cli you can actually do a lot of things you can answer a lot of questions that people outside the company might have support questions so basically where i want to get to is you know if there's something that comes in for support from from a customer we are able to actually answer that

within minutes based on agents doing the work and you still need like support engineers and regular engineers to review things and to build the tooling behind the scenes but ultimately where i want to get to is all of that stuff is executed automatically when things come in and they can use

both the code that we have internally that our customers can't see, and all the documentation and internal knowledge base that we have, either in previous support requests or issues that we have in closed source repos or documents, markdown files, and code.

I mean, I still think there's a ton of value in libraries that are written and tested and hardened over the course of multiple years.

So I don't think that's going to go away.

I think it's probably... The more complex something is, the more likely it is that you're going to want a library to do it.

So like a SQL query engine, for example, that is a very, very complex piece of software.

And you would be best picking something off the shelf that's actually written.

You're not going to ask...

an ai to write the thing from scratch right although it certainly could try and probably could produce some fairly passable result but it's not going to be you know as performant and as battle hardened as something that's been developed over the course of years so i don't think that changes i think as the ais get better and better like the scope of things that they can one shot and give just give you

uh improves so like you know in the various like code ecosystems like npm or crates or whatever there's this huge long tail of libraries where it's like you know a few functions or whatever like those the value of those is like gone

Right.

But I think the bigger problem, based on what I've seen from people online, is there is now like a deluge of, you know, AI slot pull requests that open source maintainers are having to deal with.

And they're basically getting to the point where they have to start shutting down pull requests like they are accepting them at all.

Right.

They have to be.

you know we'll be open source and whatever but we're not open contribution because they can't deal with the fact that like they're just getting inundated with these pull requests that have no thought or or time behind them right because it's just too easy for somebody to spin up an agent to say like do this and issue a pr

So maybe that gets better and GitHub actually adds some tooling.

I think we've seen a lot of GitHub anger over the last few months because they don't seem to be too on top of this at the moment.

But yeah, right now that feels like the bigger impact.