# Software factories make codebases easier to learn and operate

Markdown copy of https://realalpha.app/s/software-factories-make-codebases-easier-to-learn-and/ on Real Alpha, the best minutes from long interviews with the people building AI. Cite and link the page, not this copy.

- Speaker: [Satya Nadella](https://realalpha.app/builders/satya-nadella/) · Satya Nadella is CEO of Microsoft. · Led Microsoft's cloud infrastructure and services transformation, and has been CEO since February 2014.
- 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 engineering after code becomes cheap with Satya Nadella](https://realalpha.app/v/0NE89Nzfk20/), Nov 16, 2026
- Moment: 15:32 to 20:47 of the episode (5 min), playing on https://realalpha.app/s/software-factories-make-codebases-easier-to-learn-and/; the episode from there: https://realalpha.app/v/0NE89Nzfk20/?t=932

## Quote

> “The way you want to do agentic coding is these little tasks that you give it. **Make sure that it's truly done**.”
> — [Satya Nadella](https://realalpha.app/builders/satya-nadella/) at [17:50](https://realalpha.app/v/0NE89Nzfk20/?t=1070) · The Pragmatic Engineer

## Takeaways

1. Use specifications and intent to guide agent-generated code.
2. Documentation can make codebases easier for new engineers to learn.
3. Connect production traces and operations back to code and fixes.

## About this segment

Satya Nadella describes software factories built around clear intent, documented codebases, small agent tasks and production feedback. Teams can bring operations into the software loop, not leave them alongside it.

From “Software engineering after code becomes cheap with Satya Nadella”, Nov 16, 2026. [Watch the full episode](https://realalpha.app/v/0NE89Nzfk20/)

## Transcript

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

[15:37](https://realalpha.app/v/0NE89Nzfk20/?t=937) We've now been throwing around the term software factory for a little bit. So let's actually talk about it. I feel this term is a bit vague, but it's coming around. What does it mean for you? Yeah, so I'm also still kind of coming to grips with it. So I'm pattern matching in what is teams of people in a software team today do, right? So, you know, I think I'd point your viewers to the blog that Bass wrote.

[16:04](https://realalpha.app/v/0NE89Nzfk20/?t=964) I mean, in fact, there are two nice blogs, right? The Cowork team and the GitHub Copilot team. Both of them have these blogs out. One individual developer was able to do that was on the GitHub side, which was maintain an entire runtime. And I think they also migrated, I forget whether it's from Python, I guess, to Rust. It's always to Rust. But nevertheless, that's a beautiful case study of what the productivity of a single developer and what does it mean to do that maintenance and so on.

[16:35](https://realalpha.app/v/0NE89Nzfk20/?t=995) Then there is the team. I think it's nine or 12 or whatever number of engineers. It's kind of crazy that that's the total size of that team and the software factory. And they've also done a nice blog. But there's so many things that I love. I mean, this is where, you know, if I could just go join that team and really learn it firsthand versus just reading blogs or talking to Bass and team. But for example, the fund.

[16:58](https://realalpha.app/v/0NE89Nzfk20/?t=1018) Fundamental transformation as I understand it is, right? One is code is gone from being input to output. Great. Then you kind of have to say, okay, that means specification and intent, right? Which is always important. Design docs were important. And so alignment, yeah. And so that's kind of very important now. Yeah. The other fascinating thing I'm also finding is, and I talked to one sort of early in career person who went in. Getting into a code base now is actually much easier because the reason when you're managing a software factory, everything is documented. And then you can ask it questions.

[17:40](https://realalpha.app/v/0NE89Nzfk20/?t=1060) You have this patient mentor or onboarding buddy. Exactly. And so you can have it. Your onboarding onto a code base is so much more easier than you scrounging around for tribal knowledge that's in people's heads, if you will. So The other thing is, I'm learning a lot about this verification stuff. The way you want to do agentic coding is these little tasks that you give it. Make sure that it's truly done. How do you have the critique? There's so much to be said about having a separate model family.

[18:09](https://realalpha.app/v/0NE89Nzfk20/?t=1089) In fact, that's the other thing that I've always worried about. It's like, hey, if there's one model family and these model families are not going to have all these alignment issues, how do you use a critique to ensure that one model family's challenge doesn't become your challenge. And so anyway, I kind of look at saying there's an entire new way to build that is emerging. And it's new software engineering. And it requires software engineers. It's just a level of interaction. Maybe that's why I like even the analogy of when you went from writing your own assembly to saying, oh, wow, I have a compiler. And suddenly you felt like, oh, wow, I can now go from intent to code and I don't need to know assembly.

[18:50](https://realalpha.app/v/0NE89Nzfk20/?t=1130) There's a little bit of that. It's a level of abstraction. But even how you work in a team has changed and how you construct a product has changed. The other one that I'm really excited about is the traces from production coming back. I love that too. We're talking about the observability, but now you have more opportunities. Yeah, I mean, when people say RSI, that's kind of my RSI, which is it's sort of the ability to take my production logs. And then to be able to verify the fix, in fact, that verifiability loop is great that you can then deploy the fix and deploy it all the way through that it actually passed all the tests. That actually is very helpful. And so I think there's a lot of learning that these teams are having and spreading across Microsoft. I mean, it's just good to see how this is now

[19:42](https://realalpha.app/v/0NE89Nzfk20/?t=1182) becoming the way teams are structuring. And the other one that I love is our networking, Azure networking team, right? In fact, this used to be my favorite story where this team said, hey, you know, Microsoft manages something like 500 fiber operators all over the world for our global network. And, you know, always it's a physical asset, something or the other goes wrong. You know, the fancy word for managing all that is DevOps, but the reality is it's emails and, you know, know, all sorts of ad hoc processes. And so they went and built this entire agentic system that actually does the ops. And that ops is connected even to their repos. And so now it's not just the repo on its own or the code base, but it's even the operations that are around it.

[20:28](https://realalpha.app/v/0NE89Nzfk20/?t=1228) And so you can start seeing how the nature of what technical teams do is build these factories of ops plus software that do the job versus doing the job. But still, they're doing a job which is slightly different.
