1. Podcasts
  2. The MAD Podcast: How AI Gets Built — with Matt Turck
  3. GitHub CEO: The AI Coding Gold Rush, Vibe Coding & Cursor
The MAD Podcast: How AI Gets Built — with Matt Turck

12 Jun 2025 · 1h 5m · 21 chapters

Episode artwork

GitHub CEO: The AI Coding Gold Rush, Vibe Coding & Cursor

In short

GitHub CEO Thomas Dohmke discusses the “AI coding gold rush,” focusing on GitHub Copilot’s evolution (autocomplete → chat → agentic workflows) and GitHub’s strategy in the competitive-but-collaborative AI coding market. He explains GitHub’s 2018 Microsoft acquisition rationale, how GitHub ties into Azure, and why “coding agents” (Agent Mode) are the next wave.

Guest backgrounds

Thomas Dohmke is CEO of GitHub (acquired by Microsoft in 2018 for $7.5B). He previously worked on the acquisition strategy and describes early GitHub involvement with OpenAI’s Codex via Microsoft’s partnership.

Key claims

Current models already enable more than people expect; Copilot’s “magic flow” keeps developers in their editor without context switching; GitHub’s “choice” strategy spans multiple model providers and BYO keys; fine-tuning is less valuable than tool-using agents with context (MCP); Microsoft’s DNA is to compete and partner simultaneously.

Notable examples

GitHub’s Copilot Agent Mode runs tasks in the cloud by spinning up a VM, checking out repos, installing tools, writing code/tests, and submitting PRs. GitHub Models (Aug 2024) and multi-model Copilot (Anthropic Sonnet/Opus, Google Gemini) are cited; Copilot shipped June 2021, with Codex-trained confidence from ~230 interview exercises solving >90%.

Written by AI. May contain mistakes.

Chapters

0:45

The Rise of AI Coding Agents

Discussion on AI coding agents, their impact, and collaboration in the market.

“and fast-growing nimble startups like Cursor.”
2:28

The GitHub Acquisition by Microsoft

Exploration of the strategic thinking behind Microsoft's acquisition of GitHub.

“and in-depth conversation about all the things, both for coders and non-coders to understand where it's all going.”
6:22

GitHub's Role in Microsoft's Ecosystem

Analysis of how GitHub contributes to Azure and Microsoft's developer tools.

“The hyperscaler business model is, you know, generally described as building a bunch of applications that drive demand for the underlying compute.”
9:58

Innovations and Challenges in AI Development

Insights on GitHub's early innovations and the challenges faced in AI coding.

“GitHub Actions, all the open source on GitHub, consuming that, contributing back to it.”
14:01

AI in Autocompletion: A Historical Perspective

Learn about the evolution of AI in autocompletion and its implications for developers.

“The other thing that's easy to forget is autocompletion has been around forever.”
15:40

Understanding GitHub Copilot's Functionality

Discover how GitHub Copilot enhances developer workflow by facilitating coding tasks.

“And it feels strange looking back now to summer 2022, three years ago, when co-pilot G8 and how many people were still doubting that this technology is any good and will become a standard tool for developers.”
18:22

Real-World Applications of Copilot for Students

Hear personal anecdotes of how Copilot assists young learners in programming.

“and it's just flowing from top to bottom in the file and it feels like you're changing the world.”
20:46

The Evolution of AI Models at GitHub

Explore how GitHub's AI models have transformed and the importance of model choice for developers.

“2025 is all about, is agentic scenarios.”
22:45

Navigating the Landscape of Model Choices

Understand the significance of offering developers a variety of AI models.

“And what really, you know, it is about choice.”
24:41

Challenges and Future of Fine-Tuning AI Models

Learn about the complexities and future considerations of fine-tuning AI models for specific environments.

“Or you offer the choice and then the enterprises can stick with a model that they feel is the one that is the best for them and approved and reviewed by security and compliance and all that.”
Show all 21 chapters
28:00

Understanding Agent Capabilities in Coding

Learn how AI agents enhance coding by understanding the coding environment and automating tasks.

“And so they can call tools on the command line to install a Maven package or an NPM package.”
29:10

The Political Economy of AI in Development Tools

Explore the rapid innovation pace and the transformation of developer tools in the AI landscape.

“I'd love now to talk about, let's call it the political economy of this whole space, for lack of a better term.”
36:53

Collaboration and Competition in the AI Ecosystem

Discover the dynamics of collaboration and competition among AI companies and how they impact developer tools.

“But as a side matter, you've diversified away from one supplier.”
41:29

Navigating Product Decisions in AI Development

Understand the challenges and strategies in making AI development decisions within large organizations.

“I'm curious what it feels like from the inside, you know, running a very important major division as part of the broader ship when it comes to product decisions.”
42:03

Microsoft's Approach to AI Development

Learn how Microsoft manages its AI initiatives within a large organizational structure.

“and then another part of Microsoft needs to make sure that VS Code remains very versatile, broadly applicable to lots of different use case and scenarios.”
46:44

The Bear and Bull Cases for AI Companies

Understand the challenges and opportunities that AI companies face in a competitive landscape.

“I was curious what the bear case is for them, like the reason why they're going to be, you know, a roadkill from the power of Microsoft and perhaps Google.”
50:00

The Future of Coding Agents in Software Development

Explore the role of coding agents in revolutionizing software development and task management.

“And so both the bear and the bull case are actually very similar, which is, can you predict what that looks like?”
54:49

Using the Coding Agent: Features and Benefits

Discover how the coding agent works and the specific tasks it can automate for developers.

“where the coding agent works asynchronously.”
56:00

Understanding AI Coding Agents and Their Benchmarks

Explore how AI coding agents work, their benchmarks, and user feedback.

“Although even there, you can start with brainstorming a cycle first.”
1:00:02

The Future of Coders in an AI-Driven World

Discuss the evolving role of software developers with AI integration.

“To close, it feels almost inevitable when having a conversation about AI coding in 2025 to not ask about what that means for the broader industry in the broader world.”
1:02:30

The Impact of AI on SaaS and Application Development

Analyze how AI will change SaaS value propositions and complexity.

“And I think, you know, everything that I can easily replace with a single prompt is not going to have any value.”
A man walking through an airport, asking his phone a question

Ask about this episode

Get the gist, explore an idea or ask about something said.

Claude

On The MAD Podcast: How AI Gets Built — with Matt Turck, what are the key points of this episode?

Searching your listening

Transcript

Automatic transcript. May contain errors.

0:00I think we're underestimating how much you can do with the models that are out today, not the ones that are coming next year or next month. We are only touching the surface of what's possible. Welcome back to the Matt Podcast. Today, we have a fantastic conversation with Thomas Dohmke, the CEO of GitHub. Now, of course, GitHub is the world's largest developer platform. Once upon a time, a scrappy startup, GitHub was acquired by Microsoft in 2018 for$7.5 billion. And today, it serves 150 million developers and generates around$2 billion in annual recurring revenue. GitHub is also sitting today at the epicenter of the hottest space in generative AI, AI coding, where hyperscalers like Microsoft and Google face off against AI giants like OpenAI and Anthropic and fast-growing nimble startups like Cursor.

