Hi, my name’s Aaron Powell and I’m a Cloud Advocate at Microsoft. My area of specialty is front-end web dev and .NET (especially F#), but I enjoy doing silly things with technology.
I default to the CLI because I really like to understand how something works. In my experience most GUI tools are just executing the CLI commands, often batching a few together to undertake a task.
By using the CLI I get to know what the GUI would be doing if I don't have it available to me, so I'm never left high and dry.
When I was doing consulting the CLI was also a great normaliser. I'd be training someone on git and you'd have 1 person using Git Extensions, another using GitHub for Windows and someone using a different GUI. By focusing on one GUI you wouldn't have the everyone able to follow along, but using the CLI meant that everyone had it available and they could translate your CLI command to their GUI equivelant.
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.
I default to the CLI because I really like to understand how something works. In my experience most GUI tools are just executing the CLI commands, often batching a few together to undertake a task.
By using the CLI I get to know what the GUI would be doing if I don't have it available to me, so I'm never left high and dry.
When I was doing consulting the CLI was also a great normaliser. I'd be training someone on git and you'd have 1 person using Git Extensions, another using GitHub for Windows and someone using a different GUI. By focusing on one GUI you wouldn't have the everyone able to follow along, but using the CLI meant that everyone had it available and they could translate your CLI command to their GUI equivelant.