Masala Chai: The Story Behind GitHub

Whenever you set out to create something — a startup, a product, or anything else — there's one thing you should never overlook: failure.

Sometimes, we learn from our own failures. But sometimes, the most valuable lessons come from the failures of others.

And what better way to understand those failures than by exploring the stories behind the ideas and startups people built? The decisions they made, the challenges they faced, the mistakes they learned from, and the moments that changed everything.

You don't need to wander through Wikipedia pages, biographies, or countless articles to discover these stories. We're bringing them together here, in a series called Masala Chai, where we explore stories worth understanding.

Our philosophy is simple: Stories start with a chai.

So, grab your cup of chai, because today we're diving into the story of one of our favourite platforms — GitHub. But before GitHub became the platform millions of developers use today, it was just an idea shared between a couple of developers.

Let's find out how that idea came to life.

Chapter 1: Werner Meets Wanstrath — The W & W

In October 2007, Tom Preston-Werner, one of GitHub's founders, met Chris Wanstrath, another future co-founder, at an I Can Has Ruby gathering in San Francisco.

At the time, Tom was working on a project called Grit, a Ruby library that allowed developers to access Git repositories through Ruby code.

When Tom met Chris, he showed him what he had been working on. But he didn't stop there. He also pitched an idea for a website that would act as a hub where developers could share their Git repositories.

Now, take a guess: which website were they talking about?

The answer is none other than our favourite GitHub!

Interestingly, the name GitHub had already been decided by Tom. Chris loved the idea and immediately agreed to join the project.

And just like that, what started as a casual conversation between two developers became the beginning of something much bigger.

An unexpected story, isn't it? Honestly, if someone from Bollywood ever reads this, there's already a movie waiting to be made!

Source: Tom Preston-Werner, How I Turned Down $300,000 from Microsoft to go Full-Time on GitHub, 18 October 2008.

Read the original article

Chapter 2: Three Months, Two Developers & One Big Idea

So, we left our two developers at a bar, with an idea that would eventually become one of the most important platforms in the developer community.

But having an idea and turning it into a product are two very different things. And Tom Preston-Werner and Chris Wanstrath were about to discover that.

The First Commit

Let's begin with a date that deserves a place in GitHub's history: 19 October 2007, at 10:24 PM.

That was when Chris Wanstrath made the first commit to the GitHub repository.

Now, if you're a developer, you already know what a commit means. But for everyone else, think of it as saving a particular stage of your work in a project's history.

And this wasn't just another commit. It marked the beginning of their joint venture.

Interestingly, they didn't have any formal agreements about how things would work. No complicated business arrangements, no big corporate plans. Just two developers who had decided to build something they thought was cool.

Three Months of Building

For the next three months, Tom and Chris spent countless hours planning and coding GitHub.

They divided the responsibilities according to their strengths.

Tom continued working on Grit and took care of the user interface design, while Chris focused on building the Ruby on Rails application.

But here's something interesting: GitHub wasn't their full-time job yet.

Tom was still working at Powerset as a tools developer. Both founders were managing their existing commitments while developing their new project.

They also made it a habit to meet every Saturday. These meetings weren't just about writing code. They discussed design decisions, planned features and even spent hours figuring out what their pricing strategy should look like.

Apparently, building a startup requires more than just being good at programming. Sometimes, you have to spend two hours discussing pricing over Vietnamese egg rolls!

From Private Beta to Public Launch

After approximately three months of development, GitHub entered its private beta phase in mid-January 2008.

They started sending invitations to their friends, allowing a small group of people to try the platform.

Then, in mid-February, another developer joined the journey: PJ Hyett.

And just like that, the two-person project became a team of three.

Finally, on 10 April 2008, GitHub was publicly launched.

Think about that for a moment.

Three developers in their twenties had built a platform, launched it publicly and were ready to take on the developer community.

And they had done all of this without a single penny of outside investment.

No huge development team, no venture capital funding and no massive corporate backing.

Just an idea, a few developers and months of hard work.

Chapter 3: The $300,000 Dilemma

On 1st July 2008, Microsoft acquired Powerset. At that time, Tom Preston-Werner was working at Powerset, and following the acquisition, Microsoft offered him a job.

Now comes the real Bollywood tadka!

The offer included a salary plus an additional $300,000 over three years, along with financial security and a stable career.

This offer feels like a Bollywood rich dad asking his daughter's lover to leave her in exchange for a huge amount of money (if you know, you know).

Now, what is Tom going to do? Let's see.

Chris Wanstrath and PJ Hyett were already working full-time on GitHub. And now came the dilemma: Tom had two choices — accept Microsoft's offer or commit himself entirely to GitHub.

It wasn't an easy decision. GitHub was still a new startup, and nobody knew what the future held. After all, business is all about risks and uncertainties.

