Skip to main content

Low Code and No Code Platform == NOT with VISUAL Everything

It's interesting to read this article: The Evolution of Low-Code: Welcome to the Machine. The content is in my opinion just a marketing for Low Code Platform.

It is not true to say that the RAD tools are not successful. There are a lot of good RAD tools available from 1992 until today e.g. Delphi (Borland and now Embarcadero). No tons of generated code, very precise and works very good.

Using visual coding thing does not mean to have higher abstraction layer. And programming visual for logic like “if-then-else” with “flow chart” or BPMN or UML or other visual tools won’t scale. Therefore we still write textual today and not drawing everything to communicate. Drawing is ancient, exists before you can write and read. Visual and textual representation have their own role today in software.

Letting non-developers clicking visual programming tool means ‘horror” for the TCO (Total Cost of Ownership) of your app. Application development cost is always TCO and not only the first cost of developing it.

Also without the ability to leave such a platform, vendor lock in, I would say, everything is useless, I have seen a lot of such applications, which have to be re-developed. If you want to make the abstraction layer of software development higher, take a look at Spring Framework for Java. It definitely brings higher abstraction layer to compare with Java applications without Spring and no vendor lock-in.

Visual programming for UI is good, BPMN for Business Process modeling is the way to go and UML class model for Business Entities makes talking about the domain with everybody easier. But doing complex fine logic with visual programming won’t scale. Business logic is not just simple ScratchJr programming.

Comments

Popular posts from this blog

Creating Spring Bean dynamically in the Runtime

In my training someone asked me whether it is possible to create an object (a Spring Bean) dynamically so you can choose which implementation you want to have in the runtime. So at the compile time you don't know what object actually should be created yet. The application should decide what object to be created based on a property file.

1. We create an annotation so we can mark the method which should be able to create the object dynamically:

...
package your.package;
...
@Retention(RetentionPolicy.RUNTIME)
public @interface InjectDynamicObject {
}
...
2. Use the new created annotation in your method which should be able to create the object dynamically:
... @Named("customerBo") public class CustomerBoImpl implements CustomerBo { ...     @Override @InjectDynamicObject public Customer getDynamicCustomer() {         return this.dynamicCustomer; } ...
3. Write an aspect with Pointcut and Advise which change the object returned by the method in the step 2:
... @Named @Aspect public class Dyn…

GWT Training for Java Developers with GWT Boot

I'm always a fan of "one language solution with Java to rule them all", here are sofar my opinions about Polyglot Programming:
Why "Polyglot Programming" or "Do It Yourself Programming Languages" or "Language Oriented Programming" sucks?Warum Polyglot Programming nicht praxistauglich istJava als universelle Programmiersprache Until today nobody can excite me about Polyglot Programming. My points are getting another big support after I read the "Rise of Polyglot at Netflix" presentation which says that Polyglot is expensive, also for company in the category of Netflix. At the end of the day we need to be productive. Our applications should have a high quality standard and the total costs (TCO) of our software development should be manageable and low. To be able to reach this goal we have Java with Spring Boot or JakartaEE on the server-side which offers REST interfaces. So logically for user interface development on the client-side I…

Smart Home Sweet Home with Gigaset Elements?

Introduction
Last week I had a chance to try the Smart Home solution from Gigaset Elements. I read some articles about this product which said how easy to install this product for dummy users. Those articles woke my interest and I began to google products for Smart Home solutions.

In this article (German language) you will find a nice overview about some products for Smart Home, which can be bought in Germany. The Nest product from Google is still not available in Germany. Although it seems that RWE will offer Nest products in Germany in couple of months.

The installation of Gigaset Elements was really easy. The problem I encountered was to add the sirensensor. I had to push hard the button on the siren sensor at the same time with the button on the base, so that they can communicate with each other. After about one hour I managed to install everything properly.

Points to mention
Generally the idea is very nice. Gigaset Elements try to push KISS (Keep it Simple Stupid) principle. Howev…