I am not familiar with this particular product, but I have some familiarity with a “theory” (such as it) without code development.
Primitives of programming languages exist for some reason. Thus, there is a tendency to the gradual accumulation of functions that correspond to primitives of programming languages: “code” or “mouse-based” development systems: something similar to function calls (for reusing design fragments), links to parameters inside functions, then , that loop, conditional branching, things that combine several actions into one action, things that perform arithmetic or string operations, etc. At this point, they end with the same problems as all development systems, which all stem from the trend, users must press the envelope in search of more complex problems to solve. Therefore, they need refactoring and other nice features of the IDE style that will help them cope with complexity - by that time the “codeless” difference is more related to marketing than to the actual user interface.
We even see this trend in many attempts to “start over” with a new set of primitives in the text source language. Haskell does not really eliminate stateful procedural coding. It has a way to imitate features that taste pretty authentic, because if it weren’t, users would try to imitate it themselves and make a mistake.
source share