git is asymmetric autism

I can't believe anyone could come up with an information model and user interface so convoluted and incoherent. Just one example of many such vomit-inducing ones:

to setup a remote tracking branch of "remotes/origin/master" you'd do:
git fetch origin master:remotes/origin/master

but to delete the same thing you'd do:
git branch -rd origin/master

see the autism there? the two commands do not specify the same identity for the same object. I could go on and on and maybe even put up a blog post but I'm not one of those "hacker" news faggots.

Another git fuckery is the git config command. Notice that some config keys are camelCase and some are smashedlowercase. How is this coherent in any way? And I can even bet the way they handle it is by literally patching up the .git/config file, probably by using some vile perl script, rather than serializing/unserializing a coherent model and using validation. For example, I can get that file to have the following contents not by editing it directly, but by using the git-config command:

...
[merge]
[merge]
        defaultsToUpstream = true
...
There are a couple of WTF in that snippet: a) how is it possible that git-config can have two "merge" config sections? and b) defaultsToUpstream is not even a valid configuration variable.

Obviously no configuration file schema validation was made. git confirmed for amateurish programming at best. a toy project indeed.