
Gergely's new podcast with Satya Nadella asks what software engineering looks like when the work is verifying code rather than writing code: Build the form, let the agents run, then validate the result.
What does software engineering look like when generating the code becomes cheap and verifying it is the hard part? A rare podcast focused on everything around building software, with @satyanadella. Timestamps: 00:00 Intro 02:12 Microsoft’s open-source shift 04:15 Building VS Code in the open 05:55 Copilot, Cursor, and Claude Code 09:52 Decision engines 12:32 Verifying AI-generated code 15:39 The software factory 20:45 Bringing AI to existing products 24:06 Why adopting AI is different to adopting React 26:29 The changing role of software engineers 29:25 Microsoft’s voluntary exit offers 34:05 AI anxiety and changing roles 36:35 Junior hiring 42:36 Open models 45:39 Owning your AI infrastructure 51:21 Building trust in AI agents 53:48 Local models and hybrid intelligence 56:39 Microsoft’s model strategy 59:26 Advice for engineers 1:01:21 Closing takeaways Brought to you by: • @turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. turbopuffer.com/pragmatic (I built a greatly improved podcast/newseltter search with it, check it out: pragmaticengineer.com/search) • @linear – the product development system for teams and agents. linear.app/pragmatic • @WorkOS – everything you need to make your app enterprise-ready. workos.com/ 3 interesting takeaways from Satya: 1. A new form of software engineering: teams building software factories to improve their work. Satya cites the Azure networking team which manages 500+ fiber network operators and recently built an agentic system to better manage emails and processes. Now, they operate much more efficiently as a result. Satya sees this as the reality of “AI transformation”: brownfield work on building software factories to improve how teams operate, all while continuing the day-to-day work. 2. “Own the intelligence”: avoid lock-in & treat agents as an insider risk. Satya cautions companies to avoid lock-in with any single model provider by ensuring that the harness, memory, and model are not coupled, so that they can be changed with ease. He also thinks more companies should consider using open models as a way to protect their core intellectual property (IP) from leaking out, and build private evals to decide what models to use and upgrade to. He also says that models are intelligent but unreliable, so it’s best to treat them as “insider risks” and build a separate system to verify that agentic systems work as expected. 3. What’s with those voluntary exit offers? I asked Satya directly why Microsoft recently made voluntary exit offers to most of its software engineers for the first time in the company’s history. I also wanted to know if it could mean layoffs in the future. Unsurprisingly, his reply was diplomatic, but in the podcast I rehashed what I heard in a more direct way.