0:48In this episode, we talk about the rise of AI coding agents, including GitHub's brand new co-pilot Agent Mode. The coding agent is like a new member of your team that can take on certain tasks. And you can not only assign one task to one coding agent, you can assign 10 tasks to 10 versions of that coding agent. And they can all run in parallel. How to understand the current AI coding market and the delicate balance between competition and collaboration amongst players. It's the DNA of Microsoft to be competing and partnering with many companies in the industry. As well as the future of software and code development.

1:23AI is going to accelerate the role of a professional software developer, and it's also going to enable everyone that wants to become a developer to learn coding. This is a very educational episode packed with insights for both developers and non-developers interested in understanding where AI is going. Please enjoy this great conversation with Thomas Domke. Thomas, welcome to the Mad Podcast. Mad, thank you so much for having me. Great to have you here today. I've been very much looking forward to the conversation because AI coding is such a fascinating area. It feels like ground zero for all things generative AI.

2:00First, it's arguably the most widely adopted application of generative AI today. It's where a lot of innovation is happening. It's where some of the questions around is AI going to take our jobs or not feel the most real. and then it's like a big battleground as well from a business standpoint between the hyperscalers and the startups and the big AI labs. So what I'm hoping to do today is have a very educational and in-depth conversation about all the things, both for coders and non-coders to understand where it's all going. Does that sound good? Sounds great, and it's also, I think, one of the oldest use cases for AI.

2:39Yes, perfect segue. Let's go back to in history a little bit. Let's talk about 2018, which was the$7.5 billion acquisition of GitHub, which had been a startup for over a decade by then, by Microsoft. And you were deeply involved in this. Walk us maybe through the strategic thinking behind the acquisition at the time. $7.5 billion seems cheap now that we're in 2025 and you see all these startup valuations. I think Microsoft has always seen itself as a developer tools company. It's a platform company. And to be successful with a platform, you need to have developers on your platform that build apps, services, products on top of it, but also build an ecosystem around the platforms.

3:27And Microsoft back 50 years ago started with a basic interpreter for the Altair. and then you fast forward and in the 1990s, Visual Studio came in the 2000s. There was TypeScript and.NET and that ecosystem. And in 2018, a lot of things had changed under Satya Nadella, Microsoft's current CEO, which came into role in 2014, had changed that Microsoft started embracing open source. .NET was already an open source project. VS Code, the editor, was already on GitHub. And in fact, one of the biggest projects on GitHub in terms of number of contributions. And so we felt it was time for Microsoft to fully embrace its roots as a developer company and bring in all these web developers, those that are building apps, is now called cloud native and bring them into the Microsoft ecosystem.

4:28So I think that was the primary motivation, bring those developers that are on GitHub, that are building in the open, or on startup projects, their private projects, and increasingly in the enterprise as GitHub in the late 2010s, more and more also embraced the enterprise and started selling a server, GitHub Enterprise server, and a business product in the cloud. And so bring that into the Microsoft ecosystem. And two years before the GitHub deal, the LinkedIn deal had happened. So 2016, Microsoft had acquired LinkedIn and had kept LinkedIn somewhat independent from the big mothership. And so we also had a template of how to do such a deal where we retain a lot of the value of the deal by keeping the company independent.

5:19And the three principles that we set back in 2018, they're actually still true today, which is GitHub always puts the developer first. And so that's what drives all the decisions, the design, the product processes, how we think marketing blocks our conference. We have Microsoft accelerate GitHub. And I think that is a crucial part of how everybody should think about acquisitions, which is the buyer should accelerate the target company. It's almost like a venture capitalist investing into a startup, right? You invest money to accelerate the company you're investing into. When you're acquiring a company, I think you should have that same mindset.

6:03I'm buying a company to accelerate them so they increase their value. And as such, I'm increasing the value of the buy side. And then lastly, we also thought about GitHub accelerating Microsoft. And here we are in 2025. And then the easiest example I can give you is how GitHub accelerated Microsoft is, of course, GitHub Copilot. So just to build on those two points, which are super interesting, the GitHub helping Microsoft, to which extent does GitHub fit into the Azure broader picture? The hyperscaler business model is, you know, generally described as building a bunch of applications that drive demand for the underlying compute.

6:45Is that one of the key objectives? And what is the intersection between GitHub in general, GitHub Copilot in particular, and underlying Azure business? The Azure business within Microsoft came out of a division called Server and Tools. Today, that division is called Cloud and AI. And the Server and Tools team also had the developer division. But this core product back in 2018 being Visual Studio, you know, in itself, the IDE, you know, the old school IDE in itself, a billion dollar business and had a bunch of new stuff like Visual Studio Code. It had a platform for DevOps, back then called Visual Studio Team Services, nowadays called Azure DevOps.

7:24And so that tools division within the cloud, within Azure, had the job of providing the ecosystem, the tools, the platform for developers to build on top of Azure, to build on top of Windows, to build on top of other Microsoft platforms. And GitHub snapped into that developer division and bringing basically the open source platform, the home of all developers into that same ecosystem. From a business perspective, that meant the GitHub revenue became part of the Azure KPI that is reported in earnings calls every quarter from Microsoft. And we announced last July, so almost a year ago, that GitHub had passed$2 billion in annual revenue run rate ARR.

8:10And you can go back in time, 2017, a year before the deal, then GitHub leadership team had announced$200 million in ARR. So those are not exactly snapping to the timing of the deal, but you get an idea between 2017 and 2024, revenue went 10x, right? And as such, the first thing I want everybody to think about when you ask, you know, how is GitHub contributing to Azure? Well, it contributes to Azure's revenue number by increasingly, you know, generating more and more cloud revenue. And of course, Copilot is a big part of that cloud or an increasing part of that cloud revenue. We bring developers, new developers, students, even high schoolers, sometimes middle schoolers and increasingly younger kids as well.

8:53Often the motivation is actually less that they want to learn coding. That is also true. But I was in one of my sons' middle school last year and I asked them about GitHub. And they're like, yeah, that's why we find an old Minecraft build that works on the school laptops and isn't detected by IT, probably because it runs on some older file that isn't fingerprinted by school IT or what have you. But it brings developers into the platform, into the Microsoft ecosystem. And the ultimate hypothesis is that they go through their career journey on GitHub and learn about Microsoft tools, whether it's a VS Code and Visual Studio, whether it's the cloud in Azure.

