Not sure if I get your point. Abstraction is a concept used by IT people to deal with complexity. You'll use Docker containers in order not to have 200 very specific problems and learn about the intricate details of all of them. Or use a turnkey solution because a working day has a finite amount of hours and you can just not care and have somebody else set the XY value of Postgres to 128 because that's somehow needed for software M on python x.xx... Of course you're then not going to learn about these things. It is not "bad", though, in itself to abstract these issues away from you. Same for the other things I mentioned, networking, virtualization. Abstraction there allows to swap out complex things, do things once and in a clean way because it's easy to miss things without abstraction and you always need to pay attention to a bazillion of specifics. Also helps with backups, deal with issues because things should break within confined layers, punch above one's weight, security, do something once and roll it out several times...

I think what you want to avoid is poorly designed or written software. Or poorly done setups. Or not learn about important things. Abstraction is generally something you want, especially with complex things.