Graphical programming—or low-code/no-code programming—is excellent for education. When you’re trying to get an 8-year-old to understand programming logic and what software development can accomplish, the ability to create something concrete without spending months learning a programming language or debugging typing or syntax errors is powerful.
When you’re trying to develop a business application, one that has specific, pre-defined business logic associated with it, graphical programming will usually only get you 90% of the way there. When we’re talking about a business application, that isn’t enough. And in most graphical programming platforms, going from 90% to 100% is exceptionally hard.
Reducing Costs of IT,
Full Stack Deployment,
Machine Generated Code,
What is software development like today?
A complaint I heard from a CIO recently was that when talking to the high flying technologists at his firm he said: "they talked in strange names, Kafka this, docker that. Names of open source projects, APIs and languages that make him wonder if these people can program or just piece together technology and names? It's very easy to toss around a lot of names and convince somebody you know what you are talking about, but the real question: If you assume that you can do things like this; Is this the way we should be building software these days? Talk to developers today and a lot are doing something different than what we did just a few years ago. Today developers may use languages such as Ruby or Scala, PHP or Clojure or combinations of these things in a single project, they may use google APIs and back end as a service APIs, Salesforce APIs and APIs for doing pattern discovery, blob storage. They may use Storm or Kafka, App Factory, CEP, Stratos, docker, node.js or cassandra or an open source Identity Management. They may develop on IntelliJ or CodeEnvy in the cloud. They may build their technology with dependency injection, aspect oriented techniques, test using Chaos Monkey, appium and numerous other web services that in general allow them to have very high productivity. It is very likely they will complain bitterly if you don't have Git, Maven or Jenkins, Chef or Puppet and numerous other open source tools for them to use that they are familiar with. It's a new world that has evolved very rapidly. This cacophony of names is scary for some. I love this diagram that Kinvey came up with some time ago that illustrates some of the complexity of just the APIs for backend as a service in the new paradigm: