[BillyTheMage]

What you are fundamentally arguing is that you should be able to do something without learning how to do it. You mentioned you simply want to slap stuff into a box and never think about what's really happening. This is the problem.

Here's what you're probably forgetting: The language is that way because of how the thing works. If you don't understand the language, you probably don't understand how the database works under the hood either. And this will lead you to make simple mistakes without being able to debug them, and it will generally lead to bad design decisions because you didn't know any better.

Reminds me of when I was learning git. DAMMIT did I ever hate git. It was just so confusing, nothing made sense. I made a post just like yours here, decrying git as a total piece of crap that only brainwashed people would ever use. Like why can't I just say "git push something" and then it asks for my GitHub password, instead of all this nonsense about private keys and public keys and exporting and signing and holy fuck it never actually gets to the part where I have code and I fucking just put it in there and write down what I changed and push it and BAM it's actually done. Don't even get me started on branching and merging.

I finally let go of my preconceptions about how I wanted git to work and spent the time to learn how it really does work under the hood. And now I have no trouble using git. It was my own fault. My own mentality.

[ompogUe]

This. Learn how to learn. And the more you learn, the more (and faster) you can learn. I hit a wall with rounding in Qlik the other day, in 30 minutes of experimentation I had it nailed (as stupid as it is).

That said, I started programming in basic when <10 yo in 1980 on a mainframe, so am not a good example of someone who has been spoon-fed expectations of what it takes to be a true badass.