This is very true. Someone who builds websites/CRUD screens and someone who programs for NASA might both call themselves programmers but they are very different jobs. I'm fairly good at the first one, but I probably wouldn't know where to begin for the second.
And even if you're working for NASA your job may not be inherently more difficult than CRUD, it's just different. Where I care about server latency, as NASA engineer you'll care about real-time guarantees. Where I care about UX, you'll care about code correctness, etc.
Ability to comprehend abstractions is a bit orthogonal to all of this. It starts to shine when you need to architect a complex system or model some real-life phenomenon.
I always wonder why CRUD is so looked down upon. I do the database for a sequencing center (so essentially CRUD - though its a moderately complex schema), and I work with a lot of bioinformaticians. Their code is often just counting stuff, and or applying some basic statistics. Usually the quality of code is really bad (often the script will only be run on one or two data sets, so that's not such a problem).
Now compare that to a decent web app written to a good standard. There can be orders of magnitude more complexity in the second, even if it is "only CRUD". Getting HTML, CSS, Js working together, maybe contacting the database over REST, maybe just getting standard HTML. Maybe there is some SQL that needs optimized. URLs need to be set up. It needs to be deployed on a server somewhere.
I think I could do the bioinformatics job with if I was given decent description of the problem, but I would be surprised if any of them could do mine without a serious amount of learning.
