We live in an era of boom in demand for IT specialists. Companies strive to optimize and automate routine workflows in the struggle for efficiency, the cost of internal development centers is growing, and developers cannot cope with the amount of digital work. And there are many more new business ideas that require embodiment in the code now than developers who can turn these ideas into reality.
Here are some statistics:
6/10 CIOs expect that the lack of qualified will prevent them from further development
72% of IT managers say that the backlog in project implementation affects the work on strategic projects
<30% of open vacancies of technical specialists can be closed by qualified graduates
23% of IT managers say that the developers of their team have quite advanced skills
But technology changes life much faster than many people manage to adapt to it. The situation with programmers today is largely similar to the situation with medieval scribes. There were so many books and chronicles to copy that their number exceeded the number of people who could write and master the word competently. It came to the point that the monasteries took care of children from distressed families ready to study literacy and brought up scribes' workshops from them with promises to provide shelter and food. But Gutenberg invented the printing press, and the need for so many scribes gradually disappeared. So today, at the peak of the boom in demand for programmers, ML appears on the horizon, which helps to write code much faster and with less preparation. Obviously, as with specialists in book publishing, who have moved from manual labor to machines and computers, the need for IT programmers will not disappear, but creating code without the help of an AI assistant will become a niche direction, and the standard in the industry will be Low/No-code - so far this is an unconditional fact.
At the same time, the trend of replacing simple programming languages has been outlined for a long time, so the current transition to Low/No-code is not something unexpected for the IT industry.
At the same time, it is important to emphasize that this is not just the fantasies of a handful of digital visionaries, it is one of the key trends in the IT industry, which has long been monitored by major experts:
The issue of developing low/no-code tools has long gone beyond discussions in the expert environment, and the market has been formed for several years: both the demand for such tools from ordinary users and the supply from business are growing:
To date, there are already many "low-code" and other uncoded platforms on the market for business use options (in other words, non-consumer). These include Blender.io, Zapier, Tray.io (a London startup that raised a big round last fall), n8n (German startup supported by Sequoia), as well as large companies such as MuleSoft (acquired by Salesforce in 2018 at an estimated at $6.5 billion).
As an example of a promising player in the low-code market, I would like to cite the Berlin startup BRYTER.
The concept and existence of Bryter also erive from the trend of lack of code. It is based on the same ideas as IFTTT or Zapier, but unlike them, it is clearly aimed at users who are able to use parts of corporate software in their work, but do not understand how they actually work.
Bryter has intuitive tools that allow professionals to create, manage and sell interactive applications without programming skills. For example, the Bryter solution allows employees of accounting, law, regulatory and marketing departments without special technical skills or experience with development tools to create and run automated actions with databases and documents, build complex risk estimators and develop specialized ML bots. Now the Bryter team is launching BRYTER Open. While the basic BRYTER platform is mainly used by corporate business clients, the BRYTER Open project allows individuals, scientists and employees of non-governmental organizations to test the platform and create applications for non-commercial purposes. More than 50 university teams are already involved in testing.
Top comments (0)