Speaking of visual anything. I once ran across an experiment* where instead of leaving non programmers with the GUI, they encouraged them to experiment with a C

Speaking of visual anything. I once ran across an experiment* where instead of leaving non programmers with the GUI, they encouraged them to experiment with a CLI to do their tasks. Guess what, everyone got more productive and preferred the CLI after they figured it out. So do you have to waste resources on pretty graphs, or is it more efficient to stick a text based DSL in there for your non programmers? Is the current fetish for meta meta meta programming a feature or a bug? Can't you give your business analyst a BASIC like DSL that they can use to script most of their specific problems away? Like, you know the stuff in ms office? Of course, to do that you need to unlearn your C++ and Rust and even python while designing the DSL :) * With web search being what it is these days, I'm not going to even try and find a citation. ** Even what TFA is talking about can be considered a DSL. A DSL for debugging and software maintenance. They say it should be graphical, but a good part of the stuff that's mentioned would work as well in text reports.