Commentary: Developers who are more experienced will be less inclined to use low-code and no-code solutions. This could be a mistake.

Must Read:

You are less likely to use low-code and no-code tools the more experienced you are as a developer. That’s not really the point. Or…

Smarter code and no-code

A recent SlashData survey found that 20% of developers use low-code, non-code tools to do their coding. This number drops to 19% for professional developers, compared with 21% for hobbyists. This is hardly a significant swing, and it suggests that developers will not trust LCNC tools with their most critical tasks.

The report stated that LCNC tools were becoming more attractive when it comes to reducing development overheads, addressing challenges of finding skilled developers, as well as accelerating the time to market for software.

Most Popular:

Despite the fact that low-code and no-code tools are becoming more sophisticated, 54% of developers still don’t use LCNC. This is the half-empty view. However, the glass half-full perspective shows that 45% of developers use low-code, non-code tools. This is a significant increase from just a trace a few years ago.


The survey found that experienced developers with over 10 years’ experience are less likely to use low-code and no-code tools. Developers are less likely not to use any low-code or no-code tools as they gain more experience. This is especially true for developers with over ten years experience.

Never Miss:

SlashData’s survey revealed that developers with 3-10 years of experience are more likely to use low-code, non-code tools in their code (between 25% and 75% of their coding). This could be a sign that they are experienced enough to understand the importance of LCNC, but not too experienced to use such tools.

Use cases for low-code and no-code tools

LCNC tools are great for less-experienced coders and offer non-developers a way of helping to fill the shortage in developer talent. The more exciting opportunity is in low-code no-code. This allows experienced coders to take over complex programming tasks. LCNC tools may not be able to handle the complexity of work that would be assigned to less experienced developers. Experiential developers will likely have mastered simpler coding tasks which makes it difficult to reap the efficiency gains low-code, non-code tools are often praised for.

This is a shame as they might be the ones that will actually benefit most.

Also Read:

Takeaway: Low-code, non-code tools

While I don’t dispute that low-code, non-code tools are ill-equipped for complex coding, our top developers can handle it. However, there is still plenty of boilerplate that LCNC tools can remove.

Things like GitHub Copilot, while not exactly LCNC, promise to remove the “cruft” from coding so developers of all levels can concentrate on the most important code.

Unqork, LCNC provider, posits a future for “codeless architecture” and argues it is similar to serverless. Although you can’t do everything serverless necessarily, it can be a great way for your development to include discrete services.