Is Low-Code Development a Productivity Boost or a Hidden Toxicity?

Previously I wrote two articles about low‑code platforms, stating simply that the technology has its strengths and suitable scenarios, but like any software solution, it is not a silver bullet.

Search results for “low‑code” are filled with exaggerated headlines promising that everyone can become a programmer and that low‑code will free developers from long hours, even showing videos of programmers relaxing with coffee.

If you hold such fantasies, you need to read the following analysis.

Fake New Technology

Low‑code is not new; ten years ago we experimented with a drag‑and‑drop development platform that promised revolutionary efficiency, yet the improvement was marginal and far from replacing developers.

Efficiency Poison

Initially, low‑code can speed up simple applications, thanks to small‑scale trial‑and‑error and quick prototypes. However, as adoption expands, several problems emerge:

Platform support becomes a bottleneck, with numerous bugs and errors overwhelming the support team.

New “turf wars” appear when incidents occur, making it hard to determine whether a component bug or user misuse is to blame.

The toxicity is invisible at first, only manifesting when the platform is deployed broadly.

Innovation Poison

Standardized components can stifle creativity; although modern platforms offer custom implementations, developers still depend on the platform team for new features, turning innovation into a waiting game.

A typical scene: product managers request features that the platform does not support, the platform promises a future version months later, and developers are forced to cobble together workarounds, eroding genuine innovation.

Adopt the Right Attitude

The original goals of low‑code—quick onboarding, high development efficiency, low cost, short deployment, and low maintenance—aim to improve team efficiency. Yet when the platform is pushed onto developers, it often degrades their skills and forces them to focus on business rather than leveraging their full technical expertise.

Shifting low‑code to product teams, who have strong domain knowledge, can better align with the platform’s low‑entry‑barrier promise, freeing developers to tackle more complex, innovative tasks.

In practice, product managers with some coding background achieve better results with low‑code, but the overall success depends on using the platform in the right context.

Any tool becomes powerful only when applied correctly; misplaced, it can be worse than waste.