Chapter 1 · Lesson 2

Why Learn Git and GitHub?

See the real, everyday problems Git solves and why it became the industry standard everywhere.

Before we learn how to use Git, it helps to know why it exists. Once you feel the problems it solves, every command in this course will make sense — because you will know what each one is rescuing you from.

The problems Git solves

Imagine you are working on an important document, a website, or a piece of code. Without a tool like Git, three painful things happen again and again.

1. Lost work

You make a change, save it, and then later realise the old version was better — but it is gone. Or your computer crashes and takes hours of effort with it. With Git, every saved checkpoint is kept. You can always go back.

2. "Which version is the final one?"

You have probably seen folders that look like this: report.docx, report_v2.docx, report_final.docx, report_final_FINAL.docx. Which one is actually the latest? Nobody knows. Git keeps one file and a clean history behind it, so there is never any doubt.

3. Overwriting your teammates

When two people edit the same file and email copies back and forth, someone's changes get wiped out. Git is built so that many people can work on the same project and combine their work safely.

Before Git: a chaotic folder of duplicate files. After Git: one clean tracked timeline. ⚠ Before Git site_final.zip site_final_v2.zip site_final_FINAL.zip site_final_FINAL(2).zip site_USE_THIS.zip Which one is final? ✓ After Git Add homepage Add about page Fix the footer Latest version One file, full history
The same project before and after Git: a pile of confusing copies becomes one clean, tracked timeline.

Where people actually use Git

Git is not only for programmers. It is useful for anyone whose work is made of files. Here are some real situations:

  • Solo projects — keep a tidy history of your own work and undo mistakes instantly.
  • Teams — many people build the same product together without stepping on each other.
  • Open source — strangers around the world improve shared projects, one small contribution at a time.
  • Writing and design — track drafts of an article, a book, or a set of design files.
  • Data work — analysts version their scripts, notebooks, and reports so results are repeatable.
💡 Tip
Anytime you catch yourself adding _v2 or _final to a filename, that is a sign you needed version control. Git removes the need for those name games entirely.

Git in modern software development

In the software world, Git is no longer optional. It is the industry standard — the default way nearly every company and open-source project tracks its work. GitHub alone hosts hundreds of millions of projects.

This matters for you in a very practical way: knowing Git is an expected skill. When you apply for a developer job, you will almost certainly be asked about Git, and a GitHub profile is often the first thing a recruiter looks at. Learning it now puts you on the same footing as working professionals.

⚠️ Watch out
"I'll just keep careful backups instead" feels safe but is not the same thing. A backup gives you a copy; Git gives you a full, searchable history of every change and the ability to combine work from many people. We will see exactly why in Section 2.
Lesson Summary
Git is the safety net and the time machine for any work made of files — it stops you losing work, ends the "which version is final?" confusion, and lets people build together without overwriting each other.