They tried this in the 90s and 00s. It was such a spectacular failure it's funny to see it recycled. And for you to claim you wouldn't have to worry about mai

They tried this in the 90s and 00s. It was such a spectacular failure it's funny to see it recycled. And for you to claim you wouldn't have to worry about maintenance is especially comical. It was extremely high maintenance and expensive, and it often broke. Programmers don't just code a problem, they solve the problem. Teasing out the actual business logic is as much a part of the job as anything else, and one that most employees and managers are so clueless and utterly useless at that any no code solution will require a programmer to actually use it any way. But without any of the flexibility code gives, you end up with tons of dumb, manual, expensive, hacks and a sub-standard product. Eventually the 'no-code' platform adds the ability to use some code and you end up with a really shitty software platform that delivers 80%, but the effort required to get that last 20% is far in excess of just starting again and writing it from scratch in code. Ask any programmer who remembers workflow software their experience and you will learn from the mistakes of two decades ago.