As with any groundbreaking innovation, one of the biggest obstacles to adopting tool platforms No-code will be the developers themselves. As in other industries where automation has disrupted business models, workflows and workplaces, Zero code development can do the same in many modern
Hi-Tech organizations.
Here's what classic programmers have to say about No-Code:
The software revolution we've already made is that a great many, if not the vast majority, of people between the ages of 16 and 20 around the world already know how to program with a mouse.
From now on, a new employee, whether blue-collar or white, is expected to understand the concept of telling a computer what to do with simple, sequential dots and clicks.
The future places equal responsibility on the developers of "no-code" platforms as well as on the people who can think logically and work "point-and-click" systems.
The future of programming depends largely on the resurgence of the Ada promise: code that is written to be read and understood by humans, and compiled to run on any hardware.
"As a developer, I've seen many companies try to offer this no-code software development solution. Usually, these no-code software solutions never fully meet companies' (client) expectations and companies end up reverting back to developers. The few companies who do stick with it, end up paying expensive developers to work with the limited no-code software and / or pay huge fees for custom features. All in all, it turns out to be a bad investment for most businesses."
One cannot but agree with this, since the developers of No-Code platforms at the initial stage of their scaling cannot take into account absolutely all the nuances in certain client tasks. The developers of such tools must constantly study the statistics of client requests and, with each new version, improve the logical core, offering developers an expanded set and versatility.
The history of PC development reflects the computing and software environment prior to Mac OS and Windows.
Before the user interface was converted to a graphical one, the mass use of computers was limited to technicians who were not afraid to navigate the prompts of DOS and other programming languages. Mac OS and Windows have leveled the playing field, allowing anyone to quickly learn, use, and adapt software applications to suit their unique needs.
Today we are in the same place and at the time when it comes to developing applications without code, and real coding of software applications is not limited to programmers only.
We invite a wide audience of interested specialists to participate in our open cross-industry projects, where, in our opinion, there is a great demand for robotics, while their budgets, for a number of reasons, do not allow investing in individual developments, and the robotics industry does not offer anything available for such industries.
No-Code - BEEPTOOLKIT tooling platform for development of robotics, automatics and smart systems.
PC-based tools that do not require programming allow juniors inside the tunnel to take the shortest path to finish.
The developer, using an external graphical interface, configures and runs a framework with dynamic as well as custom final state machines (FSM). Thus, a minimal, intuitive and simple set of instructions allows you to automate the programming process. The developer only needs an algorithm in accordance with his idea and a certain level of knowledge on working with binary logic signals. This is the ability to simulate an algorithm without connecting the hardware part of the project or with a connection.
Development of the hardware part of the project, etc. The generated software source code does not need the testing that usually occurs in scripting processes. The logical core of the platform uses tested and optimized G-code from National Instrument, which, through external instructions, is included by the developer into the behavioral script of the algorithm. As a result, at the output we have the generated software part of the entire project.
An important point in the toolkit is the function of saving the project in a binary file, where the log is written not only the executive code of the project, but also the communication settings, right down to the screen. This file can be shared with other developers or end customers. If necessary, it can be edited, which occurs in the process of changing the project with saving under the same or a different name. The project protocol can be edited exclusively in its creation environment.
So, How do we, the Beeptec Engineering startup, present version of the strategy for scaling and popularizing our No-code tool platform for the development of automatics, robotics and smart systems?
Hi Alexander, I have just watched the video of your software and read the article on the date plantations, the collecting of pollen and the fertilising of the female date flowers. I spent a lot of time in israel from 1997 through to 2001 as I was the technical engineer involved in setting up our Israeli office in Herzliya. I used to stay at the Dan hotel and worked for the InterSystems Israeli Country Manager, Trevor Matz. I wrote an application for the Mathematics Professors at Haifa University called "Just Ask" which was a web application in which the professors could write Mathematical questions using MathML markup language. The students would try and solve the problem, each question was presented…
That is cool. I was introduced to he world of robotics when I got a call from a very bright guy who worked for a Pharmacy Application Software company but had a company of his own that was basically a channel for him to explore technology R&D projects. He was driving a proof of concept to install 2 robots in a HIV/TB clinic run by an NGO called Right to Care. I mentioned the conveyor belt that transported the medications past a printer that attached a label to the medication packaging and then dropped the product into the bin of the ATM style machine. He designed the concept of this system in his garage using scraps of wood and carpet.…
Hi Nigel,
it was interesting to see your experience. It seemed to me that you took the diversification strategy into the existing open source platforms, as well as the hardware architectures of signal processors, for which their developers provide an SDK for working with register values.
The paradigm of our platform is based on a democratic principle in relation to hardware design without prioritizing external controllers (PLC, DSP, RTU and etc) and other equipment from specific manufacturers.
In our case, the logical core, in parallel with the generation of binary logic signals, is also a scripting environment.
As you rightly pointed out, end users can develop a complete stack of their ideas with saving the project in an external binary…
I have been a developer for 35 years. I have been present at every major leap in technology, language development and graphical capabilities. I am working with STEM at the moment and it is a step in the right direction. I believe that we are at a point where a nocode solution is theoretically possible. I would be interested to understand the factors that have made your solution possible. Nigel alm