GUI requires much more software engineering and development hours than a CLI to create. So yes it makes your a worse engineer; don't wait for someone to expose a feature to you via API and web interface if you can get there via CLI today. Cripes.

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (3 children)

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.

[–] [email protected] 2 points 1 year ago

Postman is literally the only GUI I use for development, except for a browser I guess. Everything else is in terminals/WSL2 at work

[–] [email protected] 1 points 1 year ago

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.

[–] Dumhuvud 1 points 1 year ago

Who needs a GUI for that?

I do. It takes less time and is less error-prone to commit code, especially when you need partial staging, via a decent GUI.