Because most of the time, the complicated stuff is just a few simple commands chained together.
99.9% of the time, git is easy. You don’t need to do everything on the command line, especially when dealing with diffs and merge conflicts. But in my experience most devs who flat out refuse to use it don’t understand most of the basic concepts because it’s all hidden behind a layer of abstraction. That’s why when I teach the basic concepts, it’s command line only. At least you know what that big Squash&Merge button does and why you should never click on the big Rebase button on main/master.
Fucking backend developers who can’t even
git commitwithout their fucking IDE handling it for them.It’s so much easier to see diffs/merges with gui tools. 90% of the operations can be handled easily in the UI.
I only need to use the command line and use the docs when I do something complicated (I still screwed something up).
I do understand it’s there though, I’m not sure using it for the basic stuff would help me with the complicated stuff.
Because most of the time, the complicated stuff is just a few simple commands chained together.
99.9% of the time, git is easy. You don’t need to do everything on the command line, especially when dealing with diffs and merge conflicts. But in my experience most devs who flat out refuse to use it don’t understand most of the basic concepts because it’s all hidden behind a layer of abstraction. That’s why when I teach the basic concepts, it’s command line only. At least you know what that big Squash&Merge button does and why you should never click on the big Rebase button on main/master.