Yes there is a lot of boilerplate and plugging existing components together, but that stuff isn't the work that really brings in the bucks - it's the part where you are solving something previously unsolved, and making headway against ambiguous problem spaces that really differentiates companies/products/teams etc.
[1] It's more than being taught, it is being rewarded and punished on the notion of "one right answer" that happens in huge amounts of education. It gets mixed up with the limbic system and becomes a default assumption for everything. It has to be un-taught in a lot of contexts. Sure, there is a best or right answer for many things, and we need to show that too, but more education on how to deal with the ambiguous stuff is much needed.
Basically, you're saying people today can't handle frustration. I have a hunch that this is true, and someone should research into this.
It is the frustration and ambiguity that one has to deal with when solving technical problems. Remember, most technical problems aren't cut and dried - sometimes the problem is correctly finding what the problem is.
To be good in this industry - you have to want to go down the rabbit hole and spelunk. To get your hands and mind dirty.