Every time I hear about no code, I think about the code written by PROFESSIONALS that leads to list like Dan Luu's "Everything is broken": https://danluu.com/everything-is-broken/
If professional at top quality firms with the best tools can't write code that works, how is "no code" written by people that don't understand going to work better?
No-code is more likely to be written by people who are direct experts in the business domain, unlike the telephone game that is the development cycle in most software orgs.
I work with experts in the business domain, often C-Suite as a consultant. I've come to understand the domains almost as well as them for the companies I work with. While this knowledge is invaluable, and critical to getting the solution right in my experience they still would be completely lost when it comes to a no-code solution.
They generally only think happy path and have a really hard time understanding why you need to think about edge cases. They don't understand how to structure data or implement robust processes.
No code is great for very simple things. Fill out a form and send it in an email. But for more important and complex things we'll still need programmers. I'm not yet convinced that no-code is an amplifier for programmers. Beginners maybe, but more experienced developers are in my opinion far more likely to be productive in a text based environment.
"No-code" programs are still programs; each visual node or block or whatever is isomorphic to a construct in some programming language. Being code, it has to be maintained, especially as business needs shift, and "experts in the business domain" have other, better things to do with their time than maintain a bunch of computer programs. Thankfully, there are people in the company who specialize in maintaining computer programs -- software engineers. Which means that ultimately, software engineers will be responsible for all that no-code, and in addition to the usual telephone game they must contend with rat-wrestling some near-undebuggable node graph that lives only in a proprietary tool into doing what they want rather than using the tools they're familiar with and best at (ordinary textual code, version control, debuggers, etc.). And, Syndrome style, the company ends up throwing away the valuable time and effort of real software engineers so some mid-level manager can pretend to be one (and walk away when they get bored of that).
If professional at top quality firms with the best tools can't write code that works, how is "no code" written by people that don't understand going to work better?