Breaking GitHub, AI vampires & the great Oz | Warp’s Zach Lloyd

**Andrew Zigler** (0:05)
Welcome to Dev Interrupted. I'm your host, Andrew Zigler.

**Ben Lloyd Pearson** (0:08)
And I'm your host, Ben Lloyd Pearson.

**Andrew Zigler** (0:11)
And joining us for this week's news is a good friend of the podcast, Zach Lloyd, the founder and CEO of Warp. And Zach, it's really great to have you back. For our listeners, if you haven't checked out Zach's episode from last year, we strongly encourage you to go back and give it a listen.

**Zach Lloyd** (0:27)
Thanks for having me back on. I'm glad I earned a repeat invite.

**Andrew Zigler** (0:32)
Oh, of course. I mean, this will be first of many more, I'm sure, because back when you came on the pod and we talked about warp, which for those who aren't familiar, is the agentic terminal. Like it was a really net new thing for me, and we talked about everything under the sun, about developers and why they would adopt it. And today we have a whole bunch of news in store about developments in our industry around orchestration. Things that we've been covering week after week here on Dev Interrupted because agentic orchestration is coming in for everything in engineering right now.
And the greatest thing is that right now, you know, Warp, you've just released a new product on this as well called Oz. And we're going to talk about that a little later in our news roundup. But first, we do have to cover some of the highs and lows of this week in tech and the things that we all lived through as we evolve into the agentic developers of tomorrow. And the first thing we're going to talk about is GitHub, maybe struggling to keep up this week. Because if you were like me or many other developers who have an orchestrator at this point, you might have rolled out of the weekend doing about a thousand commits. So when it came Monday morning and you and all your coworkers were turning on these token machines, something dramatic very much happened to GitHub. If you were like me, you probably already know that GitHub was down. So Ben, what did you think of one of the largest code forges in the world having this tumultuous start on Monday? What does it mean for us?

**Ben Lloyd Pearson** (2:01)
Yeah, I mean, it really points out how as we become more dependent on agentic systems, the infrastructure that runs all of this stuff is more important than ever, because if Claude goes down, then there's significant portions of my job at this point that I'm basically incapable of doing. I could do it, but the manual effort it takes for me to replicate what Claude would have replicated for me is just like, it just doesn't make sense. It will just wait for it to come back up. Right. But yeah, it's pretty crazy just how impactful when you're using AI to accelerate everything, how big the gap feels when your infrastructure goes down.

**Andrew Zigler** (2:42)
Yeah. All right, you Zach, did y'all feel it over there when GitHub wasn't responding Monday morning?

**Zach Lloyd** (2:47)
Yeah. This was the day before we were doing our biggest product launch of the year, and all of a sudden, we couldn't see dips, we couldn't make commits. It was horrendous timing for us, and we were just trying to find ways to work around it.
We were coming up with creative things, like we have a code review feature in Warp, so you can do it locally. So we were just trying to find ways where you can bypass, get up, but it was just horrendous timing for us. I don't know if you all know what the root cause, if they've talked about it at all, but I would assume that they are starting to strain because the amount of AI generated code and GitHub activity has to be going through the roof right now.

**Andrew Zigler** (3:31)
It is. It's skyrocketing. It's like code agents that cloud code are committing about 4%, 5% of all commits on GitHub right now. And there's actually this chart that I saw on Monday, I'm sure we can include it in the show notes, of the commits going up and up and up and getting steeper, and then right around the beginning of February, it just skyrockets and suddenly you have slope on slope growth. And I think that's a moment where a lot of folks started to really understand orchestration and the power of running multiple agents at once and then being able to scale to do so. So GitHub, I think, just maybe wasn't ready for that kind of wave. I don't know if we've gotten an official kind of like breakdown on what happened, but maybe if you were like some folks too, at one point my agents recommended should we spin up our own GitForge? Is GitHub going to really be in the way of people?