problem is, the hard part is not coding, the hard part is transforming requirements and workflows into logical structure a computer can understand.
that's the bottleneck, whatever the language.
the new literacy would be not just to see a lego construction and understand the pieces involved, but to see the final construction and to be able to recover the build instructions by sheer mind gymnastic.
> the hard part is transforming requirements and workflows into logical structure
that's like saying for painting a picture, the hard part is knowing where to put the paint. The act of slashing paint on canvas itself is trivial.
I think the real problem is that there hasn't been any proper primitives created - primitives that can be linked together to produce what looks like another primitive. I guess the non-physicalness isn't helping, because lego works really well as a building primitive.
primitives that can be linked together to produce what looks like another primitive
This was the design intent behind UNIX pipes; text processing through composable programs.
I'd go in the other direction and say the problem is too many primitives; it's easy to spend all your time just evaluating possible solution components.
that's the bottleneck, whatever the language.
the new literacy would be not just to see a lego construction and understand the pieces involved, but to see the final construction and to be able to recover the build instructions by sheer mind gymnastic.