Key Takeaways

  • GitHub now hosts over 200 million "developers," a massive leap from 80 million, signifying an expanded creator base that grew 14x over a prior period.
  • GitHub CEO Kyle Daigle passionately rejects gatekeeping the term "developer," asserting that anyone using the platform to create code or bring an idea to life is a developer, regardless of formal training.
  • This anti-gatekeeping stance is seen as vital for GitHub's explosive growth and for fostering an inclusive community, especially as AI tools enable new cohorts to build.
  • Daigle views AI-assisted creation not as cheating, but as a new entry point, making building accessible “just like I can go change a light switch in my house.”

The 200 Million Developer Reset: Why Gatekeeping Dies with AI

When Swyx, host of Latent Space, casually asked Kyle Daigle for GitHub's latest user count, he expected something in the realm of 80 million. Daigle, CEO of GitHub, corrected him: “we're over 200 million now.” That’s a 14x growth over an unspecified previous period, and a stunning 2.5x jump from Swyx’s last memory. What does it mean for "developer" to scale that high? It means the definition itself has cracked open.

Daigle admits this is “the biggest debate that like everyone loves to have at GitHub at this point.” But his position is clear and unyielding: “the idea that . . . we should be like . . . splitting hairs or segmenting developers in the early era of software development is like not worth our not worth the time.” For ambitious founders, this isn't just a philosophical stance; it's a strategic directive. If you're still building for the "professional enterprise developer" of five years ago, you're missing the largest, fastest-growing cohort.

Your Next Million Users Aren't 'Coders' — They're Builders

The traditional "developer" image — computer science degree, deep understanding of algorithms, pure lines of human-written code — is quickly becoming obsolete as the only definition. Daigle pushes hard against this, saying, "You get into gatekeeping like 100% because I mean I wasn't a developer when I started writing code." He understands the impulse, but he rejects it.

His operating principle for GitHub is simple: “I fight very clearly on the line of like if you create code, if you have an idea and you create it into some way of like I'm going to run it and use the app right now.” The kicker? “You may still use AI in that moment. But that's okay.” GitHub’s unprecedented growth to 200 million isn't despite AI, it's because of it. AI isn't just making existing developers faster; it's minting millions of new ones. These new builders might use Copilot to scaffold entire applications, or just tweak a script for a personal project. To Daigle, they're all developers. “Anyone should be able to go and build a thing just like I can go change a light switch in my house.” This means your next user might be a marketer automating a report, a scientist scripting data analysis, or a hobbyist building a smart home dashboard — all using AI to bridge skill gaps.

What to Do With This

Stop building your product or community exclusively for a narrow, idealized definition of "the developer." Pull up your last three customer interviews. Did you unintentionally filter out the "new builders" — the marketers, designers, or citizen developers now enabled by AI? This week, challenge your product team to define a user persona for someone who only uses AI to write code, but still needs your tool to ship. Design for them. Broaden your community onboarding to welcome contributions from non-traditional backgrounds, explicitly encouraging AI-assisted projects. The 200-million strong future of software development belongs to the anti-gatekeepers.