Equating MDD with low/no-code feels like classic tool tunnel vision, with confusion on one particular notion of How for the broader Who/What/Why. -- Who/What/W

Equating MDD with low/no-code feels like classic tool tunnel vision, with confusion on one particular notion of How for the broader Who/What/Why. -- Who/What/Why: From a design perspective, Low-Code means productivity for someone like a BI Analyst who will jump crazy hoops to stay in a UI + SQL and never go deeper, while No-Code is not-even-SQL. It's not even that clear cut in practice: Even if a no-code UI allows visual coding, many users will still consider that "someone else's job" for most of their work. -- How: Whether it's MDD, neural nets, program synthesis, or the latest VC-fueled JS-is-the-new-VB dumpster fire ready to implode, it's the devs who care, not the user. Interestingly, as soon as you appreciate the constraints of the Who/What/Why, new implementation dimensions open up for the How. We're picking our own pieces for the How part of no/low-code (rejected the MDD + JS approaches), but IMO just as important, working through design considerations for the social & collaborative nature of code, esp. as it enters team/org/OSS/etc. scenarios. It's sort of like, all social networks are basically the same from 10K ft, but it's not easy getting the design decision right of how 140 characters for dense broadcast x AI-mediated voting will define a successful niche like 'community newsfeed for between tasks on your laptop + on-the-go'. Edit: Historical note on the How - MDD is from a fun era when folks were figuring out domain-specific workbench tools and what becomes possible with them. While some of that is continuing even today (esp. in Europe!), most R&D here has largely advanced to program synthesis (esp. via SAT/SMT), and much more nascent, via neural nets. That's far out enough that I can count on my fingers how many startups are here, vs more VB/Excel/Hypercard-in-JS