← Return to Index Archived November 16, 2026
The Lead — Nov 16
THE PRAGMATIC ENGINEER · GERGELY OROSZ

Software engineering after code becomes cheap with Satya Nadella

Microsoft CEO Satya Nadella argues that cheap code generation shifts software engineering toward specification, verification and production feedback. He also makes the case for companies to own their AI infrastructure rather than surrender their knowledge and learning loops to a single model vendor.

1h 02m / November 16, 2026 /aitechnologybusiness / Transcript sourced from openai
All episodes from The Pragmatic Engineer →·Episode page →·Podcast website →·Listen on Apple Podcasts →

Overview

Gergely Orosz talks with Microsoft CEO Satya Nadella about what software engineering becomes once generating code is cheap. They cover the "software factory" idea, why companies should own their AI stack rather than depend on one model vendor, local models, and the anxiety developers feel about jobs, including Microsoft's voluntary exit offers and the slowdown in junior hiring.

Key Takeaways

Nadella admits Microsoft was early with GitHub Copilot and then fell behind twice. The first time was Cursor's agent mode. The second was Anthropic's model, which made the command-line interface (CLI) a workable form factor and pushed integrated development environments (IDEs) aside within months. His lesson is that when model capability jumps, the product shape has to change fast: "Don't be in love with what you built." He doesn't think the IDE is gone for good. He expects it could return as intelligence gets embedded inside software as callable functions.

With code moving from input to output, the hard part is verification. Teams he admires turn every failure into a test case, use a model from a different family to critique the work, and feed production traces back to verify fixes. One side effect surprised him. New hires onboard faster because everything in a software factory is documented and can be queried.

He sees decision engines as a new primitive, a kind of "stored procedure of the intelligence era." For repeated decisions, such as triaging community feedback, you use a token-efficient component instead of regenerating code every time.

Most real work is on existing codebases. Builds and continuous integration/continuous deployment (CI/CD) are the hardest pieces to change. He says the volume of coding agents on GitHub forced Microsoft to rework the Git protocol and its storage system.

His strongest argument is about strategy. Firms should keep their harness, context, memory, and tool access separate from any single model, or they lose control of their own learning loop. His acid test is that you should be able to swap any model and still improve against your own private eval. He also wants a "trust architecture" that separates authority from intelligence, treats agents as insider risk, and keeps chain-of-thought logs readable and tamper-proof.

On jobs, he describes the voluntary exit offers as giving people agency during a period of disruption. He says forward deployed engineer (FDE) is one of the fastest-growing roles at Microsoft. He thinks the slowdown in junior hiring may be temporary, while companies rebuild teams around what he calls the AI-native pattern: one human, a token budget, then the next human once that budget is maxed out.

Practical Steps

  • Write specs and intent documents before handing tasks to agents. Keep tasks small enough to verify.
  • Turn each production failure into a test, and have a different model family review agent output.
  • Connect production traces to your fix pipeline so fixes are verified against real behavior.
  • Build private evals for the outcomes your business cares about, and don't rely on public benchmarks alone.
  • Keep context, memory, and connectors outside any one vendor's model so models stay swappable.
  • Once a workflow is stable, use its traces to fine-tune a smaller, cheaper model.
  • Route lighter sub-agent work to local models on your machine and send heavier tasks to cloud models.
  • Spend more time building than reading about AI. Nadella's advice is to join a team that is actually doing the work.

Notable Quotes

"In a world where code generation has become cheap, what has become hard is verification." (Satya Nadella)

"You should be able to replace any model and still hill climb on an eval that's your private eval... If you can't do that, then you have to ask yourself, how are you a sovereign firm?" (Satya Nadella)

"When am I at my best? It's when I'm in the school mode. So let's get back to school." (Satya Nadella)

In a world where code generation has become cheap, what has become hard is verification, and there’s new tribal knowledge in managing complex software projects. — From the episode

Full Transcript

Source: openai 1h 02m runtime

