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,
(Amplituhedron allows us to compute Quantum probabilities orders of magnitude faster than ever before)
API Best Practices,
Component as a Service,
Component based software engineering,
Faster Time to Market,
The scale is staggering
14 years ago I was running a group at TIBCO that was bringing TIBCO to the Internet. Yahoo!Finance was built on the TIBCO pubsub infrastructure. At the time Yahoo was the biggest cloud/internet company and the finance pages were the most popular pages on the companies web site other than search. The hits were astronomical even at the time. It was the fever time in the tech internet industry and everyone was following the stocks of the new internet players. Many people including myself had written programs that leveraged Yahoo's web site as an API to build applications for stock analytics, portfolio analysis and to embed in their own websites. I know that Yahoo was getting 100 million hits to the web site a day or more but probably few of those were really applications making calls. There weren't a lot of other APIs in the Internet at that time. I would guess that there were 10^9 a billion "pseudo-API calls"/month back then. This is the kind of traffic that a small startup would get today for its API. :)
I could talk about each of these components in isolation, for instance, Mobile and talk about the growth of it and changes it is fostering but you wouldn't get the big picture. The change we are seeing can only be understood by considering all these components together. They each affect each other and the widespread adoption and improvement in each drives the success of the other. Therefore, this article is intended to give you the context to understand the entire change we are undergoing rather than any particular element. By seeing that you see that adopting any one technology or doing any one thing will ultimately fail.
The idea of the virtuous circle is that each component of the circle has been critical to the success of the other parts of the circle. It is hard to imagine the success of any of these elements in isolation. The massive adoption of key aspects of the circle is clearly needed but each element of the circle has been key to the success and adoption of the other parts. The constant improvement in each aspect of the circle drives improvements in other parts of the circle driving more adoption and more innovation. The process feeds itself and grows faster as each element grows. It is impossible to say which element is less - critical so they have to be considered as one.
These components of the virtuous circle imply that to leverage the benefits of the circle you have to be using components of the circle in your processes. The more components you use the more benefit you gain from the circle and the faster the change you will experience. The combination of these technologies is being called Platform 3.0.
The benefits of each part of the virtuous circle
APIs are the honeybee of software (apis is latin for honeybee)
Accelerating Pace of Change,
Faster Time to Market,
InnerSource OpenSource Megatrend SDLC Enterprise R,
open source software,