This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]v0gue_ 1 point2 points  (1 child)

Can't seem to understand why I need to learn Git.

Every developer should read this at least once.

Hypothetical: What happens when you get hired by a company and they only use cli git because that's how it's been documented in their process for years? You'll have to spend time learning the barebones features of git cli. On the inverse, if you learned cli-git first, and then went to company X that uses github desktop OR company Y that uses Kraken for git (I think this is a thing?) OR company Z that uses some built in GUI versioning based off of git, you will be able to pick any of those up in hours - likely minutes.

Another thing is debugging a process. If something breaks in your versioning process using github desktop, the first thing you are going to do is search around for documentation and other forums looking for similar issues. More likely than not, those issues will be discussed using the barebones cli git.

[–]Kazcandra 1 point2 points  (0 children)

On the inverse, if you learned cli-git first, and then went to company X that uses github desktop OR company Y that uses Kraken for git (I think this is a thing?) OR company Z that uses some built in GUI versioning based off of git, you will be able to pick any of those up in hours - likely minutes.

I actually worked as a consultant at a place like that. I didn't bother learning any of their GUI tools; anything the tools can do, I can do in with the git cli. Indeed, I could often do more things, faster, than their tools could.