9:35And of course, we have within GitHub a number of integration points where you can deploy your repository to Azure and something called GitHub Actions, our CI, C &E service, where it suggests the Azure Kubernetes service, for example, to deploy a Docker file. It's the other way around, which is the Azure teams obviously are also leveraging GitHub for their work, whether it's GitHub itself, whether it's GitHub Copilot, GitHub Actions, all the open source on GitHub, consuming that, contributing back to it. So when we think about developers at Microsoft and developer tools at Microsoft, we always should also think Microsoft is one of the biggest software development companies itself.

10:15So it benefits from every innovation that we're building into GitHub for its own backlog, for its own shipping velocity, quality, et cetera. The other thing that you mentioned a minute ago that's fascinating is precisely the fact that the acquisition of GitHub seemed to have been so successful in terms of keeping the spirit alive. And to put it in full context, one of the things I find amazing about this whole story is that you guys came up with co-pilot way ahead of anybody else in the market. In particular, you were a year before the whole chat GPT thing, you know, unleashed the entire generative AI craze.

11:01So you're very much early to this market, which when you think about big companies, that tends to be the other way around, right? Especially for people like me in the venture world, it's always like, you know, the startup moves faster than the big company. That was not the case here. What was the secret and the kind of management tricks and techniques that enabled you guys to do that? Tying it back to the acquisition, you know, one story I can give you is that beyond all the other reasons I gave you that we are part of the strategy document that we had to write to send it to Satya and then for Satya to go to the Microsoft board and ultimately get approval for the deal.

11:37One additional thing was, in fact, AI and saying we believe there's a future where we can train AI models on the graph, as I think what we called it, of all the source code that is stored on GitHub, but also on the relationships between the developers, how they work together. And so in 2018, obviously, we didn't know anything about Copilot, but AI was certainly a reason to do the deal. comes 2020. And in the meantime, Microsoft had invested into OpenAI. I think that was in mid-2019. And GPT-3 was on the horizon. And we got early access because of the partnership between Microsoft and OpenAI. And we played for the model.

12:22Just like, you know, today you play with a new model whenever a new one comes out, which feels like it's every other day. And we ask it, you know, to write methods, like prime number detection, sorting algorithms, those coding exercises available. In fact, through that process, we looked at our own coding exercises that we use for our interview loops. And I think we collected about 230 or so of them and ran them through the model, which then was called Codex. So OpenAI fine-tuned a model based on the open source code on GitHub and other sources. And I think there's a paper still still on some of these Arbix or whatever the page is called that describes exactly how Codex was trained.

13:09I think the model was able, with multiple attempts, to solve more than 90 % of these coding exercises, of these 230 coding exercises. And that ultimately gave us the confidence we can build a product here. So this is 2020, two years and a bit before ChatGPT. But actually conversational coding is what we called it, It was one of the ideas we had. And the only reason we didn't ship that was that it wasn't good enough. And we were quite skeptical shipping something where everybody looks at this and, you know, asks in a chat interface, you know, describe this method or ask, you know, the typical chat scenario that we all now used to.

13:48And it often gave incomplete answers or wrong answers. And so we felt like we can't really do this and then ship this to developers. were going to get all the ridicule on social media. The other thing that's easy to forget is autocompletion has been around forever. Microsoft, I think, shipped IntelliSense, which is like the somewhat intelligent autocompletion in the 2010s. And in fact, even that was debated by developers because the worry was that if it can predict the next word and the method name, I have, I think the term was brain rot. I'm going to forget, you know, my skills. And so that question of, is AI going to replace the developer and make us all less skillful at lower level of craft, that goes as far back as IntelliSense.

14:46And I remember first using TextMate in 2004 or 2005. And it felt magical to me that it could autocomplete even stuff that wasn't in the Ruby and Rails app that wasn't even in the documentation because it would pass the file and create a dictionary of the file I'm working in. And so it could predict the next, the method name that is actually part of the code I vote. And then Microsoft evolved IntelliSense into IntelliCode, which was IntelliSense with AI using a local model to do better predictions. So that was already AI. It just wasn't a large language model, a transformer model as we used for Copilot.

15:27But all these steps ultimately set us up to ship Copilot, the original Copilot, in June 2021, more than a year and a half before the big bang of AI. And then we brought that into production within a year. And it feels strange looking back now to summer 2022, three years ago, when co-pilot G8 and how many people were still doubting that this technology is any good and will become a standard tool for developers. And here we are in 2025 and all of that has happened. And you see many CEOs in AI and outside of AI predicting these co-pilots are going to write 90, if not 100 % of all code. You know, again, in an effort to make this interesting to both a developer coder audience, but a broader audience as well.

16:16How would you describe GitHub Copile in two minutes? And how does that interface with VS Code? And what is VS Code? And so if I'm a non-developer, what does that all mean? The way I'd like to start describing what GitHub Copile does is describe what a developer's job actually is, which is writing code. And so most developers in the morning, they go somewhere where they have their backlog, you know, the tasks that they define themselves or often that comes from their manager or from their product team. And they pick up a task and then they go into an editor, which is, you know, ultimately a program where I can edit files with plain text.

16:53And the key skill of a developer is to take this description that is in human language, because that's what all the specs, all the issues, all the bug reports are in, right? like in English, German, French, whatever language the stakeholder used, the key job of the developer is to translate that language into code and to take human language and transfer it into programming language. And so they type code. And as any writer, whether it's a coder or whether it's a journalist or a VC writing a blog post, it's really hard to do that because you're getting stuck when you have an empty file. You're getting stuck because you don't remember specifically how to call.

17:32method or how to do a certain algorithm connecting to some backend system and so on. And so what you did before Copilot would command tap or alt tap on your computer into a different application, often the browser, and try to find that information. And you do that by opening a new tab and using Google or Stack Overflow, GitHub, lots of platforms, Reddit, that have developers talking about these problems and then figuring out what's the answer to the problem I'm trying to solve. and 10, 15, 20 minutes later, you're back in your editor and you copy and paste that code snippet that you found somewhere and then you make it work within the file that you were working on.

18:12And so Copilot does all of that without that context switch. It keeps you in the flow. Developers often call this the magic flow state where you have an idea, you know what you're doing, and it's just flowing from top to bottom in the file and it feels like you're changing the world. And you want to stay in that state for as long as possible. You want to, you know, surf the wave, if you will, without falling into the water and having to paddle back and find a new wave. And so Copilot, the original Copilot did that by suggesting multiple lines of code, you know, instead of just the next word that could complete, you know, five, 10, 20 lines of code.

18:51And you would just accept that with the tab key or you would keep typing until it was good enough for you to say, okay, I can now press tap and then edit this a little bit to make it work because most developers also are very used to trial and error, trial and error. That's how we all learn coding. And so Copilot does that autocompletion and that continues to be the most used features because it's always there. The magic of Copilot in the early days was it wasn't really about AI. It wasn't about large language models. It was about giving you a feature in your editor that keeps you in the flow state and makes you more productive and ultimately more happy.

