When teaching the rudiments of programming to children -- like Scratch -- maybe.
In all cases, once again, "no code" doesn't make the programming go away, it just puts a visual skin on it that makes it prettier to look at but more difficult to manage over a system's lifecycle.
In the 1970s, secretaries at MIT used a version of Emacs -- Multics Emacs, which predated GNU Emacs -- to type up documents; and what's more, they automated common tasks with Emacs Lisp. They were only ever told they were customizing the editor, though, not programming it, so they could approach Lisp without fear.
The representation could be anything -- literally anything at all -- and as long as the end user doesn't believe they are doing "programmers' work" they will use it if it makes life less tedious.
Scratch is a good one. My daughter started using it and I was very excited to see her embrace it. It is a good tool to start thinking logically, understanding flow, and planning out a program...and debugging!
In all cases, once again, "no code" doesn't make the programming go away, it just puts a visual skin on it that makes it prettier to look at but more difficult to manage over a system's lifecycle.
In the 1970s, secretaries at MIT used a version of Emacs -- Multics Emacs, which predated GNU Emacs -- to type up documents; and what's more, they automated common tasks with Emacs Lisp. They were only ever told they were customizing the editor, though, not programming it, so they could approach Lisp without fear.
The representation could be anything -- literally anything at all -- and as long as the end user doesn't believe they are doing "programmers' work" they will use it if it makes life less tedious.