Define “learn git”? For the few commands I actually uses, I don’t remember it being any more than a day. I don’t see a reason to become an expert and things I might only use once every 5 years, if that.
Even Linus Torvalds only really uses a few commands.
> Torvalds described himself as a casual user of Git who mainly uses just five commands: git merge, git blame, git log, git commit and git pull – though he adds later in the interview that he also uses git status “fairly regularly.”
mikewarot · 4h ago
I couldn't make heads or tails of Git for the longest time, until it dawned on me that my mental model of what it was, was completely wrong.
I thought it was a very sophisticated system of file version management that very carefully measured deltas between versions of files, and stored only those deltas. If you believe this, you'll experience nothing but grief with Git, because that's not what it is.
It actually stores everything you tell it to, and can optionally compress it down to deltas. The storage at the root is all content based, instead of file name based, so if you have 5000 different names for the exact same 1 megabyte of stuff, you'll only store it once, along with all the names (and other metadata it uses internally).
lioeters · 2h ago
I've been using Git for years and haven't learned even half of it. I use a small subset that I understand, and the rest I learn about (or refresh my knowledge) when I need it.
Bender · 4h ago
I was used to subversion so I found a cheat-sheet for git for subversion users and that was mostly good enough for my use cases. Over time I learned more out of need and curiosity. It was not a one and done but the basics were a few minutes.
chistev · 4h ago
You never do. You just learn what you need for your daily needs.
Even Linus Torvalds only really uses a few commands.
> Torvalds described himself as a casual user of Git who mainly uses just five commands: git merge, git blame, git log, git commit and git pull – though he adds later in the interview that he also uses git status “fairly regularly.”
I thought it was a very sophisticated system of file version management that very carefully measured deltas between versions of files, and stored only those deltas. If you believe this, you'll experience nothing but grief with Git, because that's not what it is.
It actually stores everything you tell it to, and can optionally compress it down to deltas. The storage at the root is all content based, instead of file name based, so if you have 5000 different names for the exact same 1 megabyte of stuff, you'll only store it once, along with all the names (and other metadata it uses internally).