I am interested in Blockchain, Ethereum, and smart contracts. I currently develop SharePoint, but am looking to shift towards the cryptocurrency space.
This statement can be done the other way around too: It's 100% unnecessary to use Git in a GUI. I am a senior dev and rarely use Git outside of the command line. it is all preference.
You don't need to use a CLI tool to take advantage of the value git brings, but if one is to download and install git, they are installing the git binary which IS a command line tool. At GitHub we tend to recommend the CLI, but if folks feel good using a different tool to interface with Git, they should stick with it.
I'm a little bias, but lab.github.com is also a good learning resource.
I am interested in Blockchain, Ethereum, and smart contracts. I currently develop SharePoint, but am looking to shift towards the cryptocurrency space.
It depends on what you do. I find myself in many different environments frequently. I learned CLI because it would take too long, or I am not allowed to install preferred tools. CLI, just like vi, tends to be everywhere. if you always develop in the same machine, then OK, I agree.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This statement can be done the other way around too: It's 100% unnecessary to use Git in a GUI. I am a senior dev and rarely use Git outside of the command line. it is all preference.
You don't need to use a CLI tool to take advantage of the value git brings, but if one is to download and install git, they are installing the git binary which IS a command line tool. At GitHub we tend to recommend the CLI, but if folks feel good using a different tool to interface with Git, they should stick with it.
I'm a little bias, but lab.github.com is also a good learning resource.
Good point, Dan!
Very true, but the article and others like it seem to imply that learning to use it on the command line is absolutely essential. It isn't
It depends on what you do. I find myself in many different environments frequently. I learned CLI because it would take too long, or I am not allowed to install preferred tools. CLI, just like vi, tends to be everywhere. if you always develop in the same machine, then OK, I agree.