I think that no-code enables non-programmer to produce more workable prototypes without any help from programmer. This speeds up the iteration. If a prototype is proven to be useful, then it can be given to professional programmers to hash out the details and build a robust version.
Actually -- programmers' opinions on no-code solutions are irrelevant. The non-programmers' ones are more important.
This is exactly how we use no-code at my startup. It allows non-programmers to iterate with the product manager on a solution's design before it makes it to the dev team's plate.
The problem is that it's never how those solutions are sold, and rarely how they are bought.
No-code solutions are ok for quick prototyping of automating processes that are not the core of the business. When you start using them you have to define the step where you will switch to a more maintainable solution.
This is the same as deciding when to use a shell script and when to decide to rewrite the script in a stronger programming language.
Actually -- programmers' opinions on no-code solutions are irrelevant. The non-programmers' ones are more important.