3 ms·

`git merge`, `git rebase`, `git rebase -i`, `git revert`, `git checkout`, `git reset`, `git reset --hard`, `git log`, `git reflog`, `git stash`, `git cherry-pic

`git merge`, `git rebase`, `git rebase -i`, `git revert`, `git checkout`, `git reset`, `git reset --hard`, `git log`, `git reflog`, `git stash`, `git cherry-pick`, `git add`, `git rm`, `git status`, `git commit`, `git push` and squash, reword, fixup, pick and f@ck knows what else. Who wants to really use all this bullshit just to do versioning? Especially if you are a beginner, this doesn't make any sense (and not even later in many cases) In my experience during the last two decades or so in the industry, there is always a special kind of person in the IT field who takes pride knowing all the nitty-gritty details of the latest shiny versioning tool. Should it be IBM Clearcase or SVN or CVS or Git or Mercurial. Even though that most of these softwares only slightly improve the user experience and only claim to solve the users' problems, so they over promise and under deliver. But there is this special kind of person who takes pride in it. To me this seems like someone who takes pride in knowing all the details of his toaster. Might be impressive, but also completely irrelevant for the 90% of the toaster users.

rimliu 7y ago
You don't need all this to just do versioning.
eitland 7y ago
> Who wants to really use all this bullshit just to do versioning? Nobody. It is a strawman or should be. You can teach everything a beginner need to know about git as an ordinary team member in less than one A4 page and less than half a days work. Of course this means part of what you teach then is when to talk to the git expert on the team but as long as beginners stay away from squash, rebase etc they should be fine. Ok, add another half day about effective diffing and merging too, it is a big topic and useful outside the context of git too (local history etc).
- BeetleB 7y ago
  >Of course this means part of what you teach then is when to talk to the git expert on the team but as long as beginners stay away from squash, rebase etc they should be fine. The thing is, if you ask 10 git experts what should be taught to a beginner, you'll get 10 different A4 size pages. As an example, when my team (finally) switched to git, the expert on the team made a tutorial on what commands to use, and what to avoid/ignore. Looking at it now, he taught that rebase is almost mandatory and gives problems you're guaranteed to run into if you don't use rebase. Not saying I agree with him, but that is one problem with git - no clear consensus on beginner friendly features.
Gracana 7y ago
It's a tool that you use many times a day every day for years, and understanding how to do it well helps you make money... doesn't it make sense to spend some time to learn about how it works and how to use it?

rimliu 7y ago

You don't need all this to just do versioning.

eitland 7y ago

> Who wants to really use all this bullshit just to do versioning? Nobody. It is a strawman or should be. You can teach everything a beginner need to know about git as an ordinary team member in less than one A4 page and less than half a days work. Of course this means part of what you teach then is when to talk to the git expert on the team but as long as beginners stay away from squash, rebase etc they should be fine. Ok, add another half day about effective diffing and merging too, it is a big topic and useful outside the context of git too (local history etc).

BeetleB 7y ago
>Of course this means part of what you teach then is when to talk to the git expert on the team but as long as beginners stay away from squash, rebase etc they should be fine. The thing is, if you ask 10 git experts what should be taught to a beginner, you'll get 10 different A4 size pages. As an example, when my team (finally) switched to git, the expert on the team made a tutorial on what commands to use, and what to avoid/ignore. Looking at it now, he taught that rebase is almost mandatory and gives problems you're guaranteed to run into if you don't use rebase. Not saying I agree with him, but that is one problem with git - no clear consensus on beginner friendly features.

Gracana 7y ago

It's a tool that you use many times a day every day for years, and understanding how to do it well helps you make money... doesn't it make sense to spend some time to learn about how it works and how to use it?