DEV Community

Cover image for From Curiosity to Code: My Accidental Journey Into GitHub
Karthik Korrayi
Karthik Korrayi

Posted on

From Curiosity to Code: My Accidental Journey Into GitHub

It was sometime in 2021. I was casually scrolling the web, not even looking for anything serious—just hopping from one click to another. That’s when I stumbled upon something intriguing. A link ended with:

github.io/portfolio/

I clicked.

And there it was—

A beautiful, clean, and sharp digital profile of someone. Almost like a resume, but better. Interactive, well-organized, and somehow... professional.

“Wait—this is a website? Like a full-blown one, and the person made it for themselves?”

That moment was like a switch.

My student mind, hungry for learning and exposure, lit up with questions.

What is github.io? Why is it not .com?

And more importantly—how did they even build this?


💡 GitHub: More Than Just a Website

My curiosity led me to research. Soon, I discovered that GitHub is not just a website hosting platform. It's a kind of OneDrive or Google Drive, but for developers. But the more I read, the more I realized—it was even deeper than that.

GitHub isn’t just about storing files.

It's about versioning, collaboration, code sharing, and project tracking.

But GitHub is just the stage.

The real actor? That was Git.


🔁 Enter Git: The Time Machine of Code

Every hero has an origin story.

So does Git.

Back in 2005, the Linux kernel development team was struggling. They were using a proprietary tool called BitKeeper to manage their codebase. Things broke down when the license agreement fell through. So, Linus Torvalds—the creator of Linux—did what only a legend would do:

He built his own version control system.

Thus, Git was born—

Fast, distributed, free, open-source, and secure.

It allowed developers to track every change, branch out into experiments, and merge back safely.


🌍 The Rise of GitHub

Even though Git was powerful, it was hard to use. Terminal commands scared many.

Enter 2007–2008.

Tom Preston-Werner, Chris Wanstrath, and PJ Hyett asked:

“What if we made Git simpler, and brought collaboration online?”

They built GitHub—a social coding platform. It gave Git a friendly face, plus features like:

  • Pull Requests
  • Issues and bug tracking
  • Team discussions
  • Code reviews

Now, developers didn’t have to email zipped code (yes, that was a thing!).

No more sending patches over Gmail.

Everything was centralized, trackable, and beautiful.

So yes—you're not wrong if you heard GitHub solved the "Gmail struggle." It didn’t happen because of Gmail, but it definitely helped end the days of chaotic code emails.


🔄 Fast Forward to Today (2021–2025)

From the day I discovered that portfolio, I’ve seen GitHub evolve rapidly:

🔧 Today's Cool GitHub Trends & Tools:

  • GitHub Actions: Automate deployments, tests, or anything with workflows.
  • Codespaces: Full cloud dev environments. No need to install VS Code locally!
  • Copilot: AI-powered coding assistant that completes your code while you type.
  • GitHub Pages: Free static website hosting for portfolios, docs, or blogs.
  • Discussions: Great for community engagement in open-source projects.

🔒 Private Repos & Other Git Collab Platforms

As I explored more, I found that Git is the technology, and GitHub is just one platform. There are others too:

  • GitLab – Powerful CI/CD integration
  • Bitbucket – Often used by enterprises and teams with Jira
  • Azure DevOps Repos – For Microsoft and enterprise stack teams

These also support private repositories, where:

  • You can collaborate in secret
  • Share only with teammates
  • Protect sensitive or early-stage code
  • Work on personal projects without showing them to the public world

It’s like a shared diary for coders—except with better branching and no spelling mistakes (hopefully).


📚 What I Learned From That Click

  • Git is like a time machine for your project.
  • GitHub is the home where your code lives, grows, and shines.
  • Learning GitHub opens the door to contributing, collaborating, and coding like a pro.

😂 Before You Go…

If Git tracks every change you make,

and you accidentally commit your heartbreak story into a repo,

...

Will Git blame your ex or you? 🤔

Let me know once you figure it out.

Because I still can’t decide whether to git revert
or just git commit -m "It is what it is".


Top comments (0)