Eventually, there's almost always a need for some edge case, some scenario not quite covered by the no-code framework, and you're back to writing code, even if it's sold as not actually coding.
I'd agree that of course "real" programming is gonna be able to cover a lot more cases than "building blocks" programming can ever cover. A bit like comparing only using libraries vs writing your own code, can get you far but will never allow you to do anything.
> and you're back to writing code
My point was more geared towards the people who can't write code. So this is not really an alternative for them. So something imperfect that kind of does what you need, in most cases, is most of the times better than nothing.
I don't think anyone is selling "no code" as a solution that works for everything and any case. But it does work for a lot, so us "real" programmers can stop implementing the same boilerplate over and over, and people who can't program, can build automated workflows for themselves, which is nice.
It's a nice dream, I'm not opposed to it in principle.
However the systems I've seen from vendors pushing (for instance) "no code" data permissions rules on top of an identity database, have quickly shown their rough edges and the need for custom building blocks backed by code (or worse, XML pretending not to be code!). Maybe it's getting better than this now.
