Fossil was created by Richard Hipp, who's also the creator of SQLite.
Fossil as a version management system gets completely out of the way.
In all the years over used Fossil, I've rarely had to use more than a few commands and have never had to understand any underlying concepts, let alone trying to figure out how to use the commands.
Additionally, fossil also comes with a wiki and a bug tracker, which is a bonus.
Generally most IDEs will help you out with basic git tasks without even needing to know commands. There also dedicated GUIs for git.
Though for full time devs just learning how to use plain git isn't that hard. I very rarely have to look up git commands these days. You can limit yourself to the basic commands first.
This method also lends well to problem solving. You don't look at a repo and immediately think 'what commands will I use?'. You start with the problem. Then you formulate a solution as a sequence of operations that you know. You may be able to solve a problem with more operations even if you know fewer operations. Finally, convert each operation into a command and execute them.
Even the pro-git book is structured this way.