This is not true at all, and your examples are bad.
You don't need to know how btree's work to use SQL, true, but you need to know they exist and how they can be used by the database.
You don't know how to rebuild an engine to use a car, but you need to know what to put in the gas tank, when to change the oil, when to change the tires, what tires you can buy, how much air goes in them. You have to know a lot about how a car works to operate a car, or you have to pay someone to figure it out for you every time something needs done.
Git is the same. You have to know about how it works, not all the details of how it works. You could hire someone to do everything in git for you like you probably do with a car, but Git isn't a tool for stupid babies, it's a tool for professionals, and frankly professionals should know how their professional tools work.
If you can't be bothered or struggle to understand how your tools work as a professional, you should change professions as you are incompetent. If you think it's better if you don't have to know, then you will be passed by like you are standing still in your career by people who don't have qualms about knowing how things work and therefore can solve lots of problems in a couple minutes you think are too icky to bother to understand and would take you weeks.
(Note: I'm saying 'you' but I'm not addressing anyone in particular with that, so please don't take this as some kind of personal attack.)
You don't need to know how btree's work to use SQL, true, but you need to know they exist and how they can be used by the database.
You don't know how to rebuild an engine to use a car, but you need to know what to put in the gas tank, when to change the oil, when to change the tires, what tires you can buy, how much air goes in them. You have to know a lot about how a car works to operate a car, or you have to pay someone to figure it out for you every time something needs done.
Git is the same. You have to know about how it works, not all the details of how it works. You could hire someone to do everything in git for you like you probably do with a car, but Git isn't a tool for stupid babies, it's a tool for professionals, and frankly professionals should know how their professional tools work.
If you can't be bothered or struggle to understand how your tools work as a professional, you should change professions as you are incompetent. If you think it's better if you don't have to know, then you will be passed by like you are standing still in your career by people who don't have qualms about knowing how things work and therefore can solve lots of problems in a couple minutes you think are too icky to bother to understand and would take you weeks.
(Note: I'm saying 'you' but I'm not addressing anyone in particular with that, so please don't take this as some kind of personal attack.)