Exploratory Data AlexI wish to blur the line between _using_ a computer and _programming_ a computer.
There's this barrier between computer use and computer programming and it's mostly *not* computer science knowledge, but complexity of languages and the tools for working with them. I want to lower this barrier. I doubt that "low code" tools are the way, but rather, more powerful, higher-level languages and scripting interfaces with more approachable tooling.
Arik Friedman@alexkyllo
Would you consider Excel a "use computer" or a "program computer"?
Would you consider Excel a "use computer" or a "program computer"?
@arikf both, and that's a big reason for its popularity. But even within Excel, there's a significant barrier between using it with formulas and programming it with VBA, and the VBA interface hasn't been kept up to date with the rest of the product.
@alexkyllo
When I asked about use vs. program I wasn't referring to the VBA part (which is clearly code), but about the formulas. This was before my time, but I suspect that the spreadsheet paradigm (introduced by VisiCalc) pushed what used to previously require programming into the "use" domain. I'm actually not sure if this paradigm would fall on the "no code" or on the "scripting interface" side...
When I asked about use vs. program I wasn't referring to the VBA part (which is clearly code), but about the formulas. This was before my time, but I suspect that the spreadsheet paradigm (introduced by VisiCalc) pushed what used to previously require programming into the "use" domain. I'm actually not sure if this paradigm would fall on the "no code" or on the "scripting interface" side...