19:30And then came ChatGPT. And of course, we added the chat scenarios and that allows you to do all kinds of exploratory things like asking questions and describing code, telling the chat part to fix a bug. And I bought both my kids a Copied license because before they would always come to me and say, hey, my Python, of course. That also let me test the payment and the billing flow. And so I get free emails from GitHub every month, one for my own account and then one for each of my sons. And so I'm, you know, a customer zero, as we would call that. And, you know, before that, they would come and say, hey, I'm building this Python Pi game, a little jump and run platformer and I have a bug and I can't figure out how to solve that bug.

20:18And then I was like, well, you know, I'm talking with Matt right now, but I come to your room in an hour. And of course they don't like that because their stuff is way more important than your podcast, Matt. Priorities, priorities. And so I bought them co-pilot. And, you know, now they're just asking co-pilot, you know, help me to fix the bug. And it doesn't have to be perfect. I'm not perfect either when I help them, right? I try to understand what they did. So does co-pilot. And so that's the second scenario. And then the third one, and that's really what, you know, 2025 is all about, is agentic scenarios.

20:53We call it agent mode in the IDE. We have the coding agent on the platform. Instead of just asking questions and getting answers, you can give a task and it does that task for you. You mentioned that initially GitHub Copilot ran on Codex, which was the early coding model from OpenAI. I think at the end of last year, 2024, you introduced GitHub Models, which feels like a library of different underlying models you can use. Walk us through that. How does that work and what can you do as a developer? In 2024, we did two things. GitHub Models was early August and that gives developers access to catalog of models integrated into the GitHub platform.

21:38And in fact, last month, in May 2025, we brought these models into the repository. And so you can integrate these models into your repository to build AI scenarios into your own applications. And that's really cool because you don't have to go to another place and sign up for a new account, and then you have your model stuff here and your code on the other side. GitHub ultimately was always about millions of developers collaborating on a project together. And so our philosophy is we bring what we call the primitives that developers need into the repository, issues, wikis, pull requests, actions, And now models.

22:19And then late, I think it was late October, we announced multi-model choice for Copilot, moving from just having one model provider, OpenAI, to having multiple model providers for Copilot Shack and for now Copilot Agent Mode. And so we added back then Anthropic Cloud 3.5 Sonnet. And now it's Anthropic Cloud Sonnet 4 and Opus 4. And we added Google Gemini back then 1.5. Now we are 2.5 Pro. And what really, you know, it is about choice. We fundamentally at GitHub believe that we need to offer developers choice. Right. You wouldn't be using GitHub if it only had one open source project or one programming language or one ecosystem.

23:04Like we are not the ones telling developers whether jQuery or React or Next.js or whatever the next thing in the JavaScript ecosystem is, whether those are the ones to pick. We are offering all these projects at home where they can collaborate and innovate. And we let the developers, the teams, organizations choose which of these ecosystems they want to participate in or consume. And we believe the same is true for models. There is never going to be one single model that rules them all. But the world of software development is just way too broad for this. And that's also, I think, where the benchmarks, it's the right word, dangerous, I guess.

23:43Because, of course, there's a big difference between writing code in C, C++, or even Assembler, to writing code in TypeScript or Python. And often, if you look at these benchmarks, the devil is in the details. You have to do the double click and see, you know, how does it do for my language for a documentation scenario or for test generation scenario? And in fact, you know, nowadays in VS Code, we not only have the models that we offer on our inference API. We also have bring your own keys. We can connect Copilot to OpenRouter or OLAMA. It can run a local model and try out that model in Copilot to build your own agentic behavior into your developer workflow.

24:29So that's what it's all about. And that also enables us to move really fast, which has become incredibly important in the AI space. I've never seen anything like that in my 30-year career as a software developer. There's so much innovation, so much change happening that just sticking with one model will ultimately mean you either are really, really good at change management with all these tens of thousands of enterprise customers. That's the hard nut to crack. Or you offer the choice and then the enterprises can stick with a model that they feel is the one that is the best for them and approved and reviewed by security and compliance and all that.

25:10And then there's all the other models that we can offer other customers and individual developers, those that want to stay at the cutting edge. So that's the other part of the choice being important. If you want to move fast, you ultimately have to support multiple models because there's always going to be a group of customers that intentionally want to move slow given the regulated environment they're operating in. And for the enterprise, do you allow people to fine tune their model based on their data? How does that part work? We do not today. We have pursued that path in the past. So I think 2023, 2024, a number of companies in our space saw fine-tuning as the next opportunity.

25:55The challenge, from my perspective on fine-tuning, is that, A, there's another model every other day. You're ultimately always going to be behind with your fine-tuned model. and we are putting you then in a position where you're having the choice between the model that you fine-tuned that is based on an older version of the base model, or you can pick the new model, but that isn't fine-tuned yet. B, I think most customers' code bases, especially if you look into the individual project, most companies that are at a certain scale have not just a single programming language and a unified stack. That's the dream every CIO or CTO is talking about.

26:38Like, I want a standardized stack for all my developers. And then you look into a 30-person startup. And of course, even they don't have that because as soon as they go from web development to iPhone development to Android development, they already have three stacks. And so then if you look at the individual repository or set of repositories, that code base isn't actually big enough to have a meaningfully fine-tuned model. And lastly, I think this is where fine-tuning got left behind by most companies in the space, is that when customers think about fine-tuning, what they really mean is that the agent understands the code base and the environment that that code base sits in.

27:18But, you know, that's not only the code that was relevant during the fine-tuning process, because you can always have a new open source library being added or you're upgrading from one React version to another and now your API change or from one Java version to another, even simpler. But it's also everything else that's surrounding that project, your database schemas, whatever solution you're using for feature flagging and experimentation. There's all these services that surrounds your project that provide additional context that the agent needs to know about. And so now in 2025, I think the answer is very clear, which is MCP, Model Context Protocol, and the ability for models to call tools.

28:01And so they can call tools on the command line to install a Maven package or an NPM package. They can call an MCP server that connects into your GitHub repository or into your Jira and Confluence institutional knowledge. And then there's a thousand MCP servers for everything else. So if you want to connect to Figma or you want to connect to your Mongo database or what have you, you can put in all that context. So the agent actually knows as much about the environment that the code base sits in as the human developer. And so using MCP, using cool calls, and then whether it's retrieval or just navigating the file tree and doing code search like a human developer does.

28:43And if you have used agent mode or any of these agent modes, you can actually see that working. how it uses the chain of thought to go from, okay, it's three files, or maybe I need to add two more files. So now it has picked five files that it needs to modify. And it figures out that it not only needs to write the code, but also write the test cases for it and then run the tests and fix it itself. So this iterative process that the agent does with the help of the tool calls in all the context makes it so much more powerful than a fine-tuned model could ever be. All right, amazing. I'd love now to talk about, let's call it the political economy of this whole space, for lack of a better term.

