AI summary by TwinMind
Why Microsoft paid $7.5 billion for GitHub (Nat Friedman)
Dwarkesh Patel
8m 12s
Background and Initial Proposal
- Nat Friedman co-founded Xamarin with Miguel de Icaza and Joseph Hill (mobile tools/platforms)
- Microsoft acquired Xamarin in 2016
- Friedman initially planned to stay only ~1 year at Microsoft
- First week at Microsoft (March/April 2016): Friedman suggested to Satya Nadella that Microsoft should buy GitHub
- Nadella's response: "Good idea, we thought about it, not sure we can get away with it"
The Acquisition Memo and Decision
- ~1 year later: Friedman wrote memo to Satya about GitHub acquisition
- Catalyst: rumors Google was interested in GitHub (possibly manufactured by GitHub team)
- Key argument: Developer purchasing power shift
- Previously IT-driven purchasing decisions
- Now developers leading purchase decisions
- Microsoft was IT company, not developer company (despite being founded as developer company)
- Microsoft's first product was programming language
- Core thesis: New generation developers have no Microsoft affinity, largest collection on GitHub
- Strategy: "If we acquire this and do merely competent job running it, we can earn right to be considered by these developers for all other products"
- Satya replied in 6-7 minutes: "Very good thinking, let's meet next week"
Executive Meeting and Deal Structure
- Conference room meeting: Satya, Amy Hood, Scott Guthrie, Kevin Scott, others
- Friedman gave 20-minute presentation
- Satya's decision: "I think we should do it"
- Proposed structure: Run independently like LinkedIn, Friedman as CEO
- Initial price discussion: $2 billion target
- Timeline: 3 weeks from decision to signed term sheet and announced deal
Managing Developer Skepticism
- Deal leaked Friday before planned Monday announcement
- Weekend: negative posts online, "evacuate GitHub" sentiment
- Monday announcement: GitHub to run as independent company with Friedman as CEO
- Friedman's open source background helped calm some concerns
- Some developers decided to wait and see before migrating
First Day Strategy: 100-Day Shipping Initiative
- First day as CEO: 9 AM meeting with engineering/product heads
- GitHub had no official public feedback mechanism
- Community member Isaac (from npm) had created unofficial GitHub feedback repos
- Friedman's strategy: Fix one item from community feedback list by end of day
- Team initially skeptical about timeline (database migrations, etc.)
- Found implementable item, shipped same day
- Philosophy: Show GitHub cares about developers, not Microsoft
- Example: Adding Skype integration first would signal wrong priorities
- Committed to shipping something every day for 100 days
Benefits of Daily Shipping Approach
- Positive feedback loops:
- Developers seeing long-requested fixes implemented
- Team excitement from frequent shipping
- Broke GitHub's previous "stage fright" about shipping
- Learning benefits for Friedman:
- Exposure to team capabilities
- Understanding code quality/tech debt
- Quick assessment of design processes
- Faster company knowledge acquisition vs. 6-month projects
- Trust-building with developer community
