This content originally appeared on DEV Community and was authored by Gauri-Khanolkar1
Even after being involved in the field of Computer Science for the past 7 years (as a student and a professional), I am still not as proficient in Git as I would like. This is because I used TortoiseSVN in my previous job.
Why TortoiseSVN Slowed My Git Learning
TortoiseSVN uses a centralized version control system (CVCS) model, where the "trunk" typically represents the main development line or the latest stable version. While it’s great for handling large binary files, it has some limitations:
- “Branching” is implemented as directory copies, not as first-class objects
- A stable network connection is required to interact with the central repository
- Developers do not usually have a full local copy of the repository history
As a result, I rarely needed to think about distributed workflows or advanced branching strategies — two key parts of Git.
Why Git Feels Like a Necessity Now
Git is a distributed version control system (DVCS) that gives each developer a full local copy of the repository. That means:
- You can work offline
- Branching and merging are fast and flexible
- Collaboration scales better across teams
In hindsight, I believe Git is not just better — it’s essential for modern developers.
How I Started Learning Git
Here are two excellent resources that helped me get started:
These gave me both the big picture and the hands-on skills I was missing.
More on Git vs SVN
If you’re curious about the differences between the two, this article is a good summary:
SVN vs Git
This content originally appeared on DEV Community and was authored by Gauri-Khanolkar1