That's me with Git. If my colleagues need help and they're on the CLI, I can just literally spell them out everything they need. But if they're using some sort of Git GUI, it's always like, WTF are all these buttons? Are you sure, Git even has that many features? How do I tell it to do XYZ with certain flags? Are you sure, this isn't missing some Git features?

[–] ksynwa@lemmygrad.ml 2 points 1 year ago (1 children)

I think git's CLI is not a good user interface but with how ubiquitous it is as a VCS, it's better to power through the oddities and become proficient in it.

[–] Ephera@lemmy.ml 2 points 1 year ago

Yeah, I always tell new trainees, they can use a GUI, but they won't get around learning how the CLI works, as when they look anything up about Git, they'll only find commands.

[–] Adda@lemmy.ml 2 points 1 year ago* (last edited 1 year ago) (1 children)

This is myself with my colleagues. I use Lazygit and GitUI daily, otherwise I would spend a lifetime typing out numerous Git commands every day. And it is amazing how much one can do and how fast with these TUIs. But if a colleague needs something, and of course, they do not have these programs, all I can is just shrug and point them to the internet, as I have already forgotten all the little flags and parameters for more advanced commands. It is incredible how easy these TUIs make Git to use.

[–] Ephera@lemmy.ml 2 points 1 year ago

Well, cool that it works for you, but that is kind of why I stay away from the GUIs, too: I do not want to forget how the CLI works. Or even just become less comfortable in it.

When you need to look anything up about Git, you get told commands, and I need to mess with Git repos on remote servers every now and then.
Also, even if I can't help colleagues in their GUI, they generally have the CLI somewhere.

I do use a shell with type-ahead suggestions to alleviate the typing somewhat.