Let me start with a confession: until about two years ago, I thought GitHub was just a storage locker for code. Like, literally a place where programmers dumped their files and moved on. I'd see it mentioned in job postings, in open-source communities, in every tech conversation I half-listened to at Mumbai coffee shops between market analysis calls. But I never really understood why developers got so passionate about it.
Then I started learning to code on the side—nothing serious, just Python scripts to automate some Excel work—and suddenly it clicked. Not just what GitHub is, but why it matters. And not just for software engineers. For anyone who writes anything, builds anything, or wants to track how their ideas evolve.
So this letter is for you. The version of me from two years ago. Or maybe for your younger brother, cousin, or that friend from college who keeps saying "I want to learn coding but where do I even start?" This is what I wish someone had explained to me clearly, without the jargon, without the assumed knowledge.
What GitHub Actually Is (and It's Not Just "Cloud Storage")
Here's the thing: GitHub is a platform built on top of something called Git, which is version control software. But let me translate that into something that makes sense.
Remember when you were working on a school project with classmates, and you had 47 versions of the same file? "Project_Final.docx", "Project_Final_v2.docx", "Project_Final_ACTUAL.docx", "Project_Final_Please_This_One.docx". Nightmarish, right?
Git solves that problem. It's like having a time machine for your code—or any files, really. Every time you make changes and save them (called a "commit"), Git creates a snapshot. You can go back to any snapshot anytime. You can see exactly what changed, who changed it, and why. You can have multiple people working on the same project without overwriting each other's work.
And GitHub? It's just the platform that makes Git easy to use, gives it a nice interface, and puts it on the internet so teams can collaborate.
The Three Core Things GitHub Does
1. Version Control: Tracks every change. Imagine if Excel showed you a complete history of every formula you ever typed, every cell you modified, and let you revert to any moment in time. That's what Git does for code.
2. Collaboration: Multiple people can work on the same project simultaneously. There's a system (branches) that prevents conflicts. When you're ready to merge changes, GitHub helps manage that without anyone's work getting lost.
3. Documentation & Discovery: Your code lives on GitHub with a README file explaining what the project does. Other developers can find your work, learn from it, use it, or contribute to it. It's like a portfolio and a library combined.
GitHub vs. Just Saving Files to Google Drive
I used to think: "Why not just use Google Drive or Dropbox?" And honestly, for a single Excel file, you probably don't need GitHub. But for code projects, here's why they're completely different beasts:
Google Drive is linear. You upload v1, then v2, then v3. But if you and I are both editing the same code simultaneously, chaos happens. With GitHub, we work on separate branches of the same project, then carefully merge them back together. The system prevents conflicts instead of creating them.
Also—and this matters in tech careers—GitHub is visible to the world. Recruiters check GitHub. Companies look at your commit history (how frequently you work), your code quality, and your contributions to open-source projects. Having a strong GitHub presence is like having a live portfolio of your work. Google Drive backups of your personal spreadsheets? That doesn't go on a resume.
Why Developers Are Obsessed With It
Spend an hour in a developer community—a Discord server, a Reddit thread about programming, a GitHub discussion—and you'll notice something: developers care deeply about their GitHub activity. And it's not vanity. There are real reasons.
Reason 1: It Solves Real Daily Problems
Let's say I write a Python script on Monday morning for work. Tuesday afternoon, I break something while adding a new feature. With GitHub, I can see the exact lines I changed and revert them in seconds. Without it? I'm scrolling through 200 lines of code trying to remember what I touched.
Or imagine you're working in a team of five analysts at Morningstar (yes, like me). You're all building different components of a financial model. With GitHub, your changes are tracked separately. Your manager can review exactly what you did before it gets merged into the main project. Without it, you email Excel files around and pray no one overwrites anyone else's formulas.
Reason 2: It's the Standard in Tech Careers
Every software job posting I've ever seen mentions GitHub. Not as a nice-to-have. As a requirement. "Must be proficient with Git and GitHub." When you interview at tech companies—even in India, even at companies like Flipkart, Amazon, or Indian startups—one of the first things they ask is: "Show us your GitHub." Your GitHub is your coding résumé.
Having projects on GitHub, contributing to open-source, maintaining a consistent commit history—these things matter for your career trajectory in ways that Google Drive backups simply don't.
Reason 3: Open Source Magic
This one surprised me. GitHub is where the entire open-source ecosystem lives. Millions of free libraries, frameworks, and tools exist because developers share their work on GitHub.
You're a developer who built a tool that makes your life easier? Upload it to GitHub, open-source it, and suddenly thousands of people worldwide might use it, improve it, and contribute back. Some of the most important software in the world—Linux, Python packages, React—all live on GitHub and rely on community contributions.
This creates a culture of sharing and collaboration that's genuinely powerful. It's also how junior developers learn. You can read professional code, see how experienced developers solve problems, and learn without anyone gatekeeping knowledge behind a paywall.
How to Actually Start Using GitHub (Without Overthinking It)
This is where I see people freeze up. They think they need to understand everything before touching it. You don't. I'm still learning GitHub features I didn't know existed.
Step 1: Create an Account and Understand the Vocabulary
Go to github.com and sign up. Use your real name or a professional variation. This might be on your resume someday, so don't pick "CodingNinja420" unless you actually want that representing you to recruiters.
Now, the basic vocabulary: A Repository (or "repo") is just a project folder. Think of it like a Dropbox folder, but with version control. A Commit is a snapshot of your changes at a point in time. A Branch is a separate line of development. You can have a "main" branch (the stable version) and a "feature/new-login" branch where you work on a new feature without breaking the main code.
A Pull Request is a proposal to merge changes. You're saying "Hey, I made these changes on my branch, please review them and merge them into main if they look good." This is where code reviews happen.
That's 80% of what you need to know to start. Seriously.
Step 2: Start Small—Create Your First Repository
Create a new repository. Call it "Learning" or "Experiments" or something personal. Upload a simple Python script, or a text file with notes, or whatever. The goal isn't to build something grand. It's to get comfortable with the workflow.
On your computer, you'll use command-line Git commands:
git clone (download the repo)
git add (prepare changes)
git commit -m "message" (save a snapshot)
git push (upload to GitHub)
Do these five times and they'll stop feeling scary. I promise.
Step 3: Explore Other People's Repos (Don't Just Upload)
This is where the real learning happens. Find a project you're interested in—a Python library you use, an open-source tool, whatever. Read the README. Look at the code. Check the Issues tab (where people report bugs or request features). Look at the Pull Requests to see how contributions are discussed and merged.
You'll learn more by reading professional code on GitHub than you will from most tutorials.
| GitHub Feature | What It Does | When You Use It |
|---|---|---|
| Repository | Container for your project files and history | Every time you start a new project |
| Commit | Snapshot of changes at a specific time | After completing a small task or feature |
| Branch | Separate line of development | When working on features without breaking main code |
| Pull Request | Proposal to merge changes into main branch | When your feature is ready for review and merge |
| Fork | Copy someone else's repo to your account | When contributing to open-source projects |
| Issues | Tracking bugs, feature requests, discussions | When reporting problems or planning improvements |
GitHub Beyond Code (Yes, Really)
Here's something I didn't expect: GitHub isn't just for programmers anymore.
Data analysts use it. Writers use it. People managing research projects use it. Why? Because version control and collaboration are useful for anything that evolves over time.
For Data Work
At Morningstar, we work with datasets and scripts. Using GitHub for our Python analysis scripts means we can track changes, collaborate with other analysts, and maintain a history of how our models evolved. If a calculation is off, we can trace back to exactly when it changed and why.
For Writing and Documentation
Writers and technical documenters use GitHub too. You can track drafts, get feedback through pull requests, and see exactly what changed between versions. Some writers version-control their entire books on GitHub.
Even this blog post? I could put it on GitHub, let editors suggest changes, and track every revision.
My Perspective
I studied Economics, not Computer Science. Most of what I understand about systems and collaboration comes from analyzing how markets work, how information flows, how incentives align people toward shared goals. And honestly? GitHub is a beautiful example of systems design working well.
In Economics, we talk about information asymmetry—when one party has more information than another, markets fail. GitHub solves that. All code is visible, all changes are tracked, all contributions are recorded. There's no hidden agenda because the entire history is transparent.
What surprised me most? That the barrier to entry is so low, but the depth is infinite. You can use GitHub at a basic level in an afternoon. But there are developers with 10+ years of experience who are still learning advanced workflows, collaboration patterns, and optimization techniques.
I also got something wrong initially: I thought GitHub was a platform for showing off finished, perfect code. In reality? It's where messy, evolving, human code lives. Some of the most respected repositories are filled with commits saying "Fix bug," "Remove unused import," "Oops, that was wrong." It's honest. It's real. And that's why developers love it.
Final Thoughts
If you're reading this and thinking "But I'm not a programmer, so GitHub isn't for me"—reconsider. Even if you never write a single line of code, understanding GitHub gives you insight into how modern tech teams work, how collaboration actually happens at scale, and how to manage evolving projects.
And if you are learning to code, or thinking about it? Start now. Create an account today. Don't wait until you've built something "good enough." Upload a simple project. Make commits. The learning happens by doing, not by reading about it.
The you from two years ago—or the version of you that's intimidated by this—will thank future you for starting. GitHub isn't mysterious. It's just a tool that makes sense once you've used it a few times.
Commit (pun intended) to learning it. Your career—and your code—will be better for it.
— Dattatray
Writing this from a local café in Kalyan during my commute planning time. If you're learning to code or working with data, drop me a note about what's confusing about GitHub. Happy to clarify.
Dattatray Dagale
Data Analyst • Blogger • Mumbai
I'm a data analyst from Kalyan, Maharashtra, working at Morningstar. I write about personal finance, career growth, and everyday life for Indian millennials — the stuff I wish someone had told me earlier.
Written by Dattatray Dagale • 03 August 2026
.gif)
.png)
.png)
0 Comments