But, as Harshad Mehta says in Scam 1992, "Risk hai toh ishq hai!"

Tom rejected Microsoft's offer and chose to work full-time on GitHub.

Chapter 4: The Business Behind GitHub

Building a product is one thing, but turning it into a business is a completely different challenge.

Tom and Chris knew that GitHub couldn't run forever just because developers loved using it. They needed a business model that could keep the platform running and help it grow.

During the early planning days, the founders spent hours discussing pricing. They had to figure out how to make money without pushing developers away.

After all, charging developers for every public project wouldn't exactly make GitHub popular, while giving everything away for free wouldn't make it a sustainable business either.

Eventually, GitHub moved towards a model where developers could host public open-source projects for free, while private repositories became a paid feature.

In simple words, developers could share their code with the world without paying, but if they wanted to keep their projects private, they had to pay.

It was a clever balance between attracting users and generating revenue.

Of course, getting the pricing right wasn't easy. The founders had to reconsider some of their early pricing decisions based on user feedback.

And that's an important lesson in business: sometimes, your customers understand what they need better than you do.

Chapter 5: GitHub SWOT Analysis (2008)

Now that we've explored GitHub's early business journey, let's look at it from a business perspective.

For this, we'll use a business analysis tool called SWOT Analysis.

SWOT stands for Strengths, Weaknesses, Opportunities and Threats. It helps us understand a company's internal advantages and limitations, along with the external opportunities and challenges it faces.

Let's apply it to GitHub around 2008.

1. Strengths

These are the internal advantages that helped GitHub stand out.

  • Developer-focused platform: GitHub was built specifically around the needs of developers.
  • Git integration: It made sharing and collaborating on Git repositories easier.
  • Technical expertise: Its founders had the technical knowledge to build and improve the platform.
  • Community-driven approach: Developers could share their work and collaborate on projects.

2. Weaknesses

Even a promising startup has its limitations. GitHub was no exception.

  • Small founding team: A small team meant limited manpower for development and operations.
  • Limited resources: The company had to manage its resources carefully.
  • Early business model: The founders were still figuring out the right pricing strategy.
  • Growing user base: GitHub still needed to establish itself among developers.

3. Opportunities

These are external possibilities GitHub could take advantage of.

  • Growing adoption of Git: As more developers started using Git, demand for Git-based hosting and collaboration could increase.
  • Global developer community: The internet allowed developers from different countries to work together.
  • Growth of open source: More open-source projects meant more potential users.
  • Paid services: Private repositories and team-oriented features offered opportunities to generate revenue.

4. Threats

These are external challenges that could affect GitHub's growth.

  • Existing competitors: Platforms such as SourceForge and Google Code were already involved in code hosting.
  • Larger technology companies: Established companies had greater resources and infrastructure.
  • Technical challenges: As the platform grew, maintaining performance, reliability and security would become increasingly important.
  • Changing technology: GitHub needed to keep improving as developer tools and requirements evolved.

Looking at this analysis, we can understand that GitHub had a promising idea and a clear audience, but it also faced several challenges.

And just like a Bollywood hero, having strengths doesn't mean the villains disappear!

Note: This is our own SWOT analysis of GitHub's position around 2008, not an official report published by the company.

Chapter 6: Lessons from GitHub

So, what can we learn from GitHub's early journey?

There are a few interesting lessons worth taking away.

1. Great ideas can start with simple conversations.

GitHub didn't begin with a huge office, a massive team or a complicated business plan. It started with a conversation between two developers who wanted to build something useful.

2. Build something that solves a real problem.

Tom and Chris understood the difficulties developers faced while working with Git. Instead of simply creating another website, they worked on making collaboration easier.

3. The right team matters.

Different skills and perspectives can make a huge difference. Tom and Chris brought different strengths to the project, and PJ later joined them.

4. Listen to your users.

Their early pricing decisions showed that businesses don't always get everything right on the first attempt. Feedback can help improve a product and its business model.

5. Entrepreneurship involves uncertainty.

Tom's Microsoft offer is a reminder that entrepreneurship involves difficult decisions. There is no guarantee that choosing a startup over a stable job will work out. But founders sometimes decide that the opportunity to build something of their own is worth taking the risk.

The Last Sip

And that's how GitHub's journey began.

From a conversation at a Ruby meetup to a platform built around developers, GitHub's early story shows us how a simple idea can grow when people are willing to work on it.

It wasn't a journey without uncertainty. There were business decisions to make, pricing strategies to reconsider and risks to take.

But perhaps that's what makes startup stories worth exploring. We don't just learn about the companies that succeeded; we also understand the decisions, challenges and experiments that shaped their journeys.

After all, every successful product has a story behind it.

And sometimes, all it takes to discover one is a cup of chai.

Stories start with a chai.