I hear you. I was exactly the same. I still am, in a way, ironically I'm considered the local "git guru" at work, and I regularly save people when they're stuck.
My main pain point is that all the tutorials etc seem obsessed with the command line.
Being a visual person myself, with a horrible short-term memory, I've never been comfortable with the command line tools, I've always preferred GUIs.
The problem is that all tutorials mix up two different things: git's concepts, which is fine, with the command line syntax, which for me, personally, was confusing and inconsistent, especially if you don't know it yet.
With the command line I feel like I'm groping blindly in the dark (reinforced by the dark background, I guess).
From my point of view, all git tutorials, and almost all git answers in SO, are written by a bunch of borderline autistic and slightly sadistic people (so, programmers...), who seem hell bent on shaming me for being a visual person and not remembering arcane command line invocations. :-)
I admit that for a very long time I felt ashamed of myself, like I was not "man enough" for not remembering and mastering the command line. But this implicit shaming has to stop. There's nothing wrong in having lousy short term memory, and being a visual person. I'm still able to ship software, solve many bugs, and run a team.
I've tried different GUI tools, but Tortoise Git was what I use day to day, it's great, I keep its log view open all day and refresh it before, during and after each git action that I do, to make sure everything is fine.
If you're like me, I suggest you install it and try doing some tutorials using only it, dropping to the command line only as a last resort.
This may help you even as a temporary crutch if you really want to actually learn / memorize the command line syntax.
Looking at the visual advance of history, I understood the relationship between remote and local branches, merging, rebasing, I could see that rebasing leaves the original commits and what it does exactly, etc. Like I said in another comment here, many actions could also be done directly from this view.
My "secret weapon" when I'm helping my team grapple with git problems is opening Tortoise Git log view, pointing at the graph there and saying "ok, we are here, but we want this to be here and that to be here and all these blue lines to go away, so how would YOU do that?" and thus lead them to the answer.
It's not perfect and it has bugs, but for me, personally, it was the thing that made like git just a bit better.