I've come across many devs who think what will impress is their use of the git command line interface. Or another command line tool like vim. However, they also don't have the extensive knowledge to impress with. What they do have, is a time sink that's hard to watch.

Your development flow doesn't need to be complicated. You can't know the ins and outs of every tool. You'll do yourself a disservice by slowing yourself down. Remember the acronym K.I.S.S? Well keep it simple, stupid. Your priority is to deliver, and learn.

I like using a GUI for Git. Specifically GitHub Desktop. Most of my git interactions are really simple. It's mostly just pushing commits to a branch or pulling down someone else's to review their work. When I need to resolve merge conflicts I use my IDE of choice, Webstorm and its handy merge conflicts GUI. For my workflow these are simple tools which help me deliver and get the job done.

However, I could also use Git at the command line. I know Git inside and out. But it is slower in achieving my most common actions than GitHub Desktop is. The same is true for merge conflicts. Your development flow should be full of tools that you know well and are comfortable with. Whether that's using the command line or not.

Don't be like the dev I managed who insisted that they use vim for an IDE. It's a cool tool, don't get me wrong. But they couldn't complete simple actions like exiting vim.

Your tools work for you, you don't work for them.

If you're going to insist on using a tool spend the time to make it work for you. If you're getting stuck on simple actions you still have some learning to do.

Keep it simple, stupid.