# The battle to replace Github, building assembly lines for software, and why no one finishes projects anymore | Dev Interrupted Powered by LinearB

> This week on the Friday Deploy, Ben and Andrew unpack how surging agentic code volume and persistent GitHub outages are challenging traditional code hosting. They break down tactical blueprints for structuring chaotic AI pull requests into resilient software assembly lines and pushing past scope creep to finish complex projects.

_This is a markdown rendering of a live HTML page on linearb.io, generated for AI/LLM consumption — it is not a markdown-only site. To get the full HTML page instead, request this URL with an explicit `Accept: text/html` header (no wildcard, no markdown preference)._


```json
{
  "@context": "https://schema.org",
  "@type": "PodcastEpisode",
  "name": "The battle to replace Github, building assembly lines for software, and why no one finishes projects anymore",
  "description": "This week on the Friday Deploy, Ben and Andrew unpack how surging agentic code volume and persistent GitHub outages are challenging traditional code hosting. They break down tactical blueprints for structuring chaotic AI pull requests into resilient software assembly lines and pushing past scope creep to finish complex projects.",
  "url": "https://linearb.io/dev-interrupted/podcast/github-outages-software-factories-agentic-assembly-lines",
  "datePublished": "2026-08-21T12:00:00.000Z",
  "partOfSeries": {
    "@type": "PodcastSeries",
    "name": "Dev Interrupted",
    "url": "https://linearb.io/dev-interrupted/podcasts"
  },
  "actor": {
    "@type": "Person",
    "name": "Andrew Zigler",
    "jobTitle": "GTM Engineer",
    "worksFor": {
      "@type": "Organization",
      "name": "LinearB"
    }
  }
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://linearb.io/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Dev Interrupted - Podcasts",
      "item": "https://linearb.io/dev-interrupted/podcasts"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "The battle to replace Github, building assembly lines for software, and why no one finishes projects anymore",
      "item": "https://linearb.io/dev-interrupted/podcast/github-outages-software-factories-agentic-assembly-lines"
    }
  ]
}
```

