Why I don't use a GUI for Git
I've been a Git user since my first full-time Developer position in 2010.
I've used other version control systems, too, early in my career, but I settled on Git and haven't looked back.
I've used GUI tools for Git, such as Sourcetree and GitHub Desktop, but I prefer to use Git on the command line instead of a GUI or TUI.
As a Developer who uses a command-line-focused workflow and works mainly in a terminal, there is less context switching, but I want to focus on learning the tool itself rather than a wrapper around it.
Some GUIs add their own terminology or functionality, making it difficult for people to debug something on the command line if they experience an issue.
It's easier to solve problems if you understand the tool itself.
What if I had a favourite Git GUI that became no longer supported or maintained?
Would any time spent learning that GUI have been wasted?
This was also a reason why I switched to using Docker and Docker Compose instead of pre-built wrappers.
I want to better understand and be efficient with the underlying tool, not only someone else's implementation of it.
- Oliver
P.S. If you're creating a new Drupal module, try my free Drupal module template.
