The present, past and future of GitHub
· Summarized
Key takeaways
- GitHub has transformed from a simple platform into a diverse technological powerhouse focused on enhancing developer workflows.
- The remote-first culture at GitHub promotes productivity and allows for flexible work arrangements worldwide.
- AI tools like Copilot serve as assistants to developers, helping them write code faster and more efficiently.
- Security is a critical focus for GitHub, especially post-acquisition by Microsoft, with significant investments in safety measures.
- Hiring junior engineers is a strategic move for GitHub, providing fresh ideas and perspectives that enhance innovation.
- The future of software engineering will involve collaboration between AI tools and human developers, enhancing productivity without replacing the human element.
Summary
The Evolution of GitHub
The podcast opens with a historical overview of GitHub, including its inception in 2008 and how it has transformed over the years. Thomas Dohmke, CEO of GitHub, discusses the company's journey from a Ruby on Rails monolith to a more diverse technology stack. He details how GitHub's internal culture and tools have evolved, focusing on asynchronous communication and the embrace of open-source principles.
GitHub's Remote-First Culture
Dohmke highlights GitHub's remote-first and async-first engineering culture. The company rarely uses email, favoring platforms like Slack to enhance productivity. GitHub's approach enables flexibility for employees worldwide, fostering a diverse and inclusive work environment. Collaborative tools allow teams to work on the same platform, enhancing productivity and communication.
The Role of AI: Copilot and Beyond
The discussion turns towards the introduction of GitHub Copilot, an AI tool that assists developers by generating code snippets. Dohmke emphasizes the importance of AI as a tool rather than a replacement for engineers. He discusses how Copilot has reshaped software development workflows and the positive reception it has received since its launch.
Security and Innovation Post-Acquisition
Dohmke talks about GitHub's approach to security and how it has matured since being acquired by Microsoft. The company has significantly invested in security measures while continuing to innovate. He touches on GitHub's backend architecture and how it operates under Microsoft’s cloud services, ensuring data security and compliance with regulations.
Hiring Junior Engineers: Building the Future
An interesting segment discusses GitHub's strategy of hiring junior engineers. Dohmke believes that fresh talent brings innovative ideas and new perspectives that benefit the company. Emphasizing the significance of mentorship, he insists that junior engineers can thrive and contribute valuable insights amidst advanced technologies like AI.
Navigating the Future
The episode concludes with thoughts on the future of GitHub amidst the evolving landscape of software engineering. Dohmke expresses optimism about the integration of AI agents and their potential to assist rather than replace human developers. He urges engineers to adapt and embrace these changes, reinforcing the notion that hands-on coding will remain a critical skill.
Sponsors
- Statsig · The unified platform for flags, analytics, experiments, and more.
- Graphite · The AI developer productivity platform.
- Augment Code · AI coding assistant that pro engineering teams love.
Show notes
Supported by Our Partners
• Statsig — The unified platform for flags, analytics, experiments, and more.
• Graphite — The AI developer productivity platform.
• Augment Code — AI coding assistant that pro engineering teams love
—
GitHub recently turned 17 years old—but how did it start, how has it evolved, and what does the future look like as AI reshapes developer workflows?
In this episode of The Pragmatic Engineer, I’m joined by Thomas Dohmke, CEO of GitHub. Thomas has been a GitHub user for 16 years and an employee for 7. We talk about GitHub’s early architecture, its remote-first operating model, and how the company is navigating AI—from Copilot to agents. We also discuss why GitHub hires junior engineers, how the company handled product-market fit early on, and why being a beloved tool can make shipping harder at times.
Other topics we discuss include:
• How GitHub’s architecture evolved beyond its original Rails monolith
• How GitHub runs as a remote-first company—and why they rarely use email
• GitHub’s rigorous approach to security
• Why GitHub hires junior engineers
• GitHub’s acquisition by Microsoft
• The launch of Copilot and how it’s reshaping software development
• Why GitHub sees AI agents as tools, not a replacement for engineers
• And much more!
—
Timestamps
(00:00) Intro
(02:25) GitHub’s modern tech stack
(08:11) From cloud-first to hybrid: How GitHub handles infrastructure
(13:08) How GitHub’s remote-first culture shapes its operations
(18:00) Former and current internal tools including Haystack
(21:12) GitHub’s approach to security
(24:30) The current size of GitHub, including security and engineering teams
(25:03) GitHub’s intern program, and why they are hiring junior engineers
(28:27) Why AI isn’t a replacement for junior engineers
(34:40) A mini-history of GitHub
(39:10) Why GitHub hit product market fit so quickly
(43:44) The invention of pull requests
(44:50) How GitHub enables offline work
(46:21) How monetization has changed at GitHub since the acquisition
(48:00) 2014 desktop application releases
(52:10) The Microsoft acquisition
(1:01:57) Behind the scenes of GitHub’s quiet period
(1:06:42) The release of Copilot and its impact
(1:14:14) Why GitHub decided to open-source Copilot extensions
(1:20:01) AI agents and the myth of disappearing engineering jobs
(1:26:36) Closing
—
The Pragmatic Engineer deepdives relevant for this episode:
• AI Engineering in the real world
• How Linux is built with Greg Kroah-Hartman
• Stacked Diffs (and why you should know about them)
• 50 Years of Microsoft and developer tools
—
See the transcript and other references from the episode at https://newsletter.pragmaticengineer.com/podcast
—
Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com.
Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe
Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account