What does software engineering mean after code generation becomes very cheap? Today's guest is Satya Nadella, Microsoft CEO, one of the few big tech CEOs who started his career as a software engineer. Today we cover what the term software factory means for Satya and how it looks like today inside of Microsoft. OpenAI models, local models, and the idea of unmetered intelligence. The very real anxiety for us devs around AI, Microsoft voluntary exit offers, and why the junior hiring slowdown might only be temporary, and many more. If you want to understand what Satya thinks will take to become a standout software dev in this age of AI, and want to understand his thoughtful mental models on how to make sense of all this change, this episode is for you. This episode is presented by TurboBuffer, a ridiculously scalable, fast, and cheap hybrid search engine built on top of object storage used by cutting-edge companies like Anthropic, Linear, Ramp, and many others. Many companies who switched to TurboBuffer are cutting their search bills by 50% or more and getting much faster results. Check it out at turbobuffer.com/pragmatic. Satya, welcome to the podcast. Thank you so much for having me, Gergely. Well, it's great to be here because I'm not sure if you know, but I was a Microsoftie. Were you here or where were you? I was in London, and this is the first time I'm here in headquarters, so, you know, like, welcome. 12 years back. But I want to rewind back there. I was actually at Microsoft when you became CEO in 2014, and I remember, distinctly remember how Microsoft was still very much embracing closed source. And when you came on, you started to embrace open source. There was Visual Studio Code that was released. Microsoft acquired GitHub and went all on Git before we used TFS. TypeScript was released as open source. And I just wanted to rewind back. Why did you— people were surprised. My friends outside of Microsoft were surprised. Even I was surprised. Why did Microsoft go all in on open source? Yeah, I mean, at some level, sometimes these narratives and perceptions get shaped, and it takes a lot to change and what have you. Because if you look at even, I would say, commits even into Linux, even pre me becoming CEO, I think Microsoft had significant contributions and were committed to it. But the thing that I think we really made sure that we understood internally and the world understood is Microsoft is committed to open source, right? Whether it is bringing some of our workloads to Linux, like SQL Server, or contributing to Linux, or open sourcing projects like TypeScript and others, I think we're all part. And, you know, obviously, us as stewards of GitHub put us at the center of it, and we just wanted to make sure that we were able to earn the trust of the open source community by doing right by the community. In fact, it's fascinating, I've always thought about this, which is when you look at companies that have used open source and people who have contributed to open source, if there was a true accounting of it at some point, I think Microsoft would be at the top, or if not amongst the top, right? In fact, if you look at some, quote unquote, a lot of these other companies that have benefited the most from open source have hardly contributed. It's never. And that is, I think, how, you know, like, hey, you can't complain, but that's how the world rolls, which is it's on narratives versus facts all the time. Well, it's narratives versus facts. That's true. And again, I think there's that Windows legacy from the '90s that shifts people's, you know, like how they think about it. But what I remember made the biggest impact across the developer community was not really open source; it was Visual Studio Code. Yeah. It was open source, sure, but it was also free. And I was a developer before I used Visual Studio, and it was so good. Visual Studio 2003 is still an amazing piece of software. And somehow you decided Microsoft to bring Visual Studio for free in an open source version to the broader developer community, and boom, 10 or 5 years later, it's everywhere. Everyone was using it. Was that intentional? Yeah. In fact, you know, that, you know, Eric Gamma and others who were at that time in that place, really was absolutely, it was intentional, even building with community. In fact, you know, when I look at even... Even product making, it was the first time I also got exposed to what I think now people talk about, you know, building in the open. That was really the first time we all learned what building in the open means, having the community around it, and just that feedback cycle. I remember even spending time at that time with Amanda Silver and others, learning how that team, even the product manager, what does it mean to be a PM on that team, how they every day looked at the community feedback as a way to build versus, you know, top—you know, like it's not like, you know, I listen to my vice president, I listen to my community. So there were many, many cultural aspects of building in the open, beyond open source, that I think were fundamentally transformative. In fact, I would say sometimes I sort of feel like we learned a lot of great lessons there. We should have learned it even more deeply and more broadly. Speaking of learning more deeply or more broadly, Visual Studio Code was everywhere. GitHub was doing great. And then with Copilot, I mean, I was so surprised even looking back how Microsoft was so early to realizing that AI, before ChatGPT 3.5—this was, I think, the 3.0 version or so—Copilot was working like magic, and there was no real competition for at least a year until 2023 when Cursor came out. And then Cursor came out, and I still felt that you guys were super smart with VS Code because Cursor was based on VS Code, familiar interface, and, you know, GitHub Copilot and Cursor were going side by side, competing with one another, keeping up with one another. And then out of nowhere, 2025, Claude Code. And for myself, for people working at startups, even big tech companies, in six months everyone just forgot about the IDE. And I am still so surprised that Microsoft, you guys, live and breathe developer DNA is in your DNA, and it's always been. How do you think you missed that this sudden shift would come? And for the first time, I felt that you didn't have an immediate response. Yeah, no, it's a great thing to unpack, right? I think, to your point, being early to it, when we, you know, this was pre-GPT-4, right? So when we even started there, and even just the code completions were magical. That was sort of really what GitHub Copilot—you know, if you remember, we worked on IntelliSense forever, and we made good progress, and then we said, wow, this thing is working. And quite frankly, there was a lot of skepticism that it would ever work, but it started. And that was my—even my own belief in scaling laws, quite frankly, was fundamentally reaffirmed, let's say, when I started seeing that. And I thought we did a good job of trying to build that product. One of the keys of building with models is when model jumps happen non-linearly, the form factor has to change quickly, right? That's the, you know, what is AI-first product building in that sense is unforgiving, because when you have to be basically build everything around a given model and then be ready for the next model to have some emergent capabilities and rewire yourself for that, right? Don't be in love with what you built. So that's why even when agentic coding or task handling started becoming something that one could do, right? It's not just code completions, but you can assign small tasks. That's where Cursor, really—you know, they took the IDE, they forked, but they did a good job on really the agent mode. And so we then caught up on the agent mode, because that was sort of something that we could do on top of even the OpenAI models. But then the thing that hit us was obviously great work that Anthropic did with their model, which then truly made the CLI as a form factor. And then you could even just say just complete full handling of, you know, code went from input to output, effectively, right? I mean, that I think was the transformation. In six months or so, we went primarily—that to your point about IDEs, IDEs kind of faded away—and then you really had this new way of thinking about code as input. And that's why if I look at the new IDE, it's more about how do I really input the specs and the markdowns and everything else around the software factory. And so that transformation changes. Interestingly enough, it's funny that we're talking about it. Like one of the thoughts I have is with these decision engine models, finally I'm back again to IDEs because, you know, in an interesting way, it's kind of like functions, right? It's intelligent functions that are embedded inside software. So I think that there could be a rebirth even of an IDE as we think about even embedding intelligence in a more token-efficient way. So I don't say it's a permanent shift over in one way. It's about having multiple form factors now that actually help you with model capability. I do want to ask you here, you mentioned decision models and how you're excited about them. Both of us recently talked with Diogo in different forums. How has your thinking changed on both decision models, but also on the limits of LLMs specifically for programmatic tasks, for coding, for building software in a reliable way? Yeah, I think that that's kind of it, right? Which is, look, I think the LLMs are fantastic, and we can talk about even how— We're engineers. Let's cut to the point where they're not fantastic, right? Right. In the sense of how do you even think about the software factory, and there's an entire... Thing that we can go into. But what I love about decision engines is it's kind of a new primitive, right? And how Diego talks about it, and how our own decision engine and Achint and others are talking about it. And I like that because, you know, it's kind of like, you know, Excel macros, right? You know, what happened to spreadsheets with macros can happen with code with intelligence embedded as a primitive, right? And so, I don't know, you build any system. Like, I think I was looking at an Xbox system that they had built for managing all of the community feedback, right? It's a classic: community feedback comes, I make a set of decisions based on it. I don't want to really generate LLM code on it. I just want to be able to make decisions. So it's better to embed this primitive, right? It has a distribution. You can make a call. It's sort of a—it doesn't need to be generated again and again. It's token efficient. And so I think that this is one of those places where software engineering remains very much alive. It's changing. One of the things I like about Diego's thing is he wants to make it as boring as databases. In fact, to me, a relational database—I grew up with my, my, my, like the most favorite product in the developer chain, other than the compilers and the lex and yacc and what have you, was the database, because the relational database is a reliable way to be able to store, query your information. Just made all kinds of applications possible. And I think decision engines in the era of intelligence will also do the same. Well, in fact, the databases are the heart. And so we talk about what is the essence of a software company. It's the business logic, right? But when you go deeper, it's often in the database. In fact, so much of the business logic used to be coded in store transactions, some of these things. So I wonder if— Yeah, it's a good one. It's like, it's just like this is the stored procedure of the intelligence era. Yeah. So I wonder if there's an analogy or a hope, because I do see that we haven't found the right primitive. Like, we know that LLMs can generate code. We can use LLMs to do— to unreliable stuff, but we still, we're missing these kind of primitives, right? Yeah, yeah. So I'm very excited about it, and this is, I think, the beginning of how, you know, because one of the other challenges—and so let's go to the software factory for a second, right? If you look at even how cowork is built, or even the GitHub Copilot runtime is built today, and, you know, I think people have blogged about it, and it's fascinating, right? You know, in a world where code generation has become cheap, what has become hard is verification, right? And in fact, one of the things that I feel like, oh my God, I wish, you know, I want to join one of these Mark Russinovich, Scott Hanselman, you know, perceptorships or whatever they call, because I kind of feel like I got to learn, because I've not worked in a team that is mostly now code as output, right? But the code as output has a particular order of operations. It's not like code as output means everybody is just generating all sorts of random code. Like, the way you got to build the verification stuff, how do you take every failure and then build back the test case and make sure you truly verify the test, right? I mean, there's just so much, I would say, new type of tribal knowledge people are building up in managing complex software projects. In fact, it's a nightmare. I think even in that Rust migration they were having, they had to revert back. And so that is sort of all the, quote, the great advantages and some massive disadvantages. So that's why, to your point, having additional primitives like this decision engine, I think are good. And you mentioned that as a CEO of, like, this amazing company, you see all of the things happening, right? You oversee, you get information. You would want to go and work on a team if you could. Oh, absolutely. In fact, you know, my dream next job would be that, right? If I could go back and just be part. In fact, one of the things that's interesting, you know, I was going to send mail to Scott and Mark and say, Hey, they're doing an unbelievable job of creating this new program inside of Microsoft called Perceptive. I think they even have a relationship with Carnegie Mellon or something. And that idea that you can have people who can come in even early in career, because I care a lot about, hey, can you have an early-in-career person come in, join one of these teams, go up the learning curve? Because I think the learning curve—I remember people used to come to Microsoft for an internship. They would go see, hey, how is, you know, Cuttler's code? How do I go look at the malloc implementation? So what's the new form of that is what I think we have to really discover. And so, yes, if we, you know, my hope would be one day I get to do that again. I'm now understanding why so many CTOs, VP of engineering, SVPs do take step downs to work on small teams, to learn how to build with these new tools right now. Seems a lot is changing. Absolutely. I think, yeah, the organizational sort of context of it all is changing that I think, yeah, if I think about it, I think it's very important. In fact, you know, being a lot more hands-on at a time of great change on many fronts, right? By the way, being close to customers, building in the open, there's so much to learn on all aspects of what makes successful products or successful technology that, yeah, there's plenty of opportunity. 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. People in a software team today do, right? So, you know, I think I'd point your viewers to the blog that Bass wrote. 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 is on one individual developer was able to do—that was on the GitHub side—which was maintain an entire runtime. And, you know, 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. 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 there 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 fundamental transformation, as I understand it, is, right, one is code has gone from being input to output. Great. Then you kind of have to say, okay, that means specification and intent, right, which was always important. Design docs were important, and so alignment, yeah, align. And so that's kind of, yeah, very important now. 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 codebase now is actually much easier. Because the reason when you're managing a software factory, everything is documented. Yeah. And so, and then you can ask it questions. You have a station mentor, onboarding buddy. Exactly. And so you can have your onboarding onto a codebase is so much more easier than you scrounging around for tribal knowledge that's in people's heads, if you will, right? So the other thing is I'm learning a lot about this verification stuff, right? Which is the way you want to do agentic coding is like these little tasks that you give it, make sure that it's truly done. How do you have the critique, right? There's so much to be said about having a separate model family. In fact, that's the other thing that I've always worried about is like, hey, if there's one model family and these model families are 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, you know, 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. 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, right? Which is, you know— We're talking the observability, but now you have more opportunities. Yeah. I mean, people say like, you know, RSI, that's kind of my RSI, right? 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 it's spreading across Microsoft. I mean, it's just good to see how this is now becoming the way teams are structured. 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, 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, 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. 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. I do wonder because in AI labs, it's pretty common, and they're very open about sharing how software engineers there, their job is becoming to allow the agent and the loop to do a better job. So what you just said. But just sticking to practical level, like at a place like Microsoft, you will have teams that can experiment, and they're building new factories or there are platform teams, and maybe they have exercise and they're doing all these things. But you also have product teams who actually have a product, you have real customers. And this is where I see a lot of companies struggle with who do have a real business, and they are seeing these aspirational things from AI labs, or maybe even they're listening to you right now, and they're thinking, Hang on, like I can't just drop everything and build a factory because what am I going to do with the thing? How... How are you thinking about both this balance, and especially inside of Microsoft, what do you tell engineers? Like, how is your job changing, especially when you're working on a product that is a good product, it's a profitable product, customers depend on it? Yeah, it's a great point. I mean, like, first of all, you know, we don't get permission to do things that are not adding value to customers. Like, let's start there. To your point about a little bit of—and we've made our share of mistakes of, you know, going and doing random AI things just because they were, you know, cool to do. You kind of ultimately are going to— I think everyone's done that. Everyone's done that, and I've done my fair share of it and learned from it, hopefully, and will get better. But that said, if you sort of say, well, let's take even—let's face it, right, which is today when I look at the CVEs in Windows, right, because you now have AI models that are finding vulnerabilities. Yeah, and so we now need to go fix them all, and so therefore there's a new pipeline. So in fact, if I look at even the Windows from crash traces all the way to fixes, they are building out essentially a new type of software factory. Except this is a brownfield, right, which is the build system of Windows is still the build system of Windows. In fact, if you think about in all these brownfield projects, the most difficult part is builds and CI/CD. Oh yeah, oh yeah. And then, of course, you got to really, you know, even, you know, if I look at the amount of change that underneath even GitHub, right, which is, if you think about it, right, you know, we've had—I mean, suddenly all these coding agents showed up at work at GitHub, and the scale has gone through the roof. Yeah, it's superhuman level. Yeah, and so therefore we have to fundamentally change the entire Git protocol, the storage system. So we are working on every part of this to make sure that we are living in the brownfield as opposed to—I mean, the greenfield stuff we'll always do, but the real world is all about brownfield, and the brownfield requires stepwise, you know, hardening of systems, rethinking of the core primitives, right, all the way from source code control to build to CI/CD that work. Works in a brownfield project, and that takes time. That takes investment. That takes thought, and the sequence of operations or the order of operations is very, very critical. So one of the things that I want our teams is not about—one nice thing I like about the transformation is this is not about, oh, here is some new shiny object, and here is the team that's doing that, and everybody else lives in the old world. Like everybody across the company gets to use the new toolchain and the new ways of working and tackle the challenge in front of them on any product, whether it's Windows or SQL Server or a cloud-native service, what have you. And that, I think, is what we are seeing. To be fair, like this doesn't sound all that different to what we did in the past, because when there was a new technology, let's say React, which was a new front-end technology. Everyone wanted to use it, and what we did is no one got permission to just stop and migrate to React. But when you built a new product or you added a new feature, you start to add it in, you start to mix it. So maybe it's not all that different to how we're adopting AI. But what is different about this? It's a good one. Like, you know, sometimes I kind of say, yeah, I've seen this before and what have you. But I think the one thing that I do feel that's different this time around is that the physics of how we do things, right, that order of operations, the level of abstraction. Maybe, in fact, one of the fascinating things I think about is it is like when people moved, right? I joined the workforce at the cusp of when we went from, you know, in fact, in college, I was mostly working on a VAX, right, you know, with a VT terminal. This is the mainframe. Yeah, or a mini, right, VMS systems, right? So, and then I joined actually for a couple of years at Sun on a workstation, and then I came to Microsoft. And so, and then, you know, the world kind of was stable, right? You mostly wrote code in an IDE. Throughout my professional career, it sort of didn't really change. I mean, new technologies came, but all those new technologies were new frameworks and new runtimes. It was not like the concept count radically changed. Even the mobile thing was sort of a miniaturized PC with new sort of user interface, right, and new frameworks. This is a place where everything—what is the runtime? What is the framework? What is the IDE? What's the stack? You're right, every single part of it. It's a little more of a change in how you think about, I think. Then let's not forget, a new model could drop, right, whether it is a new frontier model or a new thing like decision engine, and it could change again, right? This is where I think we also have to be ready for the regime to completely be transformed at any moment, if you will. And so therefore, I think these are two things that— Things at least I think about, that thinking of it, learning from the past, when we are at our best individually or as companies or as teams in managing change, I think is always important. But also being open-minded that this time is different is also good. Yeah, and also specifically for the biggest change for us software engineers, and, you know, Microsoft has probably majority of the workforce is software engineers or people close to the code, as we used to spend most of our time writing code and most of our effort was learning at college, at previous jobs to be good at this. And this part suddenly disappeared, which I know for a lot of people, including me for earlier, it was hard to reconcile because we've never seen it with any technology change. It always added a new tool. How do you see people inside of Microsoft or outside who talk with reconcile this, who are really good engineers and they spend decades getting very good at coding, which is hard to do, right? Yeah, no, I think that that's right. I think so this is where what at least I am observing, and as I talk to even people who are, you know, both been great software engineers previously and now are prolific even in the new mode of production, is the same skills are still required. It's just, again, that what you think about, the order of operations, the tool chain has changed. And so that's one of the other reasons where I don't think it's about devaluing the expertise. It's about really taking the expertise and making sure that you can exercise that with new leverage, right? That is where the nature of how you work has to change, as opposed to thinking that this is about software engineering no longer being important. And I think that we're in that phase, right, where we are trying to figure out how to value the new thing. And in valuing the new thing, you are suddenly going to even start valuing the old thing, if it makes sense, right? Which is, when I look at the people, there's obviously someone who is AI native who comes out of—like, in fact, it is funny, last GitHub Universe, I went down and I met a bunch of college kids, and that was the first batch of college graduates who grew up in the AI era, right? Because they went to college when GitHub Copilot—right? So they didn't know an IDE world pre-GitHub Copilot. It was, like, stunning to me that that was sort of what's happening. So there is going to be people who are going to come at this who are going to be native to this tool chain. But I also think that people, when I see at Microsoft, anyone who has great depth and expertise in any part, has curiosity and is sort of learning the new ways to work are absolutely flourishing in it. And so one of the things I'm hoping to ensure is we create that opportunity for folks, because at the end of the day, right, you know, it's about economic return on your professional careers that matters. And so therefore, we want to make sure at Microsoft you can both value the skill set you have and build the new skill set that the marketplace will value. I'm really liking how you're looking at this, and also how you talked about how junior, new grads, early career people... are contributing, they can get up to speed. But one thing that's been going around in dev circles, and I'll just lay it out for you, is people are speculating, why is it that Microsoft is making the voluntary retirement offers? Like, what does this mean? There's this fear that could this be a prelude to potentially a layoff because of AI making teams more efficient? And I just want to ask you dead on the head, there's never been anything like this at Microsoft, which is what I actually paid most attention to, and also the fact that it is voluntary. How did your thinking and the company's thinking come together on this one? It's a very important question. And, you know, one of the things that we discussed a lot and we felt was, let's acknowledge two things, right? One is that, or maybe three things. One is let's acknowledge that there is going to be plenty of opportunity going forward. The shape of that opportunity may be different than what is the opportunity, right? If let's even narrowly think about just software engineering, as we were discussing. Yeah. So let's start there. Yeah. Then the next thing we should say is, okay, great, let's create more of that new opportunity inside the company, right? That's where everything that we're talking about, whether you're working on Windows or whether you're working on AI training, quite frankly, you get to really equip yourself with new skills that are going to be valuable inside of Microsoft and in the marketplace, right? Yes. But— In the marketplace, right? Yes. But the shape of what this new thing looks like is going to be different than what the shape of what it was before, right? Team, team sizes, team workflows. So we need to take—it's not that we don't want the 200,000 people at Microsoft flourishing, all of them, and growing even. But the 200,000 people at Microsoft and growing will have to be configured in different ways, right? When I look at even inside of Microsoft, some of even, let's say even the economic return, right? If you look at the wages for a systems engineer, right, or an infrastructure person, it's through the roof. Same thing if you are a researcher in training, right? So some of the expertise is highly competitive, highly valued, right? And so we want to give more agency, quite frankly. In fact, this voluntary thing was mostly about let's give everybody more agency to get themselves slotted into places that make sense for their economic opportunity long term. That's, I think, the key thing. You know, I've been CEO for a long time. I was a senior exec before that and what have you. But at the end of the day, though, I did grow up from an IC to this, right? So I think about a lot of the times when I was an IC or a lead, right, and maybe a manager of leads. That's sort of the lens through which I think about how should we create opportunity inside the company. I don't want to be stuck in a team that's not transforming, even inside of Microsoft. Let's face it, right? It's not like I can sit here and say every part of Microsoft has sort of really got the memo and they're all transforming at the... I want to give them, you know, if you're in a team where you feel stuck professionally, you can vote with your feet. I don't want you to, because quite frankly, there are many places you can go inside of Microsoft itself. So that is another opportunity we want to create. So in that context, we are trying to give more agency to people, realizing that this is a time of tumult, right? I wish I could just sit here and say it'll all be the same. I cannot, right? And, you know, this is one of those places where I want to be as transparent about the change. I want to make sure we do, I do the hard work of creating all the opportunity at the company and then make sure that our workforce is able to really make their professional growth come true here. I mean, I think you're saying this very nicely and thoughtfully, but how I would translate it is, you know, the world has changed big time, and we saw, for example, with cloud, there's been such a fast change, and the teams who fall asleep at the wheel, if you will, you cannot afford it. So you need to either go with it, realize that the world has changed, my work as a software engineer will change, my tools will change. And either I'm on board with this, I figure out how to be enthusiastic about this and see all the opportunities, all the engineering challenges with building the factories, with the new workflows, or I decide, well, I'm not going to do that. And in most places you're kind of stuck, but you're actually giving An option for people to decide if you would like to check out from there, you can right now, and there's no hard feelings. I think so. And I also feel like, look, I think let's sort of, if you come down to it, and I care a lot about this, right, which is we have created enormous anxiety, enormous anxiety in people sort of feeling that they don't have control of their own destiny. Because the way we have talked about this AI revolution is, yeah, you know, when people say, hey, this maybe, you know, the singularity is here, and therefore maybe we are building, there'll be one company or, you know, there'll be no jobs. All that sort of leads to anyone who even wants to change be sort of anxious. Yes. Stress. And so I kind of feel that this is where, look, we're a company of 200,000 people. You know, I know that there's going to be a lot of change in what each of us do. Like, think about it, right? One of the fastest growing jobs at Microsoft is FDE. Microsoft as well. Yeah, right across the industry right now. Across the industry, because in some sense, if you think about it, right, you have an account rep, very important. Then right next to the account rep is sort of our customers, you know, the technical support folks, right, and the customer, it's I think CSU is what we call it, customer success. Yeah. And then we have even the technical support people, and then you have the FDE team. Forward deployed engineers. All of these things require a complete, like they all should be going to the same preceptor ship that any software engineer is going, if you will, right? Because you can all, like I know even LinkedIn, I think they made this change inside where they call them full stack builders, right, which they combine roles. So all that change, I think there's opportunity. But you have to sort of walk the hard walk of really making that structural changes, getting people slotted, giving them opportunity, giving them the wage support, knowing how to evaluate people with their productivity and their excellence in their new jobs, in their new slots. This is the hard work. There ain't any incumbent. So that's why, you know, the celebration of the new, which always should be there, right? That's how competitive marketplaces work. Look, you know, we are a 51-year-old company. We're going to sort of be comfortable in our skin. We want to serve our customers well. We want to create fantastic economic opportunity for the employees at this company doing great work, given our mission to empower people and organizations. On the other side of this, but I just want to get this on the record. So when we talked about hiring new grads, so you are still hiring new grads, junior people, you're investing in them. You're seeing that because one of the worries in a lot of other companies and startups is, and they've slowed down or even stopped hiring because they're thinking, well, with AI, the people who can use it the most efficiently, as we previously mentioned, the ones who have expertise and they can leverage that, and they're very hesitant to hire any new career people. That's a great point. So one of the things that we're trying to do is in this change, this is why I think a little bit of the trends have to be watched carefully over sort of slightly longitudinally versus just, you know, one year, because we're in the process of a lot of change, right? So first job is to make sure internally all of the folks are getting reorged to places that make sense, right? That's step one. That's step one. I mean, like even inside of a team, right, you just want to get the configuration right. Then it makes sense to, oh, what is the industry hire or a new college hire? You add to this, right? And so a little bit of what's happening, I think, is the slowdown may be a slowdown to get those quote-unquote new factories of software engineering built. Such that new inputs, not just tokens, humans can come in and then in this new configuration give you high leverage, right? I mean, let's face it. What is an AI-native company? They start with a token budget and a human, right? Then they add that person maxes their token budget and then says, Let's add the next human, and then that human gets a token budget, and then their factory gets the budget. Yes, that is the constructionist way. And it's not like, okay, those companies, if they succeed, they will also be big one day, and somebody all are. And every company is going to start looking like that, and every project team or product team will look like that. And so that process of reconfiguring new discovery and configuration, it'll take time. And that's where I think, you know, trying to draw too many lines as long-term trends, I think is too early. Before we get back to the conversation, I'd like to talk about Linear, our season sponsor. Until recently, I was thinking of Linear as a tool that helps plan and organize the work, but it's much more than that. A lot of teams use Linear to ship changes from idea to merge in GitHub, all without leaving the tool. I sat down with Dima, an engineer on the Linear team, to see how devs inside of Linear use Linear to build all of Linear. So here's a real issue. When you submit a review with unsynced draft comments, Linear warns you about these comments, but it didn't tell you where those comments were. A customer complained and Dima decided to fix it. But before the fix, Dima did not open his IDE. Instead, he opened up Linear and described the issue to the agent. The agent built a fix, created a PR, and attached Storybook screenshots for easy verification. You can see the fix with the draft comments linked on this screenshot. In the PR, you can then open the preview with one click from Linear to play around with the change and see that it worked. And here's my favorite part: guided reviews, which is work in progress. Guided reviews is a new code review experience where the important stuff just pops out. The top of the review has a summary and a diagram of the change. Change. And the pull request is divided into chapters that walk you through what has changed. These blocks highlight the important changes in a way that's easier to understand and review. Oh, and when Dima is finished with all of this, he just self-approves the code and it's merged into GitHub, all without leaving Linear. If you take away one thing from this, Linear is no longer just a place for planning tickets and organizing the work. It's where all the work happens: creating the issue, kicking off the agent, checking out the preview, and doing the review, and merging to production. Linear is the product development system for teams and AI agents, and I'm loving this evolution. Linear is the product development system for teams and for AI agents, and I'm loving this evolution. Check it out and get a six-month trial at linear.app/pragmatic. If you've ever worked on B2B software, you know how this goes. A customer likes the product, then their security team sends a list: SSO, SCIM provisioning, role-based access. None of it is what you set out to build, but the deal waits on it. WorkOS is the auth infrastructure that covers all of that, so nobody on your team has to debug a customer SAML setup. The newer version of the problem is agents. Once an agent is acting inside of a customer system, the enterprise wants to know what it is allowed to do. That's what WorkOS Airlock is for. It's intent-based access control. Most access control only asks who you are. Airlock also asks what the agent is trying to do at the moment it tries to do it. Clear-cut rules like no agent deletes cloud resources run as plain code. For the fuzzier calls, an AI judge evaluates the policy at runtime. You write these policies in plain English, and Claude can pull the ones you already had out of Notion or Jira and import them for you. Your agents, whether that's Claude or Devin, connect through a single access point, and your MCP server is сид behind it. Airlock is a new layer on top of your existing permissions, so an agent can never get more access than the person who invoked it has. When something risky comes up, Airlock can escalate to a human for approval, say over Slack. The idea is to write the rules once and spend human attention only on the calls that that needed, and every request and decision is logged. Visit workos.com/airlock to learn more. Now, we know when everyone is building their software factories, they're changing how they work. A big trend, now that we go down to a little bit of the how this is done, big trend across the industry that I'm seeing, and I'm sure you're seeing as well, a lot of tech companies are moving to open models as well. A lot of them are spinning up their inference, or companies like Groq are buying their inference, they're buying their B200s and just launching the models on it. They all have their own reasons, but from your vantage point, you know, Microsoft is also in the open model serving business with Foundry, for example. How big is this trend, and is this inevitable? I'm asking myself, are there parallels to the open source movement and now the open model movement? Yeah, I think that there are for sure the parallel, which is, you know, there's sort of going to be closed models and there'll be competition amongst them, and there will be sort of an alternative to obviously closed would be open. Open gives you flexibility. In fact, I think, you know, one of the ways I come at it is with just this: what does a frontier ecosystem look like, right? It can't be— If you just get past this thing called there's going to be one frontier model to sort of have all of the world's knowledge, right? If you don't buy that, right, then you have to assume that there should be, in some sense, as many frontier models as firms in the world, right? Because after all, if you go back to actually Hayek, his description of what an economy is, it's all about knowledge being distributed, right? In fact, his entire thing about pricing is a beautiful sort of explanation of, hey, it happens because of knowledge being tacit and distributed throughout the economy, and every firm needs to be in control of it. And if so, then I would even say every firm has essentially got both human capital and token capital. So if every firm is going to have both token capital and human capital, that token capital can be an open-weight model into which you've embedded your knowledge. That's one. It can also be in the context layer. You could even be using multiple closed models, in fact, collecting even the traces of your usage of those closed models, and then using those traces to maybe train a small model and an open-weight model for yourself and keeping, you know, a combination. When I look at even Copilot, in fact, whether it's GitHub Copilot or Copilot, they're all designed as these multimodal systems, right? In fact, I would say maybe even by the next time you and I talk, everybody would say it's not about even open or closed. Everyone has a model system. In fact, it starts with even a decision engine, which says, which model to use for what task. And then I have my context and memory and my action space separate from any one model, because otherwise you have a complete lock-in. In fact, one of the things I think about is like, wow, if you really got your harness, your model, your memory, and all coupled, how would you ever get out, right? In fact, what are you doing and what do you own versus what is owned by the model? Because the model will basically collapse into it everything it sees. And so I think that this dynamic is getting better understood. You know, most people, again, think, oh, this is just some competition amongst tech people. Remember, there is no limit to intelligence. Every bank, every healthcare company, every insurance company, every analyst out there, everybody needs to sort of have a real thing, architectural approach to figuring out how do they manage to control their own learning and knowledge and have firm differentiation. And in that context, open-weight models is one strategy that I think has legs. You know, this is very interesting because I talk with a lot of mid-size tech companies, startups, and almost all of them are building the things that you just dropped: their own harness, their own context layer, their own context graph, their own inference. And I thought initially. And I thought initially, I'm like, well, this kind of makes sense because engineers love to build. And if you want to get AI engineering experience, the least risky thing is to build something internal. However, I never thought of this part where it's actually these engineers building for the right reasons, which is the strategic reason or not, they're probably doing their company a service. And you're saying that most companies should probably consider owning this system, having replaceable parts, primitives. That's correct. So in fact, what you are observing is correct, which is fascinating, right? In fact, I would say if you're a bank, you should check how software companies that are trying to manage in this ecosystem to become frontier are doing it. They're not ceding control. So in some sense, that's what the bank should be doing. So what is the bank? In there, they will have leverage. So for example, what we have done, you know, what we describe as this IQ layer is we've taken, for example, the harness that we have underneath Copilot and GitHub Copilot, made it a first-class thing that you can now go to Foundry as a managed service, and you have the harness. So in there, let's say you're building a supply chain system, you can start with our harness just as essentially an open, or you can bring Py or any other open-source harness as well. Oh, we love Py. But you can just have it as a managed service, right? So battle-tested harness from Microsoft, which we ourselves are using, is just available there. And then you can have all the Foundry models, right? So you have a harness, you can use multiple models as endpoints, you can have your context layer that is completely separate, right? Your memory and context is yours then. So I think now we have a model system. Oh, by the way, the action space, so with all the plugins and skills and connectors, right, all separate from any given model being only having the visibility to it. So I think a good sort of classic middle-tier platform. is emerging even for model-first development, where you're not just captured. And then you can eval everything, right? You can say, hey, I have an eval, and my private evals will matter more, right? All these public benchmarks, which, by the way, is great, but you need to have your own private eval for what is the outcome that matters to you, and then look at in your RLE, the real performance across all these models and continuously optimize. In fact, when I look at even, you know, even with our customers, they start with a frontier model. Then they say, well, great, I've got all those traces. Now I'm going to flip to, hey, this is a deterministic workflow. I mean, it's not like I don't need the next big model drop. I want to now cost optimize. I'll drop, you know, an MAI Flash model, drop it in there, use the traces to fine-tune it, and there you have it. So therefore, that's all stuff you can do in Foundry. So that type of work, I think, is what's going to increasingly be true. We're saying that you're already seeing that a lot of companies have their reinforcement learning environments as well on top of the evals so that they can stay in control, control pricing, and also, I guess, not leak their business data to some of the AI companies that might want to train their models on it. That's right. So if you think about it, right, so the way the simple analogy I have, at least in my head, is, you know, people, you know, in the past, whether, you know, in an insurance company, in a bank, in a healthcare company, said, hey, I'm going to get a relational database. Great. I'm going to deploy a relational database. On top of it, I may even buy some software that runs on that relational database that is sort of comes with its own business logic. But then I'm going to extend it with my own business logic that I write, right? And then I control it. And never at any point is my data in the database going to somebody else. It's not like when the database vendor says, hey, I'm no longer going to give you a database update, you still can migrate out. That's the question you have to—how are you going to migrate your memory out if your memory is in the embeddings of a given model, when that model company says, you know what, tough luck, I can't do a next update to you. Plus, I guess what we talked about when we have new primitives come, how are you going to integrate them? Great point, too. Because if you're too reliant on a vendor or a series of vendors, you'll have to wait for them to maybe do it. And I guess it's also easier to build right now, like, right? If you have competent engineers, we're good at this. Yeah. So I think that there are two enterprise architectural decisions that I think, interestingly enough, I'm hoping that people are going to start talking, right? Because, and in fact, to your point, all you have to do is look at a software team today in a software industry. They're all figuring this out to stay independent. I think this has to become more of the reality in the commercial space. And there are two: how do we avoid this reverse information paradox, which is don't leak your value. You as a firm need to be in charge and control of your own learning loop. What's the architectural approach? How are you making sure your context is separate from the models and you're using multiple models, and your harness is separate from the context and the models? Because that, I think, is the only way you can assure yourself that you can replace any model. In fact, my acid test for that is you should be able to replace any model and still hill climb on an eval that's your private eval. Yeah. If you can't do that, then you have to ask yourself, how are you a sovereign firm, right? Like, that means you do not have control of your own output. Yeah. So that's kind of the first— You're just sitting on a ticking time bomb. Yeah. I mean, you're done. I mean, like, is my point. And so then the next thing is you now need a trust architecture, right? Which is you kind of have to, in a world where you now know scaling laws work, except with scaling comes new capability but not alignment. In fact, no mechanistic understanding that hopefully someday there's a science breakthrough, but right now we're getting more and more capable and less and less reliable, like, which is the most dangerous place to be in. And so that means you have to separate out architecturally authority from intelligence. If your intelligence has authority and it's unreliable, Again, you're taken, right? You have a massive insider risk problem. And so you've got to treat these agents as insider risk. That means you've got to have a trust system. And there are a lot of things, right? Even this chain of thought, man, like this, the amount of, like, this chain of thought has to be not in neuralese. It has to be in human language. It needs to be auditable. It needs to be logged such that it's not tampered. It's not just in, you know, pre-training or in, you know, RL that things happen, right? Which is in test-time compute things could happen because they could reward hack. And so we have some serious amount of safeguards you have to build at runtime, as I describe it, which is the trust architecture that ensures that you can treat models and agents as insider risk and monitor them and have observability and what have you, and then ensure that you have control over your learning loop. As an engineer, all I'm hearing and all I'm seeing is there's so much new type of work that needs to be done. So many novel systems need to be built, which we don't have a blueprint for. I mean, and probably the best way to do is, well, build it, also talk with peers who are building it at the same time, and I'm sure we'll have blueprints and certifications in, I don't know, five to ten years or something. But right now, this is the job. Correct. And in fact, in fact, one of the things we have our conference Ignite coming up next week, and I'm excited about it because that's kind of what I want to make sure we do a good job is communicating that, hey, this is all doable. Like, there are blueprints. There is a lot of innovation happening in how companies... And so I think that we are reaching that stage where it's not just about the shiny object and the novelty effect. And I think people have to sit back and say, hey, how am I creating enterprise value in my firm? And once people sit and talk about that in a little more depth, then I think these patterns of success become much clearer. Now, as an engineer, one thing that I feel very lacking is all of these AI models, they run in the cloud on someone else's server or a super expensive B200 that I cannot afford. Or my company will not buy it for me, or if you are, I mean, you're lucky. But would it not be nice if it just ran on my laptop? That's a great point. And local AI, until now, it's been difficult, very hacky. Actually, funny, Microsoft is the one that's innovating. There's a new Surface Ultra laptop that Scott Hanselman gave me a demo, and I want to get my hands on because it has a chip. It has a local coding model running on it. Where do you think local models fit into the AI loop? And as a developer, I feel it's desperately missing, but am I kind of alone? You talk with more people. It's a great point, right? So one of the things is we're very excited about making sure that the PC is the form factor. You know, we innovate in the age of AI. And so to me, the way I've been thinking about it and how we've been executing on it is I've always felt like distributed computing will always remain distributed. So why not use all the power and all the tokens that are out there versus just the stuff in the cloud? So that's sort of the inspiration even for Ultra, because there is lots of innovation, in fact, from whether it's NVIDIA or AMD or Qualcomm. So it's fantastic. Intel, there's good silicon work happening and systems work. And this is, in fact, it's already true. What is it? Like last year's Frontier can run on your laptop, and last quarter's Frontier can run on your desktop. I mean, that's kind of like the capability. It's like how PCs used to evolve, right? Exactly. So it's great. So now that you have that, then one of the things that I think about, again, goes back to my decision engine and routers, right? So when I think about Hydra Fusion, I think that's the term we use, I forget now, which in GitHub we have a way to route. Right. I love the GitHub because all nowadays, in fact, in Copilot, the last time I chose a model— Copilot Fusion. Yeah, Copilot Fusion. So basically, we want to be able to have this router pick the models, right, for the task. And so that means, in fact, I see it in Ultra sometimes. I mean, suddenly I see the fan go, right, because my local model is being used. Because especially in an agent swarm, where you have multiple sub-agents, then you can invoke for some sub-agents a bunch of local models while you're using even the cloud models together. And so, yeah, this makes sense. Architecturally, it makes sense. Economically, it makes sense. And so we're in the beginning of what I'll call this hybrid intelligence era. Cloud will continue to grow. There's going to be infinite amount of sort of demand for these tokens. But that means you can also start thinking about the form factors at the edge as also token factories. In fact, I kind of think of it as the unmetered intelligence. Yeah, because you don't need to worry about how much you're using it. That's right. I guess this is where it's now starting to come together for me, because the MAI code, the Flash 1.1 model, I'll be honest, I wasn't too impressed. I don't think anyone was too impressed. But the one detail I was impressed with, when it comes to local models running on any laptop, I always assumed it must be open models. However, the MAI code can be downloaded on a Windows machine, even though it's a closed model, and it can be run there. There's the infrastructure there, and I'm like, huh, could there be a future where, like, other closed models, so I could choose on my laptop, like pick and choose, like either I download them and maybe it's free or I pay very little. You know, to your point about the code Flash models, getting them even all the way to a laptop is core priority for us, and we are excited. And that's kind of when I look at the code tab inside of Copilot, right, which is even independent of GitHub Copilot. Now, writing a document or writing an application, you can easily use these models on your PC, and that's exciting. But just to kind of step back and say, what are we doing with even MAI models, right? First of all, through the partnership with OpenAI, we have the OpenAI models, and we're going to continue to use those OpenAI models, right? On top of that, what we are saying is, okay, let's sort of innovate in a new model family ground up. Ground up meaning you build it from zero. Yeah, first of all, we have, you know, I think we disclosed even the new MAI-2 base, which is the pre-training, and in fact, it's one of the best disclosures of a pre-training recipe and regime. So for those who are, you know, your listeners should go look at it, right? It's probably—and people tell me from the outside—that it's the most detailed descriptions of pre-training, right? Because there are very few places where you can go to and get it, and it's completely clean room, so to speak, implementation of a pre-training run. So therefore, we're continuing to do that. But then the place where we are able to sort of innovate is, I'll call it new points on the frontier curve, where using our products, right, whether it's cyber, whether it is knowledge work, whether it's coding, how do you put new points on the frontier where you're both flop-sufficient on training and you are efficient on tokens in deployment? And once you are in a world where you're handing high-level intents to many sub-agents, the sub-agents can be using multiple model families, right? That's, I think, the way. Like this idea that, oh, I'm, like, wedded to one model family may not be true if there are choices. Agents will be smart in picking all of the models that allow them to get the task done in the most efficient way, and that, I think, is our goal. Our goal is to give more choice as opposed to just one model family. I really like how you're setting out choice, because as a developer, I love choice. It also helps leads to competition, better prices, and so on. And as closing, this change is very fast. Everyone I talk to who've been in the industry, they said they've seen, you know, like change maybe similar to this, maybe not as big, but not as quickly. You've been through multiple change cycles. When you started, it was a very different time. How would you approach this change as a software professional when your goal is, I would like to be an amazing software engineer in this new age of AI in a year or two? You know, it's sort of the stuff we talked about. Quite frankly, even for me, I think just making sure that one gets grounded in what is this change about, right? It's not just about the headlines, and it's not just about, definitely not the headlines, I love X and, you know, it's great, but it's just not about the hype cycle and that constant need to talk. But it's ironic in a podcast to say that, but it's do more, learn more, and hands-on, like experience it firsthand. That's, you know, quite frankly, that's kind of what I would even say for me. If I could change the ratio of my, you know, talk to do, I would do it. This is the time. If one piece of advice, whether you're mid-career or even a CEO like me or— Even a CEO like me, or a fresh college grad, the more you can take the time to sort of learn, to do, be in teams that are doing, the better it is versus, I think, anything else. Because at times, at some level, I sometimes think about it, and when am I at my best? It's when I'm in the school mode. So let's get back to school. Satya, thank you so much. Thank you so much. It's such a pleasure. Well, this was an awesome experience, and we really covered a ton of ground with Satya. A recurring theme that kept coming back: what kind of software engineering work becomes more important when coding becomes cheap with AI? We talked about how things both before and after coding, that is planning and validation, both become more important, and this will be activities that us engineers will spend more time on. I also observed a lot of tech companies building their own coding harness, context layer, and AI infra, and I assume that it's because engineers just like to build with novel technology. But Satya pointed out that it's actually suicidal strategy for a company to not own their AI infra and their AI intellectual property. In fact, he thinks that every successful company will build out this own AI infrastructure, and those relying on a single vendor or AI lab are making a massive strategic mistake. Talk about us devs enjoying building new stuff and it's paying off. I can see us having a lot of opportunities to build this new type of AI infra and these internal software factories. Finally, software engineering roles and expectations are also changing. Satya shared that one of the fastest-growing jobs inside of Microsoft is forward deployed engineer. This is a position that has not existed a few years ago. Satya expects to see a lot of reorganized inside of Microsoft where teams become smaller and roles change, and the voluntary exit program is an opportunity for people who leave who don't want to go through what will probably be a really intensive period of change, much more than before. I would assume that this kind of change with reorganized and role changes, all of these being more intense than before, is probably not just true for Microsoft, but it will be true for a lot of other tech companies. In the end, I walked away being more energized from this conversation. Yes, the industry is changing, but what I understood is how Satya sees that a lot of software engineering work is waiting to happen with these new AI-related primitives like decision models and some of the primitives that have not been invented, and us engineers will need to build these new systems with these new primitives, deciding what goes where, how to change it, what makes sense, how to deploy it, and just keep learning from it. Do check out the show notes below for related deep dives on AI engineering concepts like evals, inference engineering, loop engineering, and more. If you enjoy this podcast, please do subscribe on your favorite podcast platform and on YouTube. A special thank you if you also leave a rating on the show or share with colleagues or friends. Thanks, and see you in the next one.