The myth-busts, hot takes, explainers, and tools worth keeping.
◆Hot Take· 2
◆Hot Take58:30
Microsoft Bought GitHub's Developer Ecosystem, Not Just Its Revenue
The hosts argue that GitHub's strategic position among developers mattered more than its relatively modest and likely unprofitable revenue. As Windows lost some of its power to compel developer participation, GitHub offered Microsoft a durable relationship with the people building modern software.
The reported price implied a very high revenue multiple
GitHub possessed a sticky customer base and strong network effects
Windows no longer provided the same ecosystem leverage
The acquisition restored Microsoft's proximity to developers
“they bought it for the strategic place that GitHub has in the developer ecosystem.”
“I think they bought a customer base and they bought that customer base for years to come.”
#microsoft#github#strategy#developers
◆Hot Take1:19:30
GitHub Could Fill LinkedIn's Biggest Recruiting Data Gap
Because public GitHub activity serves as a developer résumé, the acquisition could complement Microsoft's ownership of LinkedIn. The hosts note that engineers are exceptionally expensive to recruit while LinkedIn contains comparatively little evidence about their actual technical work.
GitHub profiles reveal public projects and accepted contributions
Engineering recruitment can cost tens of thousands of dollars per hire
LinkedIn has limited data about code quality and technical impact
Combining the strategic assets could create recruiting value
“GitHub is the main, you know, resume for software developers now.”
“there's the least data on LinkedIn about the most valuable position to recruit.”
#github#linkedin#recruiting#developers
✶Explainer· 4
✶Explainer06:30
Why Distributed Version Control Replaced the Central Server
The hosts explain how centralized source control became restrictive once software development spread across the internet. Distributed systems made cloning, experimenting, and contributing across locations substantially easier, especially for open-source projects.
Central repositories created one canonical code base
Side experiments and long-lived forks were cumbersome
Internet-era development required geographically distributed collaboration
BitKeeper helped demonstrate the distributed model
“It's really hard once more than one person starts working on the project to kind of manage all the changes and contributions”
“once the internet comes around and distributed software development becomes more of a thing, especially in the open source community, this becomes a lot harder.”
#git#version-control#open-source
✶Explainer14:00
GitHub Turned a Code Forge Into a Social Network
Earlier forges such as SourceForge and Google Code hosted files but offered little meaningful social interaction around development. GitHub fused code, project activity, discussion, and developer identity into one community-oriented interface.
Traditional forges primarily hosted code
Project discussion was split across mailing lists and forums
Consumer social networks demonstrated the power of connected communities
GitHub brought collaboration and code into one place
“there's not much more to them beyond a place to live and like a like very standard Wikipedia style webpage about the projects.”
“what if there's more of a community type site instead of these forges where developers can interact?”
#github#social-coding#developer-tools
✶Explainer1:04:30
GitHub's Strategic Value Came From Being Switzerland
GitHub worked horizontally across languages, clouds, companies, and platforms. The hosts consider whether an acquirer might compromise that neutrality by steering developers toward its own infrastructure, particularly Azure or Google Cloud.
GitHub's neutrality supported broad adoption
Google would have faced pressure to promote its own platforms
Microsoft could create easier Azure deployment paths
Heavy-handed integration could weaken community trust
“the great thing about GitHub is that it's Switzerland.”
“I think they will use it to leverage people onto Azure.”
#github#cloud#azure#platform-strategy
✶Explainer1:07:30
Why GitHub's All-Stock Sale Was So Unusual
Microsoft could easily have paid cash but instead financed the $7.5 billion acquisition entirely with shares while conducting a buyback program. The structure also left each GitHub co-founder holding more Microsoft stock than CEO Satya Nadella, reflecting their limited dilution before the sale.
Microsoft had substantial net cash
Issuing acquisition shares appeared inconsistent with buying back stock
The structure prompted speculation about valuation and future cash needs
Bootstrapping and late funding preserved founder ownership
“Very interesting that this was an all stock acquisition.”
“Each of the GitHub co-founders now owns more of Microsoft than Satyan Adela.”
#microsoft#github#m&a#finance
❝Story· 7
❝Story10:30
The License Withdrawal That Led Linus Torvalds to Build Git
Linux development relied on a free BitKeeper license until the company withdrew it in 2005. The resulting open-source crisis produced Mercurial and Git, with Linus Torvalds implementing Git remarkably quickly before handing off its continued development.
BitKeeper supported distributed Linux development
The free license was withdrawn in 2005
Mercurial and Git emerged as replacements
Git became Linux's source-control system and spread rapidly
“this creates a huge kerfuffle in the open source community”
“Git is interesting because it is actually developed and implemented in like a week”
#git#linux#bitkeeper#linus-torvalds
❝Story19:00
The Sports-Bar Conversation That Started GitHub
Tom Preston-Werner encountered Chris Wanstrath during a San Francisco Ruby meetup and showed him an early repository-access project called Grit. Wanstrath immediately agreed to collaborate, and the pair began building the product during nights and weekends.
The founders were Bay Area Ruby developers
Preston-Werner had already started building Grit
The product idea centered on social coding
Development began alongside their full-time jobs
“I'm in, let's do this.”
“So they start working on it on nights and weekends.”
#github#founding#startups#ruby
❝Story23:30
GitHub's Launch Found Immediate Product-Market Fit
The founders first used the interface inside their own startup, giving them direct product feedback. After opening GitHub to friends in January 2008, adoption accelerated so quickly that hosting costs became an urgent business concern.
The founders acted as their own first customers
Internal adoption validated the product's usefulness
The public launch spread rapidly among Git users
Infrastructure costs forced an early monetization decision
“the whole be your own first customer thing.”
“as soon as you you turn the lights on, there's perfect product market fit.”
#github#product-market-fit#startups
❝Story34:00
GitHub Bought the Octocat as Cheap Stock Art
Inspired by Twitter's stock-art bird, GitHub's founders searched designer Simon Oxley's catalog for their own logo. They selected a cat-octopus hybrid, renamed it the Octocat, and turned an inexpensive image into a globally recognized mascot.
Twitter's original bird also came from stock art
The selected creature originally had only five tentacles
GitHub reportedly paid about three dollars
The Octocat became both logo and community mascot
“Oh, how about an unholy marriage of a cat and an octopus?”
“so they buy the octopus, rename it the Octocat”
#github#octocat#branding
❝Story33:30
GitHub Bootstrapped Before Raising a Record $100 Million Series A
GitHub remained bootstrapped and profitable during its early expansion, using a formula to adjust founder salaries as revenue grew. By 2012 it had roughly 100 employees before Andreessen Horowitz invested $100 million at a $750 million valuation.
The founders initially avoided venture capital
Revenue funded early operations and hiring
The first institutional round arrived years after launch
The round was described as the largest Series A to that point
“they decide that they're gonna bootstrap and they're making enough money they don't need to raise venture capital.”
“the largest quote unquote series A ever raised in history.”
#github#venture-capital#bootstrapping
❝Story42:30
GitHub's Flat Culture Collided With Rapid Growth
A harassment controversy and internal investigation culminated in co-founder Tom Preston-Werner leaving GitHub in 2014. The hosts connect the crisis cautiously to a young founding team, rapid growth, and an unusually flat organization where employees could choose their own work.
Preston-Werner and his wife faced accusations
An internal investigation found lapses in judgment
GitHub used a Valve-inspired flat management style
Chris Wanstrath became CEO after Preston-Werner left
“they adopted the Valve management uh style of a completely flat organization, nobody reported to anyone else.”
“anyone could work on whatever they wanted.”
#github#culture#leadership
❝Story51:30
Microsoft Went From Policing GitHub to Buying It
Gilbert recalls being warned about open-source licenses and even reprimanded for opening GitHub during a Microsoft internship. In the following years, Microsoft embraced Linux, added Git support to its developer products, and ultimately purchased the platform it had once viewed with suspicion.
Microsoft historically treated some open-source code as a legal risk
GPL obligations worried the Windows and Office organization
Microsoft gradually adopted open-source technology
The GitHub purchase symbolized a major philosophical reversal
“I got in trouble with Microsoft for having GitHub open.”
“It's just such a funny testament to how much the world has changed now that that's not Microsoft, and now Microsoft is buying GitHub.”
#microsoft#open-source#github#gpl
▲Takeaway· 1
▲Takeaway1:23:00
The Hosts Grade Microsoft's GitHub Acquisition C and B
Gilbert assigns a C because Microsoft paid heavily for a money-losing asset whose strategic integration remained uncertain. Rosenthal gives it a B, expecting a respectable but unspectacular middle outcome under Microsoft's improved leadership.
The purchase price was difficult to justify from revenue alone
The strategic case produced a wide range of possible outcomes
Gilbert chose a high-variance C
Rosenthal predicted a muddy-middle B
“It's super high variance, but I'm gonna go C.”
“I think it probably ends up somewhere in the muddy middle. I'm gonna give it a B.”