29:20You mentioned the incredible pace of innovation, and indeed it's dizzying, right? Just over the last few days, it feels, you know, Mistral announced a coding product that's a combination of the various underlying coding models that they had. Cursor officially announced their round at a, I think,$9 or$10 billion valuation and said that they were at 500 million in AR, which is kind of insane and makes them possibly the fastest growing startup of all times, at least on the enterprise side. You know, the Sonnet 4 that you mentioned earlier that came out, what, two weeks ago? It feels like old news, but that was like two weeks ago.

30:01So the pace is absolutely dizzying. What you make of it and how you would categorize it, like who does what and where do you guys fit in? And what do you cover? What do you not cover? First of all, I think, you know, we should recognize how amazing it is that a developer tools company is the fastest growing startup of all time. Because there were times, you know, between 2018 and now that you would go to, you know, a startup founder or a venture capitalist and they wouldn't want to invest into that space. And 100%, I'm so glad you said that. That was such a VC trope that don't invest in developer tools because developers are very cheap people.

30:42They will never pay any money for anything. And yeah, there you go. There's no money to be made. And here we are. And second, I think it shows that AI is going to accelerate the role of the professional software developer. And it's also going to enable everyone that wants to become a developer to learn coding. And you can see that with Copilot and a bunch of these tools. where a selfie, zero-bold, lovable, open-air codecs where folks with a non-technical background can build a quick web page. Now, and I think this is good to anchor ourselves, we have been living in a world for quite a while where companies were pitching no-code or low-code solutions.

31:30In fact, I think 15 years ago, I set up my first Squarespace web page. And even though I knew how HTML and CSS works, That was still the faster and cheaper way to just spin up a quick web page and publish. I think it was the landing page for our startup back then. And just say, here's the signup field. Let us know if you want to get informed when we're launching. With AI, we're going a step further because now you can use AI agents to generate quite complex applications. From web pages to little games. My favorite demo is the Bullsnake game. because it's a bit quick to build and quick to play without explaining too much how it works.

32:12Most people still remember Snake on their Nokia phones or whatever phone they had. And so if you look into the space now, you have companies that are working in this bootstrapping or we like to call it greenfield scenario. You stop with nothing, you enter a prompt. It's almost like using an image model. You enter a prompt and it generates an image, but instead of an image, it generates you a webpage, an application. and then you either like what you see or you want to add more or change things and you keep prompting. And in fact, the image model is a great, I think, comparison because in the same way that the first output of an image model almost never is perfect and exactly what it did in your head, the same is also true for these bootstrapping AI scenarios.

32:55So that's, I think, one category. One is IDEs. You already mentioned, you know, there's a bunch of others that have taken VS Code forked it and made it a new version. And that's the power of open source, right? The power of open source of Microsoft making VS Code open source back 10 years ago in 2015. But there's also the traditional IDEs, Visual Studio, the JetBrains family of IDEs, even Apple with Xcode. Everybody is integrating AI scenarios into these IDEs, and many companies like ours are providing co-pilot not only for VS Code and VS, the Microsoft IDEs, but also for JetBrains, for Eclipse, for Xcode, for Android Studio.

33:38And then there's forks of our code base to bring it into Emacs and what have you. So the IDE is the hardest playing field, I'd say, simply because that's where the majority of professional developers are. And the key of successful developer tools has always been you've got to meet developers where they are and then move them into that, that future that you're seeing as your North Star. But what doesn't work is to give them the new thing and tell them to stop everything that we're doing until now. That's going to create an allergic reaction. It's like, go away. I know what I'm doing. I'm used to my shortcuts and my color schemes and all these kind of things.

34:21Then there's the model companies that provide the models that power all these scenarios, but they have entered the space itself, whether it's OpenAI Codex, Cloud Code, MISTRA Code. And I think part of the reason for that is that AI code generation is a scenario that worked first and has the largest part of the respected workforce having adopted it. As in, most developers have adopted some form of AI tooling into the workflow already, while other knowledge workers, other white-collar workers, are still early in that adoption journey. And they might use a chat agent as kind of like a better version of a search engine to find a document or to summarize an email.

35:06But they haven't replaced parts of their workflow with AI. Which brings us to the fourth category, which is agents. And these agents, what separates them from the bootstrapping Greenfield scenario is that these agents work in brownfield, as in they are working within an existing code base for the coding agent or within your Azure cluster to monitor all your resources, the SIE agent, and then look at exceptions or monitoring data and then file a GitHub issue and say, hey, you know, the latest deploy has created an exception. and you can tie those together and have the SIE agent file an issue and then the coding agent pick up the issue and provide the pull request and then the human developer comes back in again to review the code change.

35:47And what's interesting about these four categories is that while there's startups in each of them, there's also companies like Microsoft and GitHub that operates in all of them and tries to provide a holistic platform across all these scenarios. And I think the key for winning is to have a continuum where you can have an agent write code for you and submit a pull request. But then if you, as a developer, see that code and you want to make three quick changes, you've got to be able to take that onto a local machine and just make those changes instead of trying to figure out how do I provide now feedback or prompt to describe in natural language where I already know how to do it in programming language.

36:31That's basically replacing something that I can do in three seconds with something that might potentially take three minutes or even longer. And that's obviously not more productivity, that's less productivity. And so enabling developers to move between those categories and being able to pick the agent that provides the best ROI or do it themselves. I think that's the key for winning in the next few years. This is so fascinating in so many ways. To take your third category of the AI labs, so there's this competition and collaboration relationship that's starting to appear where obviously Microsoft has a very special relationship with OpenAI, but through GitHub models that we were just discussing, you've diversified and you've offered choice for your users, which is the key driver.

37:23But as a side matter, you've diversified away from one supplier. That tension also between Anthropic potentially and Cursor, where Cursor has started to diversify away from them. So how do you view this evolving? Ultimately, everybody competes, but also cooperates. Or is there a moment when, I don't know, you guys maybe need to develop your own model specifically for coding? How do you view it evolving? It's the DNA of Microsoft to be competing and partnering with many companies in the industry, right? The most classic example comes to mind is that Microsoft for the longest time has sold software or provided software nowadays for the Mac, going back all the way to the Apple II.

38:15I think most of us remember Bill Gates appearing in a Steve Jobs keynote, big on screen behind him, to announce that Microsoft is investing into Apple and bringing Internet Explorer and Office to macOS. And then, of course, after Asatia became the CEO, the decision was made to bring the Office suite onto the iPad. And nowadays, we take it for granted that Office Teams Outlook, all the modern Microsoft applications run on a Mac and run on iPhone and Android. And as such, I think, you know, and I learned that when I joined Microsoft 10 and a half years ago, it was weird as a startup founder to come into the company and realizing that what I considered competitors for the product I owned at Microsoft are often also partners.