[Home](https://linearb.io/)

/

[Podcast](https://linearb.io/dev-interrupted/podcasts)

/

The battle to replace Github, building assembly lines for software, and why no one finishes projects anymore

# The battle to replace Github, building assembly lines for software, and why no one finishes projects anymore

By Andrew Zigler

|

August 21, 2026

![the_battle_to_replace_github_building_assembly_lines_for_software_and_why_no_one_finishes_projects_anymore_cbbc64ca4a](https://assets.linearb.io/image/upload/c_limit,w_3840/f_auto/q_auto/v1/the_battle_to_replace_github_building_assembly_lines_for_software_and_why_no_one_finishes_projects_anymore_cbbc64ca4a?_a=BAVMn6ID0)

When an AI can write 90 percent of a codebase in minutes, why is finishing the project harder than ever? This week on the Friday Deploy, Ben and Andrew explore the recent string of GitHub outages and why the surge in autonomous agents is forcing teams to rethink where they host their code. They once again dive into the emerging trend of software factories, breaking down how engineering leaders are turning chaotic AI pull requests into streamlined assembly lines. Finally, they share tactical advice for "landing the plane" and pushing past scope creep to deliver the grueling final fraction of any major initiative.

### Show Notes

* [Incident Report for GitHub](https://www.githubstatus.com/incidents/zkxwbgr0cnmx)
* [Cursor launches Origin code hosting platform as GitHub outage exposes opening in AI coding race](https://venturebeat.com/infrastructure/cursor-launches-origin-code-hosting-platform-as-github-outage-exposes-opening-in-ai-coding-race)
* [Ask HN: Alternatives to GitHub](https://news.ycombinator.com/item?id=49331033)
* [Everyone building a software factory wants the same proof](https://devinterrupted.substack.com/p/everyone-building-a-software-factory)
* [Introducing Warp Factories](https://www.linkedin.com/posts/warpdotdev%5Fintroducing-warp-factories-activity-7495495980377714689-d5DK?utm%5Fsource=share&utm%5Fmedium=member%5Fdesktop&rcm=ACoAABCqFmgBSQblf9s76KLHtlPIw0RYDuwkmoY)
* [Landing the plane](https://theengineeringmanager.substack.com/p/landing-the-plane)

### Transcript 

_(Disclaimer: may contain unintentionally confusing, inaccurate and/or amusing transcription errors)_

\[00:00:00\] **Ben Lloyd Pearson:** All right, Andrew. Another week, another life beyond tokenmaxxing story. I, I love it. This time it's from a LinearB customer, which I love even more. In fact, past Dev Interrupted guests as well, so Super.com. Uh, we, we were all really excited internally about this really awesome article from their head of AI over at Super.com, uh, just talking about how they stopped counting tokens.

\[00:00:24\] **Ben Lloyd Pearson:** So yeah, I guess chalk it up yet another company out there that, you know, they start with those tokenmaxxing leaderboards. They have fun for a day or two maybe, and then they immediately start thinking like, "Well, how do we, uh, how do we actually make sure we're getting value out of this?" So

\[00:00:41\] **Andrew Zigler:** It just keeps happening

\[00:00:42\] **Ben Lloyd Pearson:** it, Andrew?

\[00:00:43\] **Ben Lloyd Pearson:** It, it warms my heart reading this story.

\[00:00:45\] **Andrew Zigler:** Yes. Well, it just keeps happening and I think it's going to keep happening, and this article from Luis Morales, their head of AI, um, he does a really great job of explaining that tokenmaxxing and the leaderboard is just the first of many \[00:01:00\] questions that you need to be asking about AI adoption within your engineering org.

\[00:01:04\] **Andrew Zigler:** uh, likens it to a, like rungs on a ladder, right? And he calls out that a lot of these big industry players like Meta and Uber and the like, they're all still stuck on rung one.

\[00:01:14\] **Andrew Zigler:** And while it's undoubtedly impressive, which he agrees as well, that companies of this scale can get to a point where they are using that many tokens and there isn't that much widespread adoption.

\[00:01:23\] **Andrew Zigler:** But if you don't grow beyond then asking what's the next question, which then he further defines as, uh, asking about the outcomes, the business outcomes that you're getting from your AI adoption. Until you move to asking that question, you're just gonna be stuck in this tokenmaxxing world. So I think we're gonna see lots, lots, lots more, uh, tokenmaxxing abandonment stories from leaders.

\[00:01:44\] **Ben Lloyd Pearson:** Yeah, and of course, we'll link to the, to the article in the, the show notes for this. My opinion is like, yeah, make the tokenmaxxing leaderboard. Like, set a hard limit on the budget. Uh, just set it up, let your engineers go wild for, like, however long it takes them to spend that \[00:02:00\] budget. And then, you know, start to reevaluate how you can actually capture some, some gains out of that. So, uh, yeah, really great story. And these are the kind of stories that we cover here on "The Friday Deploy," brought to you by LinearB. I'm your host, Ben Lloyd Pearson

\[00:02:16\] **Andrew Zigler:** And I'm your host, Andrew Zigler

\[00:02:19\] **Ben Lloyd Pearson:** And this week we are covering why GitHub is down again, all of the new competition that's appearing in the cloud, code hosting space, the latest in software factories, and how to end projects.

\[00:02:33\] **Ben Lloyd Pearson:** So A- Andrew, let's talk about the thing that, uh... Well, for, for anyone who's a GitLab user, they're like, " Man, I wish our service would go down every once in a while so I could just..." I mean, maybe it does.

\[00:02:46\] **Andrew Zigler:** GitLab going down. Well, it, this is a, so from GitHub here, this story is, honestly a, a interesting repeat that's been happening through a lot of the year. I mean, obviously as the world has... Engineers \[00:03:00\] have, uh, become increasingly agentic, and their agents are slamming GitHub, which up until now has been like the de facto code repo, the place you go to throw your code.

\[00:03:09\] **Andrew Zigler:** GitHub is effectively, one, just the general, uh, adoption of, uh, like code, uh, hosting for repositories. So, uh, naturally it became the place where people were chucking all of their agentic requests. And GitHub, uh, try as it may, is definitely having trouble scaling and keeping up with the uptime needed to handle these kinds of requests.

\[00:03:29\] **Andrew Zigler:** And GitHub has joined the many companies this year whose status pages have started to look like, you know, completely orange or a mix of orange and yellow. It's like starting to look like a, a bell pepper mix

\[00:03:40\] **Ben Lloyd Pearson:** a meme at this point, like how s- status pages have changed, uh, dra- dramatically at some companies.

\[00:03:46\] **Andrew Zigler:** Yeah, just like a year or two ago before everyone was orchestrating agents, like pretty standard for status pages for engineering platforms and services to be fully green with lots of nines of uptimes and lots of SREs around it. Now, uh, it's typically \[00:04:00\] more like a, a blend of, of a whole bunch of outages, and this was something that hit GitHub over the last week.

\[00:04:05\] **Andrew Zigler:** They had an unfortunate outage that affe- impacted a large amount of their customers and their ability to push code, which in our agentic world caused a lot of problems. So naturally, what happened in this environment, an environment where people had all of the tools to move fast and where they had an opportunity or see, uh, see an option to maybe, um, move and build their own moat, house their own code, because they've been doing this with a lot of software, right?

\[00:04:33\] **Andrew Zigler:** Everyone's been going down this build versus buy story. So now suddenly GitHub goes down, and people get these shiny eyes that they never had before of what if I built GitHub? What if I had my own GitHub? And so, uh, really effectively, it's kind of like, uh, a GitHub is like Caesar in like, like the Senate, and like all...

\[00:04:52\] **Andrew Zigler:** everyone's coming up and doing like one stab, right? It's like You- and then he's like, "You too, Brutus?" And that's, uh, I don't know, one of the other open ho- source, uh, host- \[00:05:00\] hosting platforms. So everyone's spinning one up. Uh, there's e- a really fascinating one that came from Cursor as well. So you see AI native companies, AI model delivering, uh, inference delivering companies also taking a piece out of the code hosting pie.

\[00:05:15\] **Ben Lloyd Pearson:** Yeah, I wanted to save this point for a little later, but, uh, yeah, it's, it-- code hosting is like that. It's like one of those things that I feel like every developer feels like they can DIY it themselves. It's like, "I have ideas about how code should be version controlled and hosted and shared with my team and all of that.

\[00:05:32\] **Ben Lloyd Pearson:** I could surely do that and build it myself." So it doesn't surprise me to see like, uh, you know, companies taking advantage of, of this situation and just more, like a larger proliferation of, of these companies, particularly, as they, you know, the timing of this with, with between Cursor releasing their own hosting platform and the outage of GitHub is just, like, very unfortunate for GitHub. but yeah, I mean, getting into the details on this, like, you know, GitHub had degraded service for, like, over \[00:06:00\] seven hours actually. Um, and it affected a lot of, a lot of different systems, - they had a cascading series of, of issues that caused just failure after failure, and then, um, the attempts to recover from the failures actually increased the burden on, um, the infrastructure that was already failing. and, you know, it feels kind of crazy to think, uh, you know, we're talking about some of these new hosting platforms that are coming out. It's really kind of crazy to think or to be speaking of GitHub as an incumbent. But I kind of get the impression that they, they are more of an incumbent company in the Git space that is really struggling to keep up with this, all of this disruption that AI is causing. Uh, you know, I mentioned, like, you know, how a while back, I saw this meme of, like, GitHub before, uh, Copilot came out versus GitHub after, and how the status page, like, was just a completely different assortment of colors. and it's a very stark difference, and it's a real one that we're all feeling, uh, through explicitly through \[00:07:00\] outages I don't know if there's, if there's been another outage of this magnitude for as long for, from GitHub in, in, like, quite some time. Like, this really does feel like it was a pretty major outage for them. And I don't really wanna, like, rib GitHub too much because I think they still have built a really great platform and continue to build a great platform. Um, but I really wanted to draw just attention to how this really kind of is representative of this broader trend that we're seeing, um, where, you know, AI is starting to magnify quality risks within organizations. , I don't really wanna call GitHub, like, legacy, but, um, you know, for older code bases, they may be sh- they may be more difficult to integrate with these new agentic workflows that are coming out. But it's just putting more and more pressure on engineering teams to both respond to the incidents, but just generally speaking, to move faster at everything with AI. GitHub has gotta be feeling the pressure from all of these new companies entering into their, their space. Uh, we mentioned \[00:08:00\] Cursor. and you know, a lot of these fundamental fabric layers of software development, you know, the primitives do-- they are changing to accommodate, uh, this world where humans have to interact with other humans, but then also agents are involved to some degree, degree as well. and not all that collaboration ha- some of that collaboration happens in like your, or, or an increasing amount is happening in your IDE with the AI itself.

\[00:08:25\] **Andrew Zigler:** Mm-hmm.

\[00:08:25\] **Ben Lloyd Pearson:** Uh, but there's still a high degree that needs that sort of like interaction between multiple humans and agents and, and AI.

\[00:08:32\] **Andrew Zigler:** Yeah. I see this as a, as a really natural progression actually of the build versus buy story that we've been covering a lot, where you see a service or a platform and you, you maybe don't utilize or, or h- or need all of it. GitHub is a large platform. It's practically a social media network for engineers, and it has a lot of, of, of tooling and services on it.

\[00:08:53\] **Andrew Zigler:** So you also get this environment where people are taking more control over their infrastructure and the code that \[00:09:00\] goes into it, and there's more appeal in owning that part of your stack and just building exactly the slice of what you need. So it's a really precarious situation for a company like GitHub, and I think it's a really important, uh, bellwether to watch for other incumbents and for other industries and parts of the coding process that we take for granted, uh, because the same kind of, uh, divvying up for parts could, could happen really to anything that we take for granted.

\[00:09:25\] **Ben Lloyd Pearson:** Yeah, and I wanna point out that like this is not just happening to engineering e- either. Like this is happening to a lot of areas of, of knowledge work. You know, we've been seeing this a ton with content production here at Dev Interrupted. You know, our velocity has increased so much because like all of the fundamental artifacts that we have to generate as part of our content production process is, you know, a lot of them are like fully automated at this point, or very close to it at, at the very least. And a lot of the tools that we built around how we used to do content, these collaborative editing tools, like we used things like Google Docs and \[00:10:00\] comments on documents and edits and, and like all of that stuff, that was all designed in this world where it was just humans working with other humans. And there's this, this feedback loop that we have to get into our AI workflows that has been difficult for us to capture. Um, so what we've had to do is sort of like hack together all of this like custom infrastructure, uh, it's a workaround, like just, just the complete lack of tooling in this space.

\[00:10:26\] **Ben Lloyd Pearson:** And I think that's, that's really what's happening to software engineers right now. Like the velocity of, of teams right now is outpacing, um, the tooling that's being built for them, so they're having to build a lot of that

\[00:10:38\] **Andrew Zigler:** Yes

\[00:10:39\] **Ben Lloyd Pearson:** um, themselves. And, you know, it, it used to be, uh, everyone was talking about harnesses like six months ago. Now there's like a dozen that are out there that you can just go get that are open source and like have your own harness. Um,

\[00:10:54\] **Andrew Zigler:** Or you've rolled your own because many, uh, many folks have, have built their own. Really the new, the \[00:11:00\] new territory is the loops and the systems right immediately outside of that harness. And you know, it makes me even think of how folks are taking to this story on Hacker News exactly to your point, Ben, of like you have folks dropping advice in the comments about like what size hard drive that you need to run this kind of, uh, like a git repo locally for X size team.

\[00:11:22\] **Andrew Zigler:** You have folks like arguing against like the, "Oh, like you can't just say just," like there's a lot involved. And you have like ... It's like divided into camps very predictably with folks even offering up their favorite open source alternatives. And so the reality is, is that yeah, teams are strapping together with duct tape these really, uh, almost unique and, uh, very f- lightning fast solutions to problems.

\[00:11:45\] **Andrew Zigler:** W- developers have always been like water. They'll flow around any problem. We learned that from Tanya Janca when she was on the show. She rightfully called that out about security practices. They are like water. They'll go anywhere. Well, in this case, they're like a waterfall. They're going right over the \[00:12:00\] edge, right?

\[00:12:00\] **Andrew Zigler:** And there's no stopping them from being able to host their code or run their platforms however makes sense. So it's important to pay attention to that open flexibility

\[00:12:09\] **Ben Lloyd Pearson:** . Yeah. And so, you know, we, we, we, we've been talking about like the agent harnesses now. We've like solved that, and then all of a sudden everyone's talking, and we'll get into this in, in, in a moment, but now everyone's talking about software factories. So it's like the moment that you feel like you've, you've achieved the new velocity, it's like this new thing comes along.

\[00:12:28\] **Andrew Zigler:** Mm-hmm.

\[00:12:29\] **Ben Lloyd Pearson:** you know, I'll, I'll get off my soapbox on, on all of this. Like, I have a lot of empathy for the SREs who had to respond to the GitHub incident. Like, I hope you're getting some time to recover and relax from it, 'cause I know how stressful that can be. and you know, and I guess the, the general advice is that, I would provide is that just make sure that if, , if you're achieving higher velocity with AI, make sure you're not sacrificing quality along the way.

\[00:12:55\] **Ben Lloyd Pearson:** You know, people can be forgiving of outages, but if that starts to become the \[00:13:00\] norm and the expectation with your company, then, you know, that's gonna cause a lot of downstream problems with retention and, and all of that. So, you know, personally, I'm not, I'm not the kind of person to just go out and like try to like d- roll it myself on my own infrastructure or like try out the latest tool that just got released.

\[00:13:18\] **Ben Lloyd Pearson:** Like, I like to have more mature platforms for this kind of thing but at the same time, you know, I think it's just all important for us to be aware that like we need to start thinking about how just fundamental components of the SDLC like Git or like code reviews or, um, how we generate code, all of that is, is starting to ch- it, it is changing and, uh, we just need to be adaptive to it.

\[00:13:43\] **Andrew Zigler:** Exactly.

\[00:13:44\] **Ben Lloyd Pearson:** All right, Andrew, let's get into software factories and it sounds like everyone's talking about it. And I, I guess I probably say that because you and I just wrote an article about it.

\[00:13:54\] **Andrew Zigler:** Yes, yes. We might be a little, we might be a little biased, but what Dev Interrupted right now is at the \[00:14:00\] center of a zeitgeist of discussion around software factories, and we've been hard at work trying to figure out what it means for you, our listeners, and the teams and, and the, the opportunities that are ahead in organizing software delivery in this way.

\[00:14:13\] **Andrew Zigler:** So taking a step back for a moment, like, what is a software factory? Most folks, I would say, aren't calling their current SDLC or their AI adoption a software factory. But the reality is, is that we're optimizing towards many parts of that state. That includes getting to a point where code generation and agentic PRs have their own kind of creation process and come into a review cycle.

\[00:14:36\] **Andrew Zigler:** This is where many teams are encountering bottlenecks, which we talk about a ton on the show, where they build up in review and these agentic PRs don't merge. So then you have to implement new guards and new, uh, ways to direct this kind of attention so that the human operators can keep the stuff moving through.

\[00:14:53\] **Andrew Zigler:** That's a lot about how a factory works, too, in the real world. So there's a lot of lessons that we can extract out of that, but \[00:15:00\] also, too, a lot of opportunity for us to learn what it means for how we can ship s- uh, code safely and securely and at scale. So this article dove into some really emerging domain experts that we've found on this topic.

\[00:15:12\] **Andrew Zigler:** Uh, some of them are also past guests on Dev Interrupted, so it was a real pleasure to be able to focus and s- and spotlight their, their expertise. Um, I wanna call two of them out because one of them is Dex Horthy. He's, he's the CEO, co-founder of Human Layer, and the other one is Zack Lloyd. He's the CEO and founder of Warp.

\[00:15:30\] **Andrew Zigler:** And, uh, Warp actually just dropped a software factory, uh, system that we're gonna be talking about some in upcoming workshop that we have as well next week. Uh, but, uh, Dex is also attending this workshop because he's been writing a lot about how, uh, to watch for drift and rot and the problems that happen after you turn the lights off and you automate a software factory.

\[00:15:53\] **Andrew Zigler:** Um, so they both bring a really valuable perspective on how to not only operationalize it, but then what to watch \[00:16:00\] for, and there's a lot of opportunities for you to learn about maybe pain points in your own process. So that's like a high level view of this story. So if you haven't checked out the software factory, uh, coverage that we've been doing, I highly recommend that you start with that article from last week.

\[00:16:15\] **Andrew Zigler:** Dive into some of the latest announcements from our guests, and be sure to RSVP for our roundtable that I'm hosting next week with both of them and Dan Lines, my co-host here on, on Dev Interrupted and co-founder of LinearB. We're gonna have a discussion about what it takes to know if a software factory is successful.

\[00:16:32\] **Andrew Zigler:** Ben, what do you think about this topic? It really excites me, obviously, but what goes through your head when people talk about this?

\[00:16:39\] **Ben Lloyd Pearson:** Yeah. Well, first of all, I'm, I'm glad we can get in on the ground floor of, of this phrase because I feel like, uh, within a month or two, it's gonna be a, a catchphrase that everyone's kind of sick of because I think it's gonna be what everyone's talking about. Uh, so yeah, I really do think it's sort of like the logical next step to you've started to figure out how to harness your agents.

\[00:16:59\] **Ben Lloyd Pearson:** Now you \[00:17:00\] need those agents to sort of be orchestrated in a way that you can offload significant chunks of work. And we've really started to think about our work sort of as like assembly lines. Like there are, there are components of the f- the factory, the software that we produce that we can put on an assembly line, and sort of make sure that it always comes out in a consistent manner. and if we, we just chunk off work like that and start building assembly lines everywhere, eventually it starts to feel like a factory. yeah, so th- this is I think definitely the topic du jour right now.

\[00:17:32\] **Andrew Zigler:** Mm-hmm.

\[00:17:33\] **Ben Lloyd Pearson:** know, I, I, I've really had a lot of fun watching both Dex and Zach, uh, go off on kind of the deep ends on this concept. Um, and yeah, I think we're gonna have a really great session, next week on this topic. and of course, Dan Lines, the, the co-founder of LinearB will also be there, so we'll have a really great perspective on, you know, if you're, if you're still trying to unpack what is a software factory, like do I have one in my organization today? \[00:18:00\] Um, and then how do I scale that software factory and make sure that we're getting like measurable improvements from it? Like this is definitely gonna be something that will help arm you for what I think is gonna be like the next big thing that all the executives start to ask engineering leaders about

\[00:18:15\] **Andrew Zigler:** Yeah.

\[00:18:16\] **Ben Lloyd Pearson:** All right, Andrew. Uh, this one, uh, I just kind of wanted to cover as sort of a, just a closing statement 'cause, you know, I always like, I, I always like closing out on, like, more deep philosophical sort of things and less of the, like, "Here's how AI is just taking over everything."

\[00:18:33\] **Andrew Zigler:** Yeah

\[00:18:34\] **Ben Lloyd Pearson:** so we got this article from a friend of the show who we've been covering, uh, for a bit, James Stanier, um, titled "Landing the Plane."

\[00:18:40\] **Ben Lloyd Pearson:** So, uh, why don't you explain what's in this one for us?

\[00:18:43\] **Andrew Zigler:** Okay. Well, every- everyone who's ever started a project is familiar with the idea of, uh, scope creep. Landing the Plane is all about the ways that you just never really end up finishing a project, and the real difficulty of finishing that last 10% of anything. it's really easy to \[00:19:00\] think of, like, any kind of project as a linear task.

\[00:19:02\] **Andrew Zigler:** You go from 0% to 100%, and then you're done. But the reality is, is that you can get that first 90% very quickly a lot of the time, and what takes most of the time is getting that last 10%. Um, there's a quote that he, uh, Stanier includes in here that I really love that once you get the 95% of the way done, you're not even halfway there in terms of everything that you'd have to do to make it 100%."

\[00:19:27\] **Andrew Zigler:** Um, and w- what this is really rooted in is there's two problems in why 100% is so inescapable or in- unachievable for many. And one is just adding new things to do. One more thing, one more possibility, uh, never really closing the door on saying that something is complete. I think even just all modern software 100% falls into this guilty as charged category.

\[00:19:51\] **Andrew Zigler:** I think back to, like, infrastructure level things that are open source, like, um, and that w- are considered feature complete, where the \[00:20:00\] code base is done and it's closed, so we're not adding anything new. Like, that's not really a state that code bases of today are in or trending towards. Everything stays open as, like, an open-ended thing.

\[00:20:10\] **Andrew Zigler:** You're constantly chasing that elusive product market fit. You could never dare close the door on adding new stuff to your project. And so that's something that causes a lot of things that just never get finished. Um, and another one is also just knowing how the cadences of how stuff gets done. Somebody who's really good at getting something from 0 to 90% is usually not the person who's good at getting it from 90% to 100%.

\[00:20:36\] **Andrew Zigler:** I've experienced this pretty much on every major project I've ever worked on. Uh, you get it, the idea or, like, the delivery person, and then you get the one person or the leader handoff that perfects it and gets it absolutely hardened for every kind of use case, and those are very different types of skills.

\[00:20:53\] **Andrew Zigler:** So for solo builders or small teams, they just might be also missing that perspective needed to fill in those last \[00:21:00\] 3 or 4%. I mean, what did you think of this one, Ben?

\[00:21:04\] **Ben Lloyd Pearson:** Um, well, first of all, I feel a little bit called out, uh, just because it makes me really reflect on all of the things sitting around me that are at, like, 80% or more complete. But, you know, we'll get to that. Uh, and I don't wanna spoil too much in the article because, yeah, I d- I do think it's very, it's very succinct and very well-written and has-- It's just packed full with, like, tips and references to other resources that can help you, like, develop your, your first brain on this. you know, I think that it's really great to have a reminder at this time when it's easier than ever to start a new project. It is so easy to start something new with AI, um, particularly if it's, like, a greenfield thing.

\[00:21:45\] **Andrew Zigler:** Mm-hmm

\[00:21:46\] **Ben Lloyd Pearson:** hardest part is always going to be finishing it at the end. Uh, so I think the saying is something like the, the first 90% takes 90% of the time, the second 90%, or the s- the 10 per- the last 10% takes the other \[00:22:00\] 90%. just because AI is letting you create more than ever before doesn't mean all of that more is gonna turn into something valuable unless you see it all the way through to the end.

\[00:22:10\] **Ben Lloyd Pearson:** So yeah, you mentioned a few of them. There's a lot of classic tips in this, like protecting your scope, over-communicate with stakeholders, shield your team from, from new requests, run retrospectives to find ways to get better, um, and just a lot of other things. So yeah, just a lot of great general advice about how to be a leader in this very chaotic time.

\[00:22:31\] **Andrew Zigler:** Yeah, you know how there's like the ideas guy, the person who has the idea for like the game or the thing they want to build, but they don't want to do it? If only I had a, a coder, somebody who could build it, right? And that persona exists. Well, now the ideas guy can just sling his idea into code that gets 90% of the way there.

\[00:22:49\] **Andrew Zigler:** But there's still the moat for the person who actually f- uh, hardens the craft and delivers it, and I think that's what this post, um, really celebrates.

\[00:22:58\] **Ben Lloyd Pearson:** Absolutely. Well, \[00:23:00\] that's what we have for you today on the Friday Deploy brought to you by LinearB. Uh, thank you to our dear listeners for following us all the way till the end. If you've stuck around, you know, the best thing that you could do at this moment is just to help us grow the show. Give us a thumbs up, comments wherever you're consuming our media, or engage with us over on LinkedIn and Substack.

\[00:23:20\] **Ben Lloyd Pearson:** You know, if you're only listening to us here on the podcast or watching us on YouTube, you're actually missing, like, a lot of things that we share on a weekly basis, um, over on LinkedIn and Substack. So make sure you go check out, Dev Interrupted over there as well. So thank you again for listening to us, and we'll see you next week

\[00:23:38\] **Andrew Zigler:** See you next time.

## Real conversations with top engineering leaders

Find us on

[](https://www.linkedin.com/showcase/dev-interrupted/)
[](https://devinterrupted.substack.com/)

## Your next listen

[![Cover image for Can agents keep a secret? We asked 1Password’s CTO Nancy Wang](https://assets.linearb.io/image/upload/c_limit,w_3840/f_auto/q_auto/v1/Blog_Comprehensive_DORA_Guide_2400x1256_78_8ed56543e1?_a=BAVMn6ID0)](https://linearb.io/dev-interrupted/podcast/1password-nancy-wang-agentic-security-secrets)

Dev Interrupted

[Can agents keep a secret? We asked 1Password’s CTO Nancy Wang](https://linearb.io/dev-interrupted/podcast/1password-nancy-wang-agentic-security-secrets)

1Password CTO Nancy Wang joins the show to break down the golden path for agentic security, explaining how just-in-time secrets provide autonomous AI with...

[![Cover image for Agent, skill, or MCP? Which to use and when to use them | AWS’ Clare Liguori](https://assets.linearb.io/image/upload/c_limit,w_3840/f_auto/q_auto/v1/Blog_Comprehensive_DORA_Guide_2400x1256_76_bb95f7500e?_a=BAVMn6ID0)](https://linearb.io/dev-interrupted/podcast/aws-clare-liguori-agent-skill-mcp-architecture)

Dev Interrupted

[Agent, skill, or MCP? Which to use and when to use them | AWS’ Clare Liguori](https://linearb.io/dev-interrupted/podcast/aws-clare-liguori-agent-skill-mcp-architecture)

AWS Senior Principal Engineer Clare Liguori joins the show to untangle modern agentic architecture and help engineering teams choose between full agents,...

[![Cover image for Telling your agent “no” is a moat now, rearward deployed engineers, and harnessing the context for your SDLC](https://assets.linearb.io/image/upload/c_limit,w_3840/f_auto/q_auto/v1/ai_agent_workflows_engineering_context_management_82ca8af964?_a=BAVMn6ID0)](https://linearb.io/dev-interrupted/podcast/rearward-deployed-engineers-claude-code-auto-mode-sdlc-context)

Dev Interrupted

[Telling your agent “no” is a moat now, rearward deployed engineers, and harnessing the context for your SDLC](https://linearb.io/dev-interrupted/podcast/rearward-deployed-engineers-claude-code-auto-mode-sdlc-context)

This week on the Friday Deploy, Ben and Andrew break down Uber's strategy of rearward deploying engineers to scale agentic workflows across non-technical...

## Structured data

_Machine-readable metadata (JSON-LD) embedded in the page for search/AI context — not content rendered on the page itself._

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "LinearB",
  "url": "https://linearb.io/",
  "logo": "https://assets.linearb.io/image/upload/v1715628027/logo-mark-lg.svg",
  "description": "LinearB is the engineering productivity platform that helps engineering leaders prove AI is improving throughput without sacrificing delivery confidence, flow efficiency, or developer experience.",
  "sameAs": [
    "https://www.linkedin.com/company/linearb"
  ],
  "award": [
    {
      "@type": "Award",
      "name": "LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms",
      "dateAwarded": "2026",
      "awardedBy": {
        "@type": "Organization",
        "name": "Gartner®"
      }
    },
    {
      "@type": "Award",
      "name": "Great Place to Work Certification",
      "dateAwarded": "2025-2027",
      "awardedBy": {
        "@type": "Organization",
        "name": "Great Place to Work"
      }
    },
    {
      "@type": "Award",
      "name": "America's Best Startup Employers 2025",
      "dateAwarded": "2025",
      "awardedBy": {
        "@type": "Organization",
        "name": "Forbes Magazine"
      }
    }
  ],
  "hasCertification": [
    {
      "@type": "Certification",
      "name": "SOC 1 Type 2"
    },
    {
      "@type": "Certification",
      "name": "SOC 2 Type 2"
    },
    {
      "@type": "Certification",
      "name": "GDPR Compliance certification"
    },
    {
      "@type": "Certification",
      "name": "ISO 27001"
    }
  ]
}
```

## More on linearb.io

### Top navigation

- [Book a Demo](https://linearb.io/book-a-demo)
- [AI Code Reviews — Catch security risks, bugs, and spec mismatches](https://linearb.io/platform/ai-code-reviews)
- [AI & Productivity Insights — See how AI tools affect cycle time and delivery speed](https://linearb.io/platform/ai-developer-productivity-insights)
- [Measure AI Impact — Track AI adoption and tie it to delivery outcomes](https://linearb.io/use-case/measure-ai-impact)
- [MCP Server — Chat with your data to spot patterns and boost output](https://linearb.io/platform/mcp-server)
- [Resource Allocation — Cost initiatives and shape your investment strategy](https://linearb.io/platform/resource-allocation)
- [Cost Capitalization — Capitalize engineering costs with audit-ready reports](https://linearb.io/platform/cost-capitalization)
- [Dev Team Management — Set targets and tie throughput to business outcomes](https://linearb.io/platform/goals-and-reporting)
- [DevOps Workflow Automation — Policy-based PR routing, approvals, and tests](https://linearb.io/platform/ai-workflow-governance)
- [AI Powered Support — Unify AI and human code delivery in one clear view](https://linearb.io/use-case/ai-powered-support)
- [Optimization — Surface friction with feedback and MCP insights](https://linearb.io/platform/developer-experience)
- [Reporting — Spot what's working and what needs attention](https://linearb.io/use-case/measuring-developer-experience)
- [Surveys — Turn developer feedback into actionable signals](https://linearb.io/platform/developer-surveys)
- [Platform overview](https://linearb.io/platform/overview)
- [Register now](https://linearb.io/event/the-great-software-factory-debate-2)
- [Customers](https://linearb.io/customers)
- [Pricing](https://linearb.io/pricing)
- [Why choose LinearB — Explore your data. Measure performance. Act to improve it.](https://linearb.io/why-linearb)
- [APEX framework — The operating model for AI-era engineering teams](https://linearb.io/resources/apex-framework)
- [Anti-FAQ — The questions other vendors won't answer](https://linearb.io/why-linearb/anti-faq)
- [Security — Enterprise-grade compliance and zero code access](https://linearb.io/security)
- [Build vs. buy — The hidden cost of building it yourself](https://linearb.io/resources/build-vs-buy)
- [Dev Interrupted Podcast — Conversations with engineering leaders](https://linearb.io/dev-interrupted/podcasts)
- [Reports & Guides — Deep dives on productivity and delivery](https://linearb.io/resources)
- [Webinars — Expert sessions on productivity and AI](https://linearb.io/resources?category=workshops)
- [Metrics Benchmarks — See how your engineering org stacks up](https://linearb.io/resources/software-engineering-benchmarks-report)
- [Blog — Product updates and practical insights](https://linearb.io/blog)
- [Help Center — Documentation, setup, and support](https://linearb.helpdocs.io)
- [API Docs](https://docs.linearb.io/api-overview)
- [Status](https://www.linearbstatus.com/)
- [Integrations](https://linearb.io/integrations)
- [LinearB Library](https://linearb.io/library)
- [Engineering metrics](https://linearb.io/library/engineering-metrics)
- [Platform engineering](https://linearb.io/library/platform-engineering)
- [Engineering glossary](https://linearb.io/library/engineering-glossary)
- [Developer productivity](https://linearb.io/library/developer-productivity)
- [AI in software development](https://linearb.io/library/ai-in-software-development)
- [Engineering management](https://linearb.io/library/engineering-management)
- [Developer experience](https://linearb.io/library/developer-experience)
- [DevOps](https://linearb.io/library/devops)
- [Engineering operations and the context layer](https://linearb.io/library/engineering-operations)
- [Engineering efficiency](https://linearb.io/library/engineering-efficiency)
- [Software delivery](https://linearb.io/library/software-delivery)
- [Research and data](https://linearb.io/library/engineering-benchmarks-and-research)
- [LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms](https://linearb.io/resources/gartner-magic-quadrant-dpi-platforms-2026)
- [Sign in](https://app.linearb.io/login)
- [Enterprise](https://linearb.io/solutions/enterprise)
- [Contact](https://linearb.io/contact-us)
- [About us](https://linearb.io/about-us)
- [Careers](https://linearb.io/careers)
- [Service agreement](https://linearb.io/services-agreement)
- [Privacy policy](https://linearb.io/privacy-policy)
- [DPA](https://linearb.io/data-processing-agreement)
- [Security FAQ](https://linearb.io/security-faq)
- [Substack](https://devinterrupted.substack.com/)

### Footer

_Additional links from the site footer, not repeated from the top navigation above._

- [GitHub](https://github.com/linear-b)
- [LinkedIn](https://www.linkedin.com/company/linearb)
- [Twitter](https://twitter.com/LinearB_Inc)