# Software factories turn each release into a learning loop

Markdown copy of https://realalpha.app/s/software-factories-turn-each-release-into-a-learning-loop/ on Real Alpha, the best minutes from long interviews with the people building AI. Cite and link the page, not this copy.

- Speaker: [Harjot Gill](https://realalpha.app/builders/harjot-gill/) · Harjot Gill is founder and CEO of CodeRabbit. · Co-founded CodeRabbit, the AI code review company that became the most installed AI app on GitHub and GitLab.
- Host: [Gergely Orosz](https://realalpha.app/people/gergely-orosz/) · Host, The Pragmatic Engineer · Spent four years at Uber heading mobile, web and backend teams; shipped part of its payments system.
- Show: The Pragmatic Engineer
- Episode: [Software factories and code reviews with Harjot Gill](https://realalpha.app/v/4Cjb7691GJ8/), Nov 18, 2026
- Moment: 20:18 to 24:13 of the episode (4 min), playing on https://realalpha.app/s/software-factories-turn-each-release-into-a-learning-loop/; the episode from there: https://realalpha.app/v/4Cjb7691GJ8/?t=1218

## Quote

> “The chat is great when you're doing, crafting the software **one message at a time**.”
> — [Harjot Gill](https://realalpha.app/builders/harjot-gill/) at [22:34](https://realalpha.app/v/4Cjb7691GJ8/?t=1354) · The Pragmatic Engineer

## Takeaways

1. Agents can work on long-running goals, not just one chat at a time.
2. Each release gives agents a chance to learn from production.
3. Local compute limits are pushing development toward cloud environments.

## About this segment

Harjot Gill describes software factories as agent loops that build, test, deploy, and monitor code. Small teams need production-grade rollout and maintenance systems to ship at large-company pace.

From “Software factories and code reviews with Harjot Gill”, Nov 18, 2026. [Watch the full episode](https://realalpha.app/v/4Cjb7691GJ8/)

## Transcript

Transcribed by machine (Whisper) from the episode’s audio, so a word may be off here and there.

[20:25](https://realalpha.app/v/4Cjb7691GJ8/?t=1225) build products, the market's grown. There's a lot more people who need those products than ever before. And you mentioned software factory. It's a term that is going around a lot. What does it mean for you? Yeah, it's many things. I think, I mean, we have a slightly, maybe it's the same take as others but I mean I'll give you my take on it even when you're building with AI there are I think two ways of using AI one is like more like on a potter's wheel you are like shaping the software with each interactive chat with cloud code or codex like like for example like with ui development i have the browser open i'm doing annotation and each time i send a message i'm crafting the software but with ai and i can like manage as a human like my decision capacity is to do only like one or two of those tactical chats in a day i mean i usually have like 20 chats in codex right now two would be

[21:17](https://realalpha.app/v/4Cjb7691GJ8/?t=1277) of that manner around 18 are more like the factory concept like where i know that i can have the agent hill climb on something whether it's like building a distributed system i can be hands-off with a goal just like the example i gave you with the git on object stores and also sqlite ltx that's the other thing we did with knowledge base is we removed our vector database provider to build our own in-house version on sqlite ltx right on an object store and those kind of things you can hill climb the other stuff is like each time you have a deploy ci cd is happening it's an opportunity for the ai to learn and continuously improve it so i have agents running continuously to remove flaky tests right each flaky test resets the merge queue it's really bad so you have to have that continuously happen each time you have a deploy or a ci each run is

[22:06](https://realalpha.app/v/4Cjb7691GJ8/?t=1326) an opportunity for the agent to optimize something do the next thing right and then you're running the agents against production as well so you have agents which own health of some components i care about for example i care about billing i care about the knowledge base performance like i care about the code graphs we have. So each deploy, I have the agent running in a loop to observe the next experiment now and do either two things, like add more telemetry if it's like flying blind or fix something.

[22:31](https://realalpha.app/v/4Cjb7691GJ8/?t=1351) So those are the kind of loops I'm running. And those are factories. So the thing is that right now, the chat is not kind of the right interface to run those agent fleets at scale. The chat is great when you're doing, crafting the software one message at a time. So some of these things we are still figuring out. First of all, that whole maintenance, the janitorial work around shipping software and maintaining the factory should probably be in the cloud on sandboxes and all.

[22:58](https://realalpha.app/v/4Cjb7691GJ8/?t=1378) And I shouldn't be the one waking up at like 3 a.m. I mean, it's more like morning shift, night shift now in the factory. We luckily have a team in Bangalore. So we have a follow the sun model. So I want like if I'm babysitting the agent, so I'm not owning the cool daddy mode. We are owning agents. Let's say I have an agent looking at the health of a billing service and it stalls on something. it as a question, then if I'm around during the US time zone, I'm able to answer that question.

[23:19](https://realalpha.app/v/4Cjb7691GJ8/?t=1399) But I want someone to be able to unblock the agent while I'm sleeping. So I would say we haven't figured it out yet. So we are going on the upward trajectory, but most of our development right now is constrained by how many sessions people can run locally, how many releases they can make their PRs land in, like look at the release coverage and the PRs they landed. And we're also constrained on local resources. One of the things we found, and that's where I have a cheat code as a CEO, I have a very powerful machine. The developers don't have those. Like they have like 48 GB RAM, 24 GB RAMs, and they max out at like three, four sessions. Beyond that, if the machine just dies with the unit test, it has to run locally, right? So we are feeling like the real compute constraints right now in terms of the local development. And we are investing

[24:01](https://realalpha.app/v/4Cjb7691GJ8/?t=1441) very heavily to go and make some of our cloud-based environments work. But I guess it's pretty obvious
