But we will continue to see domain-specific tooling that require less "coding". There are plenty of "no/low code" CRUD app builders, tools that manipulate components on a canvas to create web pages, even tools to integrate different systems together. But the second you need to go off the trail, you've now got a big problem: you're constrained to doing things that don't break the no/low code environment, and that's a lot harder than rolling your own components and customizations.
Anything interesting enough to "disrupt" tech development will, almost by definition, not be possible in a no/low code environment.
It's robust and perfectly fine, you can even build full games without any coding at all.
Is it useful? Yes, but it would never replace "real" coding. Yet I'm excited to see any advancement on the field because it still feels like "magic" to some extent.
Unreal Blueprints isn't low code, it's just code, and it doesn't need to replace "real" coding because it is real coding.
It does raise the question where the line is. Something that I'd consider a low code / no code platform is webflow. My non programmer CEO used it to create our marketing website, and it solved something for us that normally is a very highly technical problem. He had a couple small visual glitches, he asked me to help and I discovered that it actually was a pretty thin abstraction layer over some good practice CSS, and so the glitches were easily fixed by me thanks to that.
Blueprint makes a programming language easy enough to use that a non experienced programmer might have a go at it, but in the end it's really just the outstanding library that makes it so powerful, you still need programming skills to solve programming problems with it.
But we will continue to see domain-specific tooling that require less "coding". There are plenty of "no/low code" CRUD app builders, tools that manipulate components on a canvas to create web pages, even tools to integrate different systems together. But the second you need to go off the trail, you've now got a big problem: you're constrained to doing things that don't break the no/low code environment, and that's a lot harder than rolling your own components and customizations.
Anything interesting enough to "disrupt" tech development will, almost by definition, not be possible in a no/low code environment.