It takes a week to learn Python syntax, it takes 10 years to be a good software engineer. Engineering software without code is what the most senior software engineers do all the time because the less experienced folks need (want!) direction from them and they have the knowledge and wisdom to provide it instead of coding.
I think that’s harsh. There’s a place for low/no code solutions. It’s not for nothing that Excel runs the world. But I would agree that there are definite limits, and implementations don’t do themselves favors when they make short term decisions (visual representation and JSON serialized code, I’m looking at you)
Excel definitely does not run the world and most usage of excel is formula resolution, which is not programming. Of course, we may have vastly different understanding of what “running the world” entails.
"Syntax is the easiest part of being a software engineer."
This is probably the best quip I've heard all week.
I'm developing a language with "no syntax", every token is executed immediately, making it trivial to create arbitrary syntax at any point in the file (literally you could define a function that implements SQL syntax and then call it - you are now using SQL syntax).
I don't necessarily recommend it for every language but it's really interesting how little it actually affects the hard problems of software engineering.
It takes a week to learn Python syntax, it takes 10 years to be a good software engineer. Engineering software without code is what the most senior software engineers do all the time because the less experienced folks need (want!) direction from them and they have the knowledge and wisdom to provide it instead of coding.