39:09I can't name any names, but, you know, many of these AI cogeneration companies that compete with GitHub Copilot are running their inference on Azure AI Foundry. And as such, they're paying Microsoft for the lower parts of the stack. And obviously, Microsoft's cloud business with Azure doesn't want to say to customers, you can't run on us because you're competing with one of our products. We have so many products that would hurt Microsoft's business. So it is part of our DNA to both partner and compete. And I think in many ways, that is the incredible thing about the tech ecosystem that that is possible.

39:50So Meta, AWS, Google, they're also all hosting their open source on GitHub. And as such, they are, you know, in one form or another GitHub customers. And so we really enjoy being on both sides of that spectrum. And I think it increases the energy that we have within Microsoft, within GitHub to say, okay, we'd love to partner with these companies and developers in developer space even more so. because like, look, if we would just exclude parts of the ecosystem, that means those developers go elsewhere and, you know, pay for its subscription or do their business with somebody else in the industry.

40:27Instead, we see ourselves as part of an ecosystem, as GitHub, you know, hopefully being, you know, one of the bigger planets, one of the core planets, you know, in Star Wars. And then, but there's a huge system, mid-rim and outer-rim, to stay within the metaphor. And companies that are closer to us and sponsor in our conference and have active partnerships and building active integrations, even though they're competing. Devon, as one such company, comes to mind. And others that are farther away, but obviously still a part of the developer ecosystem and that integrate with GitHub, use GitHub identity or store their source code.

41:04And so if you take it back to AI co-generation, all these companies ultimately allow a developer to submit a pull request or have the agents put the pull request onto GitHub. And as such, we have to be partners to enable those customers that pay us money for their repository, for their pull request, to choose the tools that they want to have part of their platform stack. I'm curious what it feels like from the inside, you know, running a very important major division as part of the broader ship when it comes to product decisions. A big part of the value proposition of cursor from the outside is that because they forked VS Code, they can have a product that's sort of all in on AI, very AI native in all aspects of what it does versus GitHub Copilot from what I understand where your plugin into VS Code.

42:03and then another part of Microsoft needs to make sure that VS Code remains very versatile, broadly applicable to lots of different use case and scenarios. Do you feel constrained by that in terms of how much you can do that's truly AI native because you need to operate in that framework where there are other driving factors? Not at all. And the VS Code team, while they don't report into me as the Gap CEO, They are part of the developer division that we're also part of. And together with the developer division, we're part of an organization within Microsoft called Core AI that has the whole AI stack in it as well.

42:42And so, you know, under Jay Parik, who's the leader for Core AI, we're forming one unit that competes in this age of AI with all these companies across the categories that I lined out. And as I mentioned, we're also partnering with them. So a different part of the core AI team might have one of our GitHub competitors as their customers and have partnership meetings with them and negotiate deals and Azure spend and those kind of things. Coming back to VS Code, at Microsoft Build in May, we announced that we are open sourcing the Copilot within VS Code, which also means we're moving it from an extension, which is how Copilot originally started, into a core part of VS Code.

43:29And so it becomes open source as part of the VS Code open source project or the code.OSS project. And as such, the VS Code team, and that's been true for a while, is actually the one building the client side of GitHub Copilot. And so for, I think, the last two years now, the VS Code team owns GitHub Copilot client side for VS Code. The Visual Studio team owns the Visual Studio Copilot, and then other teams in the developer division own Copilot for JetBrains, for Eclipse, and for Xcode. And in fact, the Xcode version of Copilot is an open source project from a maintainer that we took over. And it started as open source with an MIT license, and we did a commercial deal with the maintainer to transfer it into our GitHub organization.

44:17But we kept it open source. So the Xcode version of Copilot has been open source for quite a while because it started as an open source project and we decided that that open source maintainer and the contributors to that project did such a good job that it's better for us to pay him some money and take over the project instead of competing with that open source maintainer. I think the key for success at Microsoft is to leverage what is ultimately an incredible machine. And yes, it is a huge ship. And so changing direction sometimes feels really hard. But at the same time, there's so many incredible people that are working, you know, in the developer division, in the cloud division, in the AI division, that we don't feel constrained.

45:02If anything, I think the hard part in Microsoft is always going to be you have so many developers and so many employees that are supporting these developers in sales and support and what have you, that saying no to ideas is really hard. That's much easier when you're running a 10-person team because in a 10-person team, you know exactly what everybody's doing. And you're the 11th man that also is probably coding if you're the CEO. And so it's really easy to say, well, everybody's busy this week, so we don't have time for anything else unless somebody volunteers to work nights and weekends. But if you're managing an organization with, I think Microsoft all up has about 70 ,000 people in research and development.

45:46Not all of them are engineers, there's some product managers and designers, but the majority are writing code. Saying no to an idea is really hard. And so putting yourself into that mindset, yeah, we are big, but we still have to say no a thousand times before we say yes again. That, I think, is the constraint that we're having. And then figuring out what are the strategic bets and how we are competing in this market. How we're ultimately winning the race and realizing that there's always going to be another race and another race. We're playing the infinite game. As a 50-year-old company, yes, we want to win the news cycle every month, the Formula One season of 2025.

46:27But then we also want to still be here and relevant in the next decade and more to come. And that, I think, is ultimately what it is all about at Microsoft. We have always stayed the forefront of technology, and we want to keep doing that for as long as we're all here. You anticipated my question, which was what's the bull case and the bear case, you know, depending on which idea you look at it from, you know, on the cursor side, you could say they have the benefit of being constrained and being able to go all in and building one specific product and sort of attracting the kind of developers that already want pure AI.

47:06I was curious what the bear case is for them, like the reason why they're going to be, you know, a roadkill from the power of Microsoft and perhaps Google. So that's distribution, that's developer mindshare. You know, you're a very competitive guy and Microsoft is a very competitive organization. Like what why is the how are you going to crush them? I'm not thinking about crushing them because I think that's not, you know, how we are seeing the space. I like for developers to pick the tool they love most. And I like to build the ones that most of them are picking. And so I think realizing that in developer tools and in automated technology, there's always going to be multiple players.

47:50And some of them and some technologies stay around forever. Kobo and mainframes is one of such examples that comes up way more often than you would think for me as a good CEO, because many companies still deal with that Kobo and mainframe. Now, is that the state of the art and something that college kids get excited about? Of course not. But we should realize that once some software is deployed, it's incredibly sticky and it sticks around forever. and migrating things and migrating even a repository in our Formsup version into Git and then onto GitHub. That are often very complicated and expensive projects that engineering leadership only wants to fund if they can see the ROI.

48:32I think the bear case for any company in our space is missing out on the next big thing. And there's always going to be a next big thing in software demo, whether it's front-end frameworks, whether that's program languages, whether it's IDEs, maybe the IDE is going to be replaced by something much more web-based and you can in fact already do that by Copilot and assign an issue to the coding agent on your iPhone with the GitHub mobile app and then it does its work while you're maybe on a podcast and then it thinks and says here the coding agent has submitted a pull request and then you can review that code and you can even do that on your iPhone because reviewing code is fairly doable on a small screen.

