I've had some bubbling thoughts about no-code that I think just congealed: No-code is subject to simplicity vs easiness just like code is (https://www.infoq.co

I've had some bubbling thoughts about no-code that I think just congealed: No-code is subject to simplicity vs easiness just like code is (https://www.infoq.com/presentations/Simple-Made-Easy/ https://www.infoq.com/presentations/Simple-Made-Easy/). No-code tools tend to put a huge focus on doing one or both of these things. They're core value-props. But I think the question of whether or not a tool gives you sustainable value comes down to the simplicity axis (vs just making it easier to add more complexity) A no-code tool that's easier but more complex than the equivalent code solution is probably going to be a net-loss, at least in the long run. Whereas a no-code tool that helps keep things simple by presenting a narrow, focused representation of a system (instead of general-purpose code) can be beneficial. In a way, no-code can be thought of as a(n invisible) DSL + a GUI