In the previous article devoted to using the low-code in enterprise solutions
I've been talking about business. However, most of Habr users are engineers (Captain Obvious!), and in the comments to the article I came across a justified number of typical objections to LCDP (low-code development platforms) use. And while those who've never heard of the Dunning – Kruger effect are almost clicking a Dislike button, let's analyze the most common misconceptions and ideas.
In my opinion, the most common misconceptions are as follows:
Some people think that low-code is the use of ready-made products (and not a development philosophy).
- Low-code is perceived as advanced code-first platforms. One of my colleagues even gave WordPress as an example.
- Low-code does not provide for standard DevOps (code review, versioning, deploy, etc.), a standard code reuse, and other abstractions. And low-code is normally applied in some typical solutions (for which no-code is intended).
- Developers are better off writing a code with an actual value, rather than developing some builders.
- "Low-code is often incomprehensible, now it's a thing of the past. We'd rather code as usual." However, some developers still don't have a clear idea even about the DevOps and think it's a matter of role. So the situation with low-code is not unique.
Why did I raise the topic of low-code and IT industry development prospects? I graduated at Physics and Entrepreneurship. In the mid-90s, I owned the ISP Internet provider, and after that I held different positions starting from an engineer at Beeline to a managing partner of an automation software development company – it's my current position that I've been holding for the last 7 years. And now it would be nice to think about what to expect from the future.