49:14Writing is harder, mostly because of all the special characters and what have you. Predicting what is the next big thing and then being able to disrupt yourself and overcoming the innovator's dilemma that ultimately every company will get into that place where they have a moat, where they have an existing revenue stream. Even most of that revenue stream comes from many enterprise customers to then say, okay, we want to preserve that cash flow, But we also realize we got to disrupt ourselves and move into the next version. And you have heard, you know, many of the startup founders, CEOs, chief product officers of our competitors talking about that likely the world of AI cogeneration and IDEs will look very different in a year or two from now.

50:01And I think we all realize that. And so both the bear and the bull case are actually very similar, which is, can you predict what that looks like? and meet developers' expectations and have actually the user adoption that then justifies that disruption to your existing business. And at Microsoft, that is, you know, given the size of Microsoft, that is both an easier and a harder task at the same time. That's such a fantastic thought that the pace of progress actually creates an innovator's dilemma for everyone, not just for Microsoft, but actually probably for Cursor as they grow. They will also have a business to defend given how quick things are changing.

50:41That's such an interesting thought. GitHub has been pooled at least twice, right? GitHub was founded on Git, which wasn't invented by GitHub. It was invented by Linus Torvalds and the Linux kernel team. And a few years later, two years, I think, the GitHub founders, Chris, PJ, and Tom, saw an opportunity to say, Git hosting is so hard. Let's build a SaaS service. And in 2007, 2008, you know, that was a time when SaaS wasn't as established, certainly not cloud-based as it is now. And then we did this again with Copilot, where we again picked a technology that wasn't invented by us. Neither Transformer, nor the GPT model, nor the inference infrastructure came from us.

51:28And they came from OpenAI and paper, obviously, from Google and the infrastructure from Microsoft. And then we built, you know, the first Copilot and the first successful product in that space. And so, yeah, the big question is what's the next wave of that? And we believe it's coding agents. And that's why we are investing heavily into our own coding agent and in Copilot. And getting that from the 20%, 30 % benchmarks, if you would look at multilingual or 60 something percent for just Python, getting that to actually a number, I think 90 % is going to be the min bar for broad adoption and saying, this is now established technology and we need to look for the next big thing.

52:09That is going to be the challenge of the years to come. Yeah, let's double click on that for a few minutes. The launch of that agent mode was a major announcement, major new step in the history of GitHub that just happened at Build 2025 a few weeks ago. What does it do and what tasks in particular would you suggest people should direct it to? So the coding agent, the way it works is that you can just give it a task, coding task, documentation, generating test cases, or simple things like find all the bugs in my code base. The agent then, you know, goes off in the cloud and spins up a virtual machine and checks out the repository, installs other tools and solves that task for you.

52:54And the magic here is that in the meantime, you can keep working on your part of the code base on a different task, a different issue on your local machine. And so effectively, the coding agent is like a new member of your team that can take on certain tasks. And you can obviously not only assign one task to one coding agent, you can assign 10 tasks to 10 versions of that coding agent. And they can all run in parallel. And when they're done with their work, they submit a pull request exactly like one of your human team members would do. And then they alert you and say, hey, this pull request is ready for review.

53:33And then you go in and you review the code and you can comment on it. And the co-pilot will pick up those comments and keep iterating. And so if you don't like the code or, you know, I tested it yesterday with one of my hobby projects and I realized the readme is completely outdated because, you know, I didn't spend time on writing a readme for myself. and just told the coding agent, look at the code base and write a new readme. And then wrote a readme and reviewed the readme and looked at the headline. It changed the title of the readme from readme to something else. And so I gave it feedback and said, hey, I think the readme should always be called readme.

54:05And so he worked that change and it just did that, right? And so that's the most simple explanation that I can give of the coding agent. There is nuance here because there are going to be scenarios where now you want to take that code generated by the coding agent and check it out on your local machine. And you can do that with a GitHub command line and then keep working in VS Code. And of course, Copilot Agent mode is also available for you there. And so you can then use the agent in synchronous mode on your local machine. And so that's, you know, if you stay with the analogy of your team, that's like you pulled that team member that pulled the code request onto your desk or into a Zoom call.

54:45And now you're working together on that code base, But now your focus is on that task in synchronous mode, where the coding agent works asynchronously. And so this continuous spectrum of I can assign tasks, test generation, bug fixes, security vulnerabilities, bootstrapping a new feature to the coding agent, to I can take that code base into my local IDE, or I can keep working just as I'm used to all these things in parallel. That I think is going to be the future of software development. And then the skill of the developer will be to know how to describe the task in such a way that the agent can do the job with almost no additional revisions needed.

55:25Because every time you have to review code and correct the agent and wait another 10 minutes, you're interrupting your flow again. And you have to do something else in those 10 minutes. And jumping between different, you know, we're bad at multitasking and we're bad at context switching. and most developers do not want to work on 30 different things throughout the day. That's stressful and ultimately doesn't lead to great products. And the agent works with prompts, right? It's vibe coding where you describe what it is that you want it to do and it does it. Is that right? It's prompts when you use it within the IDE.

56:01Although even there, you can start with brainstorming a cycle first. And so that, for example, that works really great with Cloud Sonnet or Cloud Opus 4. And so you can first ask it, how would I build this? And what's the system design for this feature, for example? And then have it first write a markdown file with bullets doing the engineering together with the model. And then you take the first task of that and feed that into the agent mode to write the code. For the coding agent, because it sits on GitHub platform, the starting point is an issue. And the issue can be, the description that comes from a product manager or from a user of your open source project.

56:42But it's also all the comments in the issue, attached images, file references or web pages. And of course, the coding agent and agent mode both can use MCP servers and tools. And so you can then further connect into additional contacts. But yeah, fundamentally, it's a prompt. It's just that the prompt, it's no longer just one input field with three lines of code, it can be a long description, a specification from a product manager, just as they would write for the human developer. And again, the product manager then is the one that needs to learn of how much do I need to decompose the big problem into a small building block.

57:23And when you mentioned 30 % or 40 % success, is that across the board or from your experience using the product and early feedback from users, is the agent particularly good at certain tasks versus other tasks? If I'm a GitHub user and I want to play with product, what should I do first? The 30%, I was referencing the SWE benchmark that was developed by a number of researchers and originally started in Python only. It's 2000 issue pull request pairs out of a dozen Python open source repositories, but was recently expanded to other languages. And so in Python, I think the best benchmarks is 60 % to 70%, depending on what model agent combination you take.

