I absolutely love using git on the command line. I’m comfortable with the commands, and there isn’t much need for clicking since a lot of it is just typing commands, viewing files/diffs, repeat until files are staged, committed, and pushed up. Who needs a GUI for that?
OTOH, I really like postman for constructing and templating network requests. There are a few helpful panes and forms that just fit better on one screen that I can interact with.
To say working with GUIs makes someone a worse engineer sounds very short sighted to me. IMO the best engineers are the ones who use tools that maximize their efficiency.
You should give a git GUI a whirl. I like Fork. I definitely made do for years with the command line, but there were things like browsing all the diffed files between 2 commits that feel like inherently visual tasks to me, and the GUI makes that so much more natural.
I absolutely love using git on the command line. I’m comfortable with the commands, and there isn’t much need for clicking since a lot of it is just typing commands, viewing files/diffs, repeat until files are staged, committed, and pushed up. Who needs a GUI for that?
OTOH, I really like postman for constructing and templating network requests. There are a few helpful panes and forms that just fit better on one screen that I can interact with.
To say working with GUIs makes someone a worse engineer sounds very short sighted to me. IMO the best engineers are the ones who use tools that maximize their efficiency.
Postman is literally the only GUI I use for development, except for a browser I guess. Everything else is in terminals/WSL2 at work
You should give a git GUI a whirl. I like Fork. I definitely made do for years with the command line, but there were things like browsing all the diffed files between 2 commits that feel like inherently visual tasks to me, and the GUI makes that so much more natural.
I do. It takes less time and is less error-prone to commit code, especially when you need partial staging, via a decent GUI.