58:12But if you look at multilingual, we are in the 20 % to 30 % range for these benchmarks. So that gives you an idea of real-life issues in open source projects and the corresponding pull requests. How good is the agent on solving that existing issue compared to the original solution? For our coding agent, the way to approach this for developers is to just go and try it out. Because worst case scenario is that you get a pull request that is so far off from what you would build yourself that you close the pull request without merging it. But then that gave you a learning cycle between the description that you gave it and the code it generated.

58:49And then, you know, there's multiple ways you can approach that if you don't want to throw it away. One is to provide custom instructions in a file within the repository to give the agent more context of what you expect it to do. So it's kind of like a how-to that you provide to the agent in the same way that if you would hire a developer into a team or you would instruct people in open source to contribute back to your project, you would also give them a, this is how we expect the coding standards, the libraries, how we're writing unit tests. So giving the agent more instructions often leads to better outcomes.

59:21Scoping it down to a smaller change often leads to better outcome and also to smaller pull requests, which is the best practice. And over time, the models will get better. We launched the coding agent on CloudSonic 3.7. And then three days later, Anthropic came with CloudSonic 4. And so now the coding agent is running on the 4 model. And of course, these models will get better. The context for the model will get better. The tools calls will be better. And so I think, you know, the key thing to always remember is whatever your experience was with AI a month ago is probably no longer the state of the art.

1:00:01Now, you shouldn't really form strong opinions or if you have strong opinions, you should have them loosely held and change your beliefs as AI technology is getting better. To close, it feels almost inevitable when having a conversation about AI coding in 2025 to not ask about what that means for the broader industry in the broader world. So two questions. What does that mean in terms of the future of SaaS? You know, in a world where anyone can spin up applications quickly, do we all build our own applications ultimately? And then another big mini question, which I'm not suggesting we go into it in great detail, but what does that mean in terms of the future of being a coder?

1:00:50What are the skills I need to develop or not care about in the future? The future of coders or software developers, software engineers is probably the best way of framing it is bright from my perspective. And software developers will learn very fast, if they haven't already, to adopt AI within their workflows, not only co-pilot and not only in the IDE or on GitHub, but also on the command line when processing files, when organizing files, all the things that we also do when operating clusters, all these things that we also do. And we have always, as software developers, automated parts of our workflow and moved higher up the abstraction ladder.

1:01:29You know, when I started coding on a Commodore 64, there wasn't a debugger. Everything was, you know, trial and error. You would print stuff onto the console to see what the variable content is. And then came, you know, Turbo Pascal and Visual Studio and so on. And our tools got more complex. And as such, we moved up and got more done in the same amount of time. And I think for developers, the same thing will happen again. It's, in fact, already happening. It happened with the cloud. It happened with containers like Docker and Kubernetes. Today, most developers on the web don't really care about the hardware anymore, certainly not about the chip itself, other than in models where you might know that you're running on an NVIDIA A100 or H200 or whatever the latest generation is when you're listening to this podcast.

1:02:20But for most cloud applications, what's actually below the application layer It doesn't matter to the developer as long as the service scales and is fast and snappy for the users. Which brings me to the SaaS question. And I think, you know, everything that I can easily replace with a single prompt is not going to have any value. It will have the value of that prompt and the inference and the tokens, but that's often a few dollars. And to manage the allowance of my kids, I'm probably not going to pay a$10 SaaS service. And I have a hard time seeing what additional value they can provide instead of just using, for example, GitHub Spark, which is our tool for these kind of scenarios, and build my own application.

1:03:01But at the same time, I think existing SaaS services will also increase their complexity. And so as the AI technology is not only used by you and I to bootstrap application, it's also used by those SaaS companies that are building software like GitHub itself. We're making our applications more complex and add value that hopefully still motivates customers to pay for the SaaS service. And whether it's for GitHub Copilot or for the fastest growing startup or the previous fastest growing startup, which I think was Viz, I think there's always going to be companies that use the latest technology to build products that you cannot easily replicate yourself.

1:03:46And as such, I'm not worried about that value chain goes away. I think we're underestimating how much you can do with the models that are out today. Not the ones that are coming next year or next month. The ones that we have today, where I think we're only touching the surface of what's possible with those leasing capabilities. And there's a whole new generation of products and agents that will offer scenarios that we're easily willing to pay a SaaS price or a mix of seed-based pricing and consumption-based pricing for. Thomas, what a fantastic conversation. Thank you so much for doing it. Thank you.

From the publisher

AI coding is in full-blown gold-rush mode, and GitHub sits at the epicenter. In this episode, GitHub CEO Thomas Dohmke tells Matt Turck how a $7.5 B acquisition in 2018 became a $2 B ARR rocket ship, and reveals how Copilot was born from a secret AI strategy years before anyone else saw the opportunity.


We dig into the dizzying pace of AI innovation: why developer tools are suddenly the fastest-growing startups in history, how GitHub’s multi-model approach (OpenAI, Anthropic Claude 4, Gemini 2.5, and even local LLMs) gives you more choice and speed, and why fine-tuning models might be overrated. Thomas explains how Copilot keeps you in the “magic flow state,” how even middle schoolers are using it to hack Minecraft.


The conversation then zooms out to the competitive battlefield: Cursor’s $10 B valuation, Mistral’s new code model, and a wave of AI-native IDE forks vying for developer mind-share. We discuss why 2025’s “coding agents” could soon handle 90 % of the world’s code, the survival of SaaS and why the future of coding is about managing agents, not just writing code.



GitHub

Website - https://github.com/

X/Twitter - https://x.com/github


Thomas Dohmke

LinkedIn - https://www.linkedin.com/in/ashtom

X/Twitter - https://twitter.com/ashtom


FIRSTMARK

Website - https://firstmark.com

X/Twitter - https://twitter.com/FirstMarkCap


Matt Turck (Managing Director)

LinkedIn - https://www.linkedin.com/in/turck/

X/Twitter - https://twitter.com/mattturck



(00:00) Intro

(01:50) Why AI Coding Is Ground Zero for Generative AI

(02:40) The $7.5B GitHub Acquisition: Microsoft’s Strategic Play

(06:21) GitHub’s Role in the Azure Cloud Ecosystem

(10:25) How GitHub Copilot Beat Everyone to Market

(16:09) Copilot & VS Code Explained for Non-Developers

(21:02) GitHub Models: Multi-Model Choice and What It Means

(25:31) The Reality of Fine-Tuning AI Models for Enterprise

(29:13) The Dizzying Pace and Political Economy of AI Coding Tools

(36:58) Competing and Partnering: Microsoft’s Unique AI Strategy

(41:29) Does Microsoft Limit Copilot’s AI-Native Potential?

(46:44) The Bull and Bear Case for AI-Native IDEs Like Cursor

(52:09) Agent Mode: The Next Step for AI-Powered Coding

(01:00:10) How AI Coding Will Change SaaS and Developer Skills

More from The MAD Podcast: How AI Gets Built — with Matt